diff --git a/projects/dhis2-single-page-docs/am_ET/.cache_timestamp b/projects/dhis2-single-page-docs/am_ET/.cache_timestamp index 093fa25b..68117815 100644 --- a/projects/dhis2-single-page-docs/am_ET/.cache_timestamp +++ b/projects/dhis2-single-page-docs/am_ET/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:04Z \ No newline at end of file +2024-10-19T21:24:42Z \ 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 093fa25b..68117815 100644 --- a/projects/dhis2-single-page-docs/ar/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ar/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:04Z \ No newline at end of file +2024-10-19T21:24:42Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/cs/.cache_timestamp b/projects/dhis2-single-page-docs/cs/.cache_timestamp index da03a471..bd311f66 100644 --- a/projects/dhis2-single-page-docs/cs/.cache_timestamp +++ b/projects/dhis2-single-page-docs/cs/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:11Z \ No newline at end of file +2024-10-19T21:24:47Z \ No newline at end of file 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 ea977094..f646d136 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: -- Správa - DHIS core verze 2.37 +- Správa 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 0015ebca..1c6ef1a2 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/es_419/.cache_timestamp b/projects/dhis2-single-page-docs/es_419/.cache_timestamp index bfbcfc91..0630f800 100644 --- a/projects/dhis2-single-page-docs/es_419/.cache_timestamp +++ b/projects/dhis2-single-page-docs/es_419/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:18Z \ No newline at end of file +2024-10-19T21:24:53Z \ No newline at end of file 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 03a64b51..d7ff92a9 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: -- Gestionar - DHIS core version 2.37 +- Gestionar template: single.html --- 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 fb7e8d82..01d43c97 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 --- diff --git a/projects/dhis2-single-page-docs/fr/.cache_timestamp b/projects/dhis2-single-page-docs/fr/.cache_timestamp index 4e20d886..8c08907f 100644 --- a/projects/dhis2-single-page-docs/fr/.cache_timestamp +++ b/projects/dhis2-single-page-docs/fr/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:27Z \ No newline at end of file +2024-10-19T21:24:59Z \ No newline at end of file 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 edaf5a6d..d0db059f 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: -- Gestion - DHIS core version 2.37 +- Gestion 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 61d1b940..a3b1cbb4 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/id_ID/.cache_timestamp b/projects/dhis2-single-page-docs/id_ID/.cache_timestamp index 1bdf0047..565fea5d 100644 --- a/projects/dhis2-single-page-docs/id_ID/.cache_timestamp +++ b/projects/dhis2-single-page-docs/id_ID/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:36Z \ No newline at end of file +2024-10-19T21:25:08Z \ No newline at end of file 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 473e2b48..cd0f951f 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: -- mengatur - DHIS core version 2.37 +- mengatur 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 b4dc9d1e..e09e02b9 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/ko/.cache_timestamp b/projects/dhis2-single-page-docs/ko/.cache_timestamp index f5e1eaaa..705c1b78 100644 --- a/projects/dhis2-single-page-docs/ko/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ko/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:43Z \ No newline at end of file +2024-10-19T21:25:14Z \ 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 f5e1eaaa..705c1b78 100644 --- a/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ko_KR/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:43Z \ No newline at end of file +2024-10-19T21:25:14Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/pt/.cache_timestamp b/projects/dhis2-single-page-docs/pt/.cache_timestamp index 62155605..b32e9d74 100644 --- a/projects/dhis2-single-page-docs/pt/.cache_timestamp +++ b/projects/dhis2-single-page-docs/pt/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:51Z \ No newline at end of file +2024-10-19T21:25:18Z \ No newline at end of file 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 50293e95..1bbb4d94 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: -- Gerir - DHIS core version 2.37 +- Gerir 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 dc91c331..d7b6aeb4 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/ru/.cache_timestamp b/projects/dhis2-single-page-docs/ru/.cache_timestamp index c8f54d49..87393cfc 100644 --- a/projects/dhis2-single-page-docs/ru/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ru/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:24:58Z \ No newline at end of file +2024-10-19T21:25:24Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/si/.cache_timestamp b/projects/dhis2-single-page-docs/si/.cache_timestamp index a62c57dc..edfc689c 100644 --- a/projects/dhis2-single-page-docs/si/.cache_timestamp +++ b/projects/dhis2-single-page-docs/si/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:25:05Z \ No newline at end of file +2024-10-19T21:25:28Z \ 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 a62c57dc..edfc689c 100644 --- a/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp +++ b/projects/dhis2-single-page-docs/ur_PK/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:25:05Z \ No newline at end of file +2024-10-19T21:25:28Z \ No newline at end of file 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 7c0b8dfe..cd13617c 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 +- انتظام 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 542b943d..6dcc8147 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/zh/.cache_timestamp b/projects/dhis2-single-page-docs/zh/.cache_timestamp index 006ff727..4a4fd499 100644 --- a/projects/dhis2-single-page-docs/zh/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:25:12Z \ No newline at end of file +2024-10-19T21:25:34Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp b/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp index 95bddca0..12c8e94a 100644 --- a/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh_CN/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:25:18Z \ No newline at end of file +2024-10-19T21:25:39Z \ No newline at end of file diff --git a/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp b/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp index 0f389c53..06a12dbc 100644 --- a/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp +++ b/projects/dhis2-single-page-docs/zh_TW/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:25:23Z \ No newline at end of file +2024-10-19T21:25:44Z \ 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 1039dfd7..71b80443 100644 --- a/projects/docs-full-site/ar/.cache_timestamp +++ b/projects/docs-full-site/ar/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:20:06Z \ No newline at end of file +2024-10-19T21:19:35Z \ No newline at end of file diff --git a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index 5de425ae..5af553a2 100644 --- a/projects/docs-full-site/ar/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/ar/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-09-18' tags: -- Develop - DHIS core version master +- Develop --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/ar/IMPLEMENT__DATA-USE__data-visualization-md b/projects/docs-full-site/ar/IMPLEMENT__DATA-USE__data-visualization-md index 7ffc7b43..1c0a9753 100644 --- a/projects/docs-full-site/ar/IMPLEMENT__DATA-USE__data-visualization-md +++ b/projects/docs-full-site/ar/IMPLEMENT__DATA-USE__data-visualization-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/data-use/data-visualization.md" -revision_date: '2024-10-17' +revision_date: '2024-10-18' tags: - Implement --- @@ -27,9 +27,9 @@ Understanding these categories is essential to selecting the correct chart type - **Ordinal** - Categories with a meaningful order (e.g., disease status). These categories have a logical sequence. - For example, disease severity might be classified as mild, moderate, and severe, which has an inherent order. -> **Note**: +> **Note** > ->**Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. +> **Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. ![Variable categories](resources/images/dataviz_001.png) @@ -46,7 +46,7 @@ What’s the best way to choose the right visualization for the data at hand? [F Another Chart Chooser is mapped in the [Extreme Presentation Method](https://extremepresentation.com/). -![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.png) +![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.jpg) The summary below is based on the visualizations available in the core DHIS2 Data Visualizer App. @@ -93,9 +93,9 @@ The summary below is based on the visualizations available in the core DHIS2 Dat ### Specific Visualization Styles { #specific-visualization-styles } ->**Note** +> **Note** > ->**Data speaks louder than words!** +> **Data speaks louder than words!** In data visualization, choosing the right type of chart or graph is crucial for effectively communicating your data. Each visualization style has its strengths and is best suited for specific types of data and analytical purposes. This chapter explores a variety of visualization styles, detailing their applications and best practices. Whether you're looking to show trends over time, compare quantities, highlight correlations, or illustrate parts of a whole, selecting the appropriate visualization method will enhance clarity and insight. By understanding the nuances of each style, you can ensure that your data tells a compelling and accurate story. @@ -103,9 +103,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Correlation { #correlation } ->**Note** +> **Caution** > ->Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. +> Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. - **Scatterplot**: Shows the relationship between two continuous variables, each having its axis. Each point represents an observation's values on the two variables. It's useful for identifying trends, clusters, and outliers. For example, a scatterplot can display the relationship between the number of immunization campaigns conducted in various districts and the resulting immunization coverage rate. @@ -118,9 +118,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Ranking { #ranking } ->**Note** +> **Note** > ->Emphasizes the item's position in an ordered list rather than the absolute value. +> Emphasizes the item's position in an ordered list rather than the absolute value. - **Ordered bars/columns**: Shows ranks of values more easily when sorted. This visualization helps to quickly see the highest and lowest values. An ordered bar column chart can be used to display the number of TB cases in each district, sorted in descending order to highlight the districts with the highest burden. @@ -132,9 +132,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Change Over Time { #change-over-time } ->**Note** +> **Note** > ->Keep gaps between columns small to highlight data shape. +> Keep gaps between columns small to highlight data shape. Use markers for irregular data points. - **Column**: Emphasizes changing trends. Columns are used to show discrete data points over time. For example, monthly case figures can be shown as a column chart. @@ -152,9 +152,9 @@ Use markers for irregular data points. #### Magnitude { #magnitude } ->**Note** +> **Note** > ->Small gaps highlight data shape. Best for a single series of data. +> Small gaps highlight data shape. Best for a single series of data. - **Column/Paired column/bar**: Compare sizes, usually numbers rather than rates or percentages. For instance, HIV case figures for different regions can be compared using a bar chart. In this case, it is appropriate to keep the distance between the columns as they represent separate entities rather than variables through time. @@ -168,9 +168,9 @@ Use markers for irregular data points. #### Part-to-Whole { #part-to-whole } ->**Note** +> **Tip** > ->Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** +> Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** ![Imrpove the visualization choosing the most suitable colour set](resources/images/dataviz_022.png) @@ -206,9 +206,9 @@ Stacked columns or bar charts **should be avoided when** a detailed comparison o - **Choropleth**: Standard for rates on maps. Uses varying shades of a colour to represent data values for different regions. For example, population density by region can be shown using a choropleth map. ->**Note** +> **Note** > ->**Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. +> **Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. ![Map showing the percentage of PTB-BC cases in a region](resources/images/dataviz_013.png) @@ -287,9 +287,9 @@ A visualization should always have: ![Contextualized graph](resources/images/dataviz_024.png) ->**Note**: +> **Caution** > ->Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. +> Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. #### Pie Chart { #pie-chart } diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md new file mode 100644 index 00000000..eda4f24c --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -0,0 +1,206 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-design.md" +revision_date: '2023-03-31' +tags: +- Implement +--- + +# COVID-19 Surveillance - Aggregate System Design Guide { #c19-agg-design } + +## Purpose { #purpose } + +The COVID-19 Surveillance Aggregate System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## السياق{ #background } + +This aggregate design has been updated to reflect new aggregate reporting requirements from the [Global surveillance of COVID-19: WHO process for reporting aggregated data](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form), last updated on August 7, 2020. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| **Type of Surveillance Package** | **Case-based Surveillance (Tracker)** | **Case surveillance line-listing (Event)** | **Case surveillance (Aggregate)** | +| --- | --- | --- | --- | +| **Description** | Enrolls a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables weekly reporting of key aggregate data points | +| **Pros** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| **Cons** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation)| + +**This document covers only the design of the aggregate package**; separate system design documents are available for DHIS2 Tracker and Line-listing (event-based) packages. As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The aggregate package is designed to meet the most critical reporting requirements and analytical capacities for surveillance and response. + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated August 7, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +The aggregate COVID-19 surveillance package includes + +1. Weekly aggregate data set and data elements for key COVID-19 surveillance reporting +2. Categories for data disaggregation +3. Core indicators +4. Dashboard and its items + +The dataset captures a minimum number of data points that meet the current WHO weekly reporting requirements; and generate a core set of indicators and dashboards for national and sub-national decision-makers to rapidly analyze and respond to disease trends. + +| **Name** | **Periodicity** | **Purpose** | +| --- | --- | --- | +| Aggregate Weekly Surveillance | Weekly| Reporting of key COVID-19 surveillance data including cases, tests and deaths. | + +It is recommended that the weekly dataset is assigned to Organisation Units at the lowest level of the health system feasible for reporting data, such as health facilities. + +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). + +### Intended users { #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. +- 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 + +## Datasets { #datasets } + +This dataset is intended to capture weekly data needed for rapid response to disease transmission. If the burden of reporting becomes too great or when it is no longer considered an emergency situation in the country, the data set may be changed to monthly according to MOH policies. + +### Daily Surveillance Data Elements { #daily-surveillance-data-elements } + +The following lists the data elements and disaggregation (category combinations) included in the data set: + +| **عناصر البيانات** | **Category Combinations** | +| --- | --- | +| New Confirmed Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Confirmed Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Hospitalized Cases | None | +| New Discharged Cases | None | +| New Cases Among Health Workers (Confirmed + Probable) | None | +| New Deaths Among Health Workers (Confirmed + Probable) | None | +| Number of Persons Tested for COVID-19 | None | +| Number of persons Tested with PCR Assay | None | +| Transmission Classification | None | + +### Weekly Surveillance Data Entry Form { #weekly-surveillance-data-entry-form } + +- **Section 1: New confirmed and probable Cases** + +Data should be entered for all new confirmed and probable cases reported during the reporting period. Confirmed cases refer to laboratory confirmed cases per WHO guidance; probable cases are defined by WHO as cases where laboratory test result is inconclusive; however countries may apply their own case definitions. The total column is automatically summed during data entry. +![Picture1](resources/images/AGG_Picture1.png) + +- **Section 2: New confirmed and probable deaths** + +Data should be entered for new confirmed and probable deaths reported during the reporting period. The total column is automatically summed during data entry. + +![Picture2](resources/images/AGG_Picture2.png) + +- **Section 3: Health worker infection and death** + +This section captures data for health workers' new confirmed and probable cases including deaths reported during the reporting period. + +![Picture3](resources/images/AGG_Picture3.png) + +- **Section 4: Hospitalisation and discharges** + +This section captures data for new hospitalisation and discharges during the reporting period. + +![Picture4](resources/images/AGG_Picture4.png) + +- **Section 5: Tests conducted** + +This section captures data for tests conducted with additional requirement to report tests conducted using PCR during the reporting period + +![Picture5](resources/images/AGG_Picture5.png) + +- **Section 6: Transmission Classification** + +This section summarizes the major form of transmission classification experienced by the reporting unit. + +![Picture7](resources/images/AGG_Picture6.png) + +### Customizing Data Entry Forms { #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) + +## Data Validation { #data-validation } + +The following data validation rules have been configured. These validation rules do not run in the data entry form itself as it is anticipated that the urgent reporting of data where events occur in different time frames (e.g. one week can see only 3 new cases but 5 deaths). + +| **Name** | **Operator** | **Instruction** | **Left side description** | **Right side description** | +| --- | --- | --- | --- | --- | +| COVID19 - PCR tests \<= tested | less\_than\_or\_equal\_to | Tested with PCR should be less than or equal to total tests conducted | Tested with PCR | Tested conducted | +| COVID19 - New Cases hospitalised \<= All New Cases | less\_than\_or\_equal\_to | New Cases hospitalised should be less than or equal to all new cases | New Cases hospitalised | All New Cases | +| COVID19 - New confirmed deaths \<= New confirmed cases | less\_than\_or\_equal\_to | New confirmed deaths should be less than or equal to New confirmed cases | New confirmed deaths | New confirmed cases | +| COVID19 - Probable deaths \<= New probable cases | less\_than\_or\_equal\_to | Probable deaths should be less than or equal to New probable cases | Probable deaths | New probable cases | +| COVID19 - New deaths among HW (confirmed + probable) \<= All deaths reported | less\_than\_or\_equal\_to | New deaths among HW (confirmed + probable) should be less than or equal to All deaths reported | New deaths among HW (confirmed + probable) | All deaths reported | +| 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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Please refer to the [installation guidance](covid-19-aggregate-installation.html) for more information. + +## Indicators { #indicators } + +From the data captured, we can calculate at least the following indicators, many of which are recommended by the WHO for [weekly reporting](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) and present them in a dashboard. All COVID-19 program indicators are assigned to the Indicator Group 'COVID19'. + +| **name** | **description** | +| --- | --- | +| COVID19 - New Confirmed Deaths | Number of new confirmed deaths | +| COVID19 - New Cases Among HW (Confirmed + Probable) | Number of New Cases Among HW (Confirmed + Probable) | +| COVID19 - Proportion of HW amongst reported cases (%) | Proportion of HW amongst reported cases (%) | +| COVID19 - Active cases | Number of of active cases | +| COVID19 - Closed cases | Number of closed cases | +| COVID19 - New Confirmed cases | Number of new Confirmed cases | +| COVID19 - Recovery rate (%) | Recovery rate of confirmed cases | +| COVID19 - Case fatality rate among HW (%) | Case fatality rate among HW | +| COVID19 - New Hospitalized Cases | New Hospitalized Cases | +| COVID19 - Tested | Total number of tests conducted | +| COVID19 - Tested with PCR Assay | Tested with PCR assay | +| COVID19 - Positivity rate (%) | Positivity rate | +| COVID19 - New Probable Cases | Number of new probable cases | +| COVID19 - New Discharged Cases | Number of new discharged cases | +| COVID19 - New Deaths Among HW (Confirmed + Probable) | Number of new deaths among HW (Confirmed + Probable) | +| COVID19 - Proportion of PCR tests (%) | Proportion of PCR tests conducted | +| COVID19 - All cases (Confirmed + Probable) | Number of all cases (Confirmed + Probable) | +| COVID19 - New Probable Deaths | Number of new probable deaths | +| COVID19 - Case fatality rate (%) | Case fatality rate among confirmed cases | + +## Dashboards { #dashboards } + +Key analytic items have been configured and added onto the dashboard “COVID19 - Aggregate Weekly Surveillance”. These items include; pivot tables, charts and a map designed to provide data visualization for some of the data captured based on the indicators. In the process of adopting this package, users can modify or create additional items as suits their analytical needs and equally make the necessary adjustments to the dashboard. + +| **name**|**type**| +| --- | --- | +|COVID19 - Tested, tests with PCR and positivity rate by subnational level this year |Pivot table| +|COVID19 - HW amongst reported cases this year |Chart| +|COVID19 - Fatality rate amongst HW.|Chart| +|COVID19 - New confirmed cases and deaths in the last 12 weeks|Chart| +|COVID19 - Cumulative tests conducted, cases reported, hospitalised, discharged and deaths|Chart| +|COVID19 - Cumulative confirmed cases by subnational|Map| +|COVID19 - Deaths by age groups last weeks|Chart| +|COVID19 - Confirmed cases by sex in the last 14 weeks|Chart| +|COVID19 - Closed and active cases at subnational last months|Chart| +|COVID19 - Case recovery and fatality rates last 12 weeks|Chart| +|COVID19 - Active and Closed Cases last 12 weeks|Chart| + +## References { #references } + +- Installation guidance: [https://www.dhis2.org/covid-19](covid-19-aggregate-installation.html) +- WHO Interim guidelines on nCoV-19 surveillance & case definitions (last updated March 20, 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions>]() +- WHO COVID-19 surveillance data dictionary (v6) +[https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98\_2](https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2) +- WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) + [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +- WHO Coronavirus situation reports + [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports>]() +- Global surveillance of COVID-19: WHO process for reporting aggregated data +[https://www.who.int/publications/i/item/aggregated-weekly-reporting-form](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md new file mode 100644 index 00000000..9597ff7e --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-installation.md" +revision_date: '2022-11-07' +tags: +- Implement +--- + +# Aggregate Package Installation Guide { #c19-agg-installation } + +## Overview { #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. + +The configuration packages for DHIS2 consists of a metadata file in [JSON](https://en.wikipedia.org/wiki/JSON) format which can be imported into a DHIS2 instance, as well as accompanying documentation. The package provides pre-defined, standard content according to WHO recommendations. This document is concerned with complete packages that include configurations of data collection (data sets, data elements, validation rules) as well as analysis and dashboards (chart, map and pivot table favourites). This is intended for use where there is no data collection configured in DHIS2, or if replacing/revising existing content to align with WHO recommendations. + +The configuration packages consists of 4 main components: + +* data sets with data elements; +* a set of indicators; +* analytical outputs (pivot table, data visualizer and GIS favourites); and +* a set of dashboards. + +These components are all linked, i.e. the indicators are based on the included data elements, the analytical outputs are based on the included indicators, and the dashboards are made up of the included analytical outputs. + +## Installation { #installation } + +Installation of the module consists of two steps: + +1. [Preparing](#preparing-the-metadata-file) a metadata file with DHIS2 metadata. +2. [Importing](#importing-a-metadata-file-into-dhis2) a metadata file into DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Performing](#examples-of-other-modifications) package-specific modifications. + +This section deals with the first two steps of preparing and importing the metadata file into DHIS2, whilst the configuration procedure is discussed in the next section. It is recommended to first read through both sections before starting the installation and configuration process in DHIS2. In addition to the general steps described here, some of the configuration packages have annexes to the installation guide, describing particular issues. These are listed in the appropriate section [here](https://dhis2.org/who-package-downloads). + +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. + +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 } + +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): + +* data elements (including categories) +* data sets +* indicators +* indicator types +* dashboards +* data visualizer, pivot table and GIS favourites + +The full list of objects included in the module (for which the administrator needs authorities to manage) can be found in the Metadata reference document for the particular configuration package. + +In cases where modifications to the .json metadata file of the configuration package are necessary [(see below)](https://who.dhis2.org/documentation/installation_guide_complete.html#preparing-the_metadata-file), a [text editor](https://en.wikipedia.org/wiki/Text_editor) is needed - these modifications should not be done with a word processor such as Microsoft Word. + +The configuration package can be installed in DHIS2 through the DHIS2 Health App, or manually through a .json file with DHIS2 metadata using the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. The procedure described in the rest of this section applies to the process of manually importing metadata. + +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 } + +**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. + +## Default data dimension { #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| +|--|--|--| +|Category|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Category option|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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 } + +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| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Percentage|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. + +**Note 2**: An alternative approach to re-using the existing indicator types is to import those included in the configuration package, and removing the existing ones that overlap. This would require all indicators that use these existing indicator types to be updated to the newly imported indicator types, before the indicator types can be deleted. + +## Importing a metadata file into DHIS2 { #importing-a-metadata-file-into-dhis2 } + +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 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 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 } + +**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 } + +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 } + +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. + +#### 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. +* 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. + +## Additional Configuration { #additional-configuration } + +Once all metadata has been successfully imported, the module should be useable with only a few minor additional adjustments. In addition, depending entirely on the DHIS2 instance the module has been imported into, some additional configuration and modification might be necessary or advantageous. This section will first go through the necessary configuration steps, then mention some of the other types of modifications or configuration that might be relevant. + +## Required configuration { #required-configuration } + +Before the configuration packages can be used for data collection, there are two steps that are required. + +* Assign the data set(s) to appropriate organisation units +* Share the data set(s) with appropriate user groups +* Add your user(s) to the appropriate user groups + +The data sets should be assigned to the organisation units (facilities) which are expected to report on that particular data set. + +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 } + +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: + +* Data elements/Data element groups +* Indicators/Indicator groups +* Data Sets +* Dashboards + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +We recommend the following access + +|Object|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| +|_Indicators/Indicator group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| +|_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 } + +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. + +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 data element categories exists these duplications can be hidden to end users through category option group sets, or certain metadata objects can be hidden for groups of users through sharing. + +It is recommended not to remove or replace the indicators included in configuration packages even though the same indicator already exists, so that the analytical outputs (which as based exclusively on indicators) can be kept. This will allow training material based on the configuration packages to be re-used. + +## Examples of other modifications { #examples-of-other-modifications } + +In addition to the required configuration, there are a number of other modifications and configuration that might be relevant, depending on the specific situation. It will not be possible to provide guidance and recommendations that cover all the different scenarios, but a brief discussion of some common problems are presented here. + +### Translations { #translations } + +Additional translations might have to be added, if other languages than those included are needed. + +### Adding additional variables { #adding-additional-variables } + +The configuration packages includes key recommended data elements and indicators. However, it might in some cases be necessary to add additional variables to address country-specific information needs. These could be added to the included data sets. + +### Updating layout of reporting forms { #updating-layout-of-reporting-forms } + +To facilitate the work of personnel doing data entry in DHIS2, it is sometimes desirable to add a custom data entry form that match the format of paper forms used at the primary level. + +## Maintenance { #maintenance } + +No particular maintenance is required for the configuration packages, since they are made up of standard DHIS2 metadata objects. However, before upgrading to new versions of DHIS2, it is important to test all functionality of the system in general on a staging/test server before upgrading any production instances of the system. + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md new file mode 100644 index 00000000..4322bbef --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/overview.md" +revision_date: '2023-03-07' +tags: +- Implement +--- + +# COVID-19 Aggregate Surveillance { #covid-19-aggregate-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-agg-release-note) + +## Design { #design } + +- [Version 2.0.0](#c19-agg-design) + +## Installation { #installation } + +- [Installation Guide](#c19-agg-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 2.0.0](https://packages.dhis2.org/en/C19_AGG/2.0.0/DHIS2.39/C19_AGG_COMPLETE_2.0.0_DHIS2.39.xlsx) + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md new file mode 100644 index 00000000..f10d3d99 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md @@ -0,0 +1,26 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implement +--- + +# Release Note { #c19-agg-release-note } + +To see additional details of the metadata objects mentioned below, refer to the metadata reference documentation of the relevant version. + +## 2.0.0 { #200 } + +* The changes leading to this version were based on the revised [WHO Global surveillance of COVID-19 Weekly Aggregate Report ](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) +* The major were made on the age disaggregations with 5 year age bands used for <20 years and 60+ years spanning upto 80+years. +* Unknown age and Unknown sex were also introduced in the disaggregations to cater data that cannot be categorized with the options provided. +* Data elements for cases and deaths among health workers (Confirmed + Probable), tests with PCR assay, deaths amongst probable cases and health workers were introduced in this version. +* Data elements for logistics and cases by transmission classifications were removed. +* Considering these changes, all the core metadata objects; data elements, indicators, dashboard and its items, dataSets, indicator groups and data elements groups were newly created. +* This version now has only one dataSet designed for weekly reporting unlike in the previous version that had 2 dataSets reported weekly and daily basis. +* All the core metadata objects have been coded in support for international standard for aggregate data exchange (ADX). + +## 1.0.0 { #100 } + +Initial release of COVID-19 Aggregate Surveillance package + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md new file mode 100644 index 00000000..ef1b5491 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -0,0 +1,291 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-design.md" +revision_date: '2022-09-13' +tags: +- Implement +--- + +# COVID-19 Case Surveillance & Contact Tracing Design { #c19-cs-design } + +Demo: [https://demos.dhis2.org/covid-19](https://demos.dhis2.org/covid-19) + +## Purpose { #purpose } + +The COVID-19 Surveillance System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## السياق{ #background } + +**This design has been updated to reflect new aggregate reporting requirements from the [WHO interim surveillance guidelines updated March 20, 2020][1]**. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| Type of Surveillance Package | Case Surveillance (Tracker) | Surveillance (Event) | Surveillance (Aggregate) | +|---|---|---|---| +| ***Description*** | Enrols a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables daily or weekly reporting of key aggregate data points | +| ***Pros*** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| ***Cons*** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) | + +**This document covers only the design of the surveillance tracker program package**; separate system design documents are available for DHIS2 event and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing case disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 surveillance package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions][2], updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +The DHIS2 case surveillance tracker metadata was based on the **[WHO COVID-19 case reporting template][3]** and the mapping of data dictionaries can be accessed at: [DHIS2 CBS tracker metadata WHO line-list data dictionary][4]. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles][5] and a common [naming convention][6]. + +The COVID-19 digital data package supports surveillance workflows and automated analysis for key components of routine and active surveillance. This package includes a Case Surveillance Tracker and Contact registration & follow-up tracker, which are installed together in the same metadata package. The tracker programs are optimized to be installed with other COVID-19 surveillance packages, including the Points of Entry Screening Tracker and aggregate daily surveillance dataset. + +1. **[Use Case 1: COVID-19 Case surveillance tracker][7]**: enrols & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. Metadata for the case surveillance tracker is aligned with the WHO [COVID-19 surveillance data dictionary][8] + + > n.b. The COVID-19 case tracker can be implemented either as a ‘standalone’ program for COVID-19 specific disease surveillance as described here; or, COVID-19 concepts can be integrated into an existing case surveillance tracker program if one already exists in-country. Please refer to installation and implementation guidance for more details. + +1. **[Use Case 2: Contact registration & follow-up][9]**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. + +Digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [Google Play store][10]. + +## Use Case 1: COVID-19 Case surveillance tracker { #use-case-1-covid-19-case-surveillance-tracker } + +The COVID-19 case surveillance tracker can be adapted and used by countries to supplement existing national disease surveillance programs. The basic case surveillance program is designed to: + +1. Enroll suspected\* COVID-19 cases (*generally appearing at a health facility, but may be enrolled at other places*) +2. Capture key information about the suspected case including demographics and exposures, such as symptoms, contact with a previously confirmed case & travel history +3. Generate lab requests +4. Record laboratory diagnosis +5. Record contacts of a confirmed\*\* or probable\*\*\* case for follow-up +6. Record case outcome +7. Facilitate case notification and national/regional/global case reporting +8. Generate dashboards and analytics tools for monitoring disease trends and planning response efforts + +The design of the case tracker program assumes that [WHO case definitions][1] are followed in the use case; its use can be adapted to local case definitions as needed. The WHO case definitions were updated on March 20, 2020 and noted below. + +> \* Suspected case: A) a patient with acute respiratory illness (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness of breath), AND with no other aetiology that fully explains the clinical presentation AND a history of travel to or residence in a country/area or territory reporting local transmission of COVID-19 disease during the 14 days prior to symptom onset; **OR**, B) A patient with any acute respiratory illness AND having been in contact with a confirmed or probable COVID-19 case (see definition of contact) in the last 14 days prior to onset of symptoms; **OR,** C) A patient with severe acute respiratory infection (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness breath) AND requiring hospitalization AND with no other aetiology that fully explains the clinical presentation. +> +>\*\* Probable case: A) a suspect case for whom testing for COVID-19 is inconclusive (inconclusive being the result of the test reported by the laboratory) **OR,** B) a suspect case for whom testing could not be performed for any reason. +> +>\*\*\* Confirmed case: A person with laboratory confirmation of COVID-19 infection, irrespective of clinical signs and symptoms. + +### Intended Users { #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 +* 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 + +### Workflow: COVID-19 Case Surveillance Tracker { #workflow-covid-19-case-surveillance-tracker } + +![Workflow of the DHIS2 COVID-19 Case Surveillance Tracker](resources/images/sdd-tracker-v3-case1-workflow.png) + +### Structure: COVID-19 Case Surveillance Tracker Program { #structure-covid-19-case-surveillance-tracker-program } + +![Structure of the COVID-19 Case Surveillance Tracker Program](resources/images/sdd-tracker-v3-case1-structure-v2.png) + +#### Program Description: COVID-19 Case Testing, Diagnosis & Outcome { #program-description-covid-19-case-testing-diagnosis-outcome } + +| Stage | Description | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is the case, which is represented by a Tracked Entity Type of ‘person.’ The *Enrollment date* is the date of registration of the case. The Related programs is *COVID-19 Contact registration & follow-up*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *Age*, *First Name*, *Surname*, *Sex*, *Case phone number*, *First Name (parent or care)*, *Surname (parent or carer)*, *Home Address*, *Workplace/school physical address*, *Country of Residence*, *Facility contact number*| +| **Stage 1: Clinical Examination and Exposures** | This stage records a suspected case’s clinical symptoms and exposures including: *Symptoms*, *Pregnancy and underlying conditions*, *Hospitalisation and Isolation*, *Exposures in 14 days prior to symptoms*, *Travel history*, *Contact with confirmed case*. After examination, you can record if the case has been hospitalised or isolated, and information surrounding this. | +| **Stage 2: Lab Request [repeatable]** | The lab request records the reason for testing and other information that a lab needs to process a sample and test it for COVID19. The information provided here can help lab personnel prioritize lab tests when resources are limited. The person entering this data could be the same person who registered the suspected case and recorded the patient’s clinical exam and exposures; or may be other personnel charged with making lab requests. | +| **Stage 3: Lab Results [repeatable]** | The Lab Results stage records the type and results from laboratory testing. It can be done directly at the lab or as secondary data entry. This stage is repeatable as samples for a given case may be tested multiple times (i.e. in the case of an inconclusive laboratory results, a new lab test can be conducted and results recorded). | +| **Stage 4: Health Outcome** | The health outcome records the final outcome of the case: (recovered, not recovered, dead or unknown) including date of discharge or death as applicable. | + +#### Enrollment Stage { #enrollment-stage } + +![Enrollment](resources/images/sdd-tracker-v3-case1-enrollment.png) + +#### Program Stage 1 - Clinical Examination & Diagnosis { #program-stage-1-clinical-examination-diagnosis } + +##### Section 1 - Clinical Signs and symptoms { #section-1-clinical-signs-and-symptoms } + +Selecting “yes” to the Data Element ‘Any signs or symptoms?’ reveals the rest of the options. + +![Section 1](resources/images/sdd-tracker-v3-case1-stage1-section1.png) + +##### Section 2 - Pregnancy Details { #section-2-pregnancy-details } + +This section is hidden unless gender is selected as ‘Female.’ + +![Section 2](resources/images/sdd-tracker-v3-case1-stage1-section2.png) + +##### Section 3 - Underlying Conditions/Comorbidity { #section-3-underlying-conditionscomorbidity } + +The details of this section are hidden unless “Any underlying conditions” is marked as “Yes”. + +![Section 3](resources/images/sdd-tracker-v3-case1-stage1-section3.png) + +##### Section 4 - Hospitalisation { #section-4-hospitalisation } + +The details of this section is hidden unless “Hospitalised” is marked as “Yes”. + +![Section 4](resources/images/sdd-tracker-v3-case1-stage1-section4.png) + +##### Section 5 - Exposure Risk { #section-5-exposure-risk } + +This section is used to record exposures + + 1. The fields ***country, city and facility*** are hidden by program rules if the case is not a health care worker; + 2. The fields for contact IDs are hidden by program rules if the case has not had contact with a confirmed case in 14 days. + +A suspected case’s exposure to a *previously confirmed* case is distinct from prospective contact tracing in Program Stage 5. + +![Section 5](resources/images/sdd-tracker-v3-case1-stage1-section5.png) + +##### Section 6 - Travel History { #section-6-travel-history } + +![Section 6](resources/images/sdd-tracker-v3-case1-stage1-section6.png) + +#### Program Stage 2: Lab Request { #program-stage-2-lab-request } + +![Stage 2](resources/images/sdd-tracker-v3-case1-stage2.png) + +#### Stage 3: Lab Results { #stage-3-lab-results } + +![Stage 3](resources/images/sdd-tracker-v3-case1-stage3.png) + +#### Stage 4: Health Outcomes { #stage-4-health-outcomes } + +![Stage 4](resources/images/sdd-tracker-v3-case1-stage4.png) + +### Program Rules: COVID19 Case Surveillance Tracker { #program-rules-covid19-case-surveillance-tracker } + +The following program rules have been configured. If a country has an existing case surveillance program and wishes to incorporate elements of the COVID-19 case tracker into their existing program, special attention must be paid to the configuration of program rules. + +| Program Rule Name | Program Rule Description | +|---|---| +| Assign Enrollment Date | This assigns the enrollment date if there is no onset date available to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators. | +| Assign Onset Date| This assigns the onset date to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators.| +| Calculate and assign patient age in years | Calculate and assign patient age in years based on DOB | +| Display patient age in years + days | Display patient age in years + days | +| Hide Date of Death | Hide the Date of Death unless Death is the health outcome | +| Hide Date of Discharge | Hide Date of Discharge if no outcome or if the outcome is death | +| Hide Measured Temperature field | Hide Measured Temperature field until Fever is selected | +| Hide confirmed case ID's if no contact with other confirmed cases| Hides any contact ID's if the case has not been in any contact with other confirmed cases | +| Hide health care worker details if not a health worker | Hide health care worker details if not a health worker | +| Hide health outcome explanation if health outcome is not other | Hide health outcome explanation if health outcome is not other | +| Hide hospitalisation details if hospitalisation is no or unknown | Hide hospitalisation details if hospitalisation is no or unknown | +| Hide isolation date if case is not in isolation | Hide isolation date if case is not in isolation | +| Hide pregnancy details for a female if not pregnant | Hide pregnancy details for a female if not pregnant | +| Hide pregnancy details section if sex is male | Hide pregnancy details section if sex is male | +| Hide reason for testing explanation if an option is selected | Hide reason for testing explanation if an option is selected | +| Hide travel history details if no travel 14 days prior to symptom onset | Hide travel history details if no travel 14 days prior to symptom onset | +| Hide underlying conditions if case does not have any | Hide underlying conditions if case does not have any | +| Show warning if the event date is after the enrollment date | Show warning on completion of an event if the event date is before the enrollment date | + +You can read more about program rules here: [https://docs.dhis2.org/master/en/user/html/configure\_program\_rule.html][11] + +### Program Indicators { #program-indicators } + +From the data captured in the COVID-19 case surveillance program, we can calculate at least the following indicators including those recommended by the WHO for daily and weekly aggregate reporting and present them in a dashboard: + +| Indicator name | Description | +|---|---| +| COVID-19 - Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU) | *Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU)* | +| COVID-19 Contacts | *Counts the number of relationships (‘has been in contact with’) created that are linked to the case TEI* | +| COVID-19 - Deaths (all suspected cases) | *COVID-19 related deaths (deaths recorded among all suspected cases)* | +| COVID-19 - Deaths (confirmed cases) | *COVID-19 related deaths (deaths recorded among confirmed cases)* | +| COVID-19 - Deaths (probable cases) | *COVID-19 related deaths (deaths recorded among all probable cases)* | +| COVID-19 - Confirmed Hospitalised Cases | *Number of confirmed cases that were admitted into hospital* | +| COVID-19 - Imported Cases | *Cases where likely source of infection is recorded as another country or imported from another country.* | +| COVID-19 - Laboratory confirmed cases | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by report date* | +| COVID-19 - Laboratory confirmed cases - by onset of symptoms | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by date of onset of symptoms* | +| COVID-19 - Laboratory tested cases | *Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)* | +| COVID-19 - Local transmission cases | *Number of suspected cases where transmission is local (no travel in last 14 days* | +| COVID-19 - Probable cases | *Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date* | +| COVID-19 - Probable cases - by onset of symptoms | *Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms* | +| COVID-19 - Recovered confirmed cases | *Number of laboratory confirmed cases with outcome recovered*| +| COVID-19 - Suspected cases | *Total number of cases suspected with COVID-19, by report date* | +| COVID-19 - Suspected cases - by onset of symptoms | *Total number of cases suspected with COVID-19, by date of onset of symptoms* | +| COVID-19 - Suspected cases without a positive test result | *Total number of suspected cases without a positive lab result* | +| COVID-19 Total number of laboratory tests conducted | *Total number of lab tests conducted (count of tests, not cases)* | +| COVID-19 Total number of positive tests | *Total number of lab tests returned with positive results (count of tests, not cases* | +| COVID-19 Deaths by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Confirmed cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Suspected cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | + +## Use Case 2: COVID-19 Contact registration & follow-up { #use-case-2-covid-19-contact-registration-follow-up } + +This program can be used in addition to the case surveillance tracker to facilitate the registration and follow-up of contacts of a confirmed case. In this scenario, it is assumed that if any contacts of a confirmed case meet criteria for suspected case and are referred for testing, the case will be enrolled into the COVID-19 Case Surveillance tracker program. + +The Contact registration & follow-up program registers each contact of a case (as described in COVID-19 Case Surveillance Use Case) as a new Tracked Entity Instance (person) and links them to the case in the COVID-19 Case Surveillance Program via a ‘relationship.’ It has a simple repeatable follow-up stage where symptoms and any follow-up undertaken can be registered. + +### Workflow: Contact registration & follow-up { #workflow-contact-registration-follow-up } + +![Worflow of the Contact registration & follow-up](resources/images/sdd-tracker-v3-case2-workflow.png) + +### Program Description: Contact registration & follow-up { #program-description-contact-registration-follow-up } + +| Stage | Description | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is represented by a Tracked Entity Type of ‘person.’ The Related program is *COVID-19 Case based surveillance*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *First Name*, *Surname*, *Date of birth*, *Age*, *Sex*, *Phone number (local)*, *Home Address*, *Country of Residence* | +| **Stage 1: Follow-Up [non-repeatable]** | This stage is meant to record information related to contact tracing follow up, given that a contact has already been identified. It is divided into two sections: *1. Relation with case*, *2. Exposure Assessment* | +| **Stage 2: Symptoms[repeatable]** | This stage is intended to record symptoms of the case. Follow-up to check on the symptoms of a contact can be repeated until the follow-up period is complete (for example, after 14 days or according to national guidelines). When follow-up period is complete, the enrollment can be ‘completed.’ *1. Symptoms*| + +Contacts are added to the index case using the relationships menu in the case surveillance program: + +![Profile](resources/images/sdd-tracker-v3-case2-profile.png) + +Once you select “Add” from the relationships box, you are able to select the relationship and program and either select an existing person or enroll a new contact using the enrollment stage that appears. This will enroll the contact into the contact registration and follow-up +program. + +![Add a relationship](resources/images/sdd-tracker-v3-case2-add-relationship.png) + +Contacts that are added will then be listed on the case’s tracker dashboard in the relationship +widget + +![Relationships widget](resources/images/sdd-tracker-v3-case2-relationships-widget.png) + +You may also enroll them separately into the program. Once enrolled, you will be able to find them for the follow-up as required. + +#### Enrollment { #enrollment } + +![iEnrollment in the use case 2](resources/images/sdd-tracker-v3-case2-enrollment-case2.png) + +#### Program Stage 1 : Follow - Up { #program-stage-1-follow-up } + +![Case 2 Stage 1](resources/images/sdd-tracker-v3-case2-stage1.png) + +#### Program Stage 2 : Symptoms { #program-stage-2-symptoms } + +![Case 2 Stage 2](resources/images/sdd-tracker-v3-case2-stage2.png) + +### Program Indicators: Contact Registration { #program-indicators-contact-registration } + +| Program Indicator Name | Description | +|---|---| +| COVID-19 travelers screened | Total number of travelers screened and enrolled in screening program from POE | +| COVID-19 travelers cleared at POE | Number of travelers cleared after POE screening (no follow-up required) | +| COVID-19 travelers with symptoms at POE | Number of travelers presenting with symptoms during POE screening | +| COVID-19 travelers cleared after 14 days monitoring | Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period) | +| COVID-19 travelers referred to health facility | Number of travelers that were referred to a health facility at any time during 14 day followup | +| COVID-19 travelers enrolled for 14 day follow-up | Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening | +| COVID-19 currently under follow-up | Number of travelers that have not been cleared or referred to a health facility | +| COVID-19 travelers developed symptoms during follow-up | Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening) | + +## References { #references } + +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form [https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + +[1]: https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf +[2]: https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions +[3]: https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx +[4]: https://drive.google.com/open?id=1vigXHkP7L2hJ2lrZpdf9u4csQtppMH16 +[5]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html +[6]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html +[7]: #use-case-1-covid-19-case-surveillance-tracker +[8]: https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2 +[9]: #use-case-2-covid-19-Contact-registration-follow-up +[10]: https://play.google.com/store/apps/details?id=com.dhis2&hl=en +[11]: https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md new file mode 100644 index 00000000..b3913fde --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-installation.md" +revision_date: '2022-09-13' +tags: +- Implement +--- + +# COVID-19 Surveillance - Installation Guide { #c19-cs-installation } + +## Overview { #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: + +1. COVID-19 Case-based Surveillance Tracker program & COVID-19 Contact Registration & Follow-Up program +2. Points of Entry Screening Tracker program + +You will have to follow the instructions in full for each separate package that you install. + +## Installation { #installation } + +Installation of the module consists of several steps: + +1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. +2. [Importing](#importing-metadata) the metadata file into DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Adapting](#adapting-the-tracker-program) the program after being imported + +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 } + +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 } + +**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. + +### Default data dimension { #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| +|--|--|--| +|Category|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Category option|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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 } + +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| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Percentage|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| +|--|--|--| +|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| + +## Importing metadata { #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 } + +***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 } + +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 } + +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. + +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. + +#### 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: + +* 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. + +## 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. + +### Sharing { #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 +* Program +* Program stages +* Dashboards + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +By default the following is assigned to these user groups + +|Object|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| +|_*Program*_|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| +|_*Dashboards*_|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: + +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. + +### Organisation Units { #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 } + +**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. + +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). + +## 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. +* 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. + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md new file mode 100644 index 00000000..60263176 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md @@ -0,0 +1,29 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/overview.md" +revision_date: '2022-11-22' +tags: +- Implement +--- + +# COVID-19 Case Surveillance { #covid-19-case-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-cs-release-note) + +## Design { #design } + +- [Version 1.0.2](#c19-cs-design) + +## Installation { #installation } + +- [Installation Guide](#c19-cs-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 1.0.2](https://packages.dhis2.org/en/C19_CS/1.0.2/C19_CS_COMPLETE_1.0.2_DHIS2.37.xlsx) + +## Training Material { #training-material } + +- [COVID-19 Training Material](https://dhis2.org/covid-training-material) + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..27d88ae2 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implement +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Overview { #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/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md new file mode 100644 index 00000000..94302510 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -0,0 +1,136 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/c19_poe-design.md" +revision_date: '2022-07-05' +tags: +- Implement +--- + +# COVID-19 Points of Entry Tracker Design { #c19-poe-design } + +Demo: [https://covid19.dhis2.org/](https://covid19.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Points of Entry (POE) Screening System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## السياق{ #background } + +The Points of Entry Screening Tracker is inspired by the pioneering design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health. In January 2020, the Sri Lanka MOH implemented screening measures at ports of entry like airports to identify travelers who may have been exposed to nCoV-19. DHIS2 tracker was to enroll travelers entering Sri Lanka who had visited countries impacted by COVID-19. DHIS2 tracker enabled follow-up with travelers at field level for 14 days to ensure no symptoms developed. If symptoms developed, travelers would be referred to a health facility for clinical examination and testing. The POE tracker can be used in combination with other COVID-19 digital data packages that include case surveillance and contact tracing. + +The World Health Organisation (WHO) has published [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). Points of entry (POE) include international airports, seaports and land crossings. POE measures include 1) detection of ill travellers; 2) interview of ill travellers for COVID-19; 3) reporting of alerts of ill travellers with suspected COVID-19 infection and 4) isolation, initial case management and referral of ill travellers with suspected COVID-19 infection. These guidelines should be consulted, in addition to national protocols for points of entry. + +## System Design Summary { #system-design-summary } + +### Use Case { #use-case } + +The POE tracker program use case was designed to support the registration of travelers 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. For this use case, it is assumed that a traveler may be 1) screened and cleared immediately with no follow-up needed; 2) screened and followed up for 14 days [with or without isolation measures] to ensure no symptoms develop; or 3) screened and referred for testing and/or initial case management. The current design proposes that a traveler meeting the country’s definition of a suspected case would be enrolled into the complementary DHIS2 COVID-19 Case-Based Surveillance (CBS) Tracker. For example, a traveler enrolled in this program who later meets the definition of a suspected case during follow-up (i.e. an asymptomatic traveler from a country with known transmission is registered at the POE and later develops symptoms) is enrolled as a suspected case into the COVID-19 CBS program to capture all clinical details, exposures and follow the case through laboratory diagnosis and case outcome. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +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). + +### Intended users { #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. +* National and local health authorities: monitor and analyse data through dashboards and analytics tools to conduct risk assessments and plan response measures. + +### Workflow { #workflow } + +The Points of Entry program workflow is based on the following scenario + +![Scenario](resources/images/POE_image01.png "Scenario") + +In this design, it is assumed a traveler would complete their enrollment in the POE under the following scenarios: + +1. Traveler is marked as ‘cleared’ during initial screening or after 14 day follow-up +2. Traveler is referred to health facility at any point during follow-up + +**A traveler that is referred to a health facility is expected to be enrolled in the COVID-19 Case-based Surveillance Tracker as a suspected case** (according to national guidelines). Details about a suspected case including clinical exam, exposures, laboratory results and case outcome would be recorded in the CBS program. + +### Structure: Points of Entry Screening Tracker Program { #structure-points-of-entry-screening-tracker-program } + +![Structure](resources/images/POE_image02.png "Structure") + +#### Consideration for Organisation Units & Geography { #consideration-for-organisation-units-geography } + +This program design assumes that Points of Entry such as airports, seaports or land crossings will be created as organisation units included in the OU hierarchy. The program would be assigned to the POE org units. Primary analysis is based on the enrolling Org Unit (the port of entry). + +Additional geographical components are also captured as other dimensions: + +1. TEI coordinates: It is possible to capture TEI coordinates when registering the traveler as TEI. These can be displayed in the maps app. Local protocols may choose what coordinates to enter, for example the TEI’s local residence where he/she may be self-quarantined for 14 days. +2. Event coordinates: for screening and follow-up stages, coordinates can be captured on the event and displayed in a map. For example, the user may capture a traveler’s location each time they are followed up (i.e. in the case of tourists or others not in home quarantine). + +#### Program Description { #program-description } + +|Stage|Description| +|--|--| +|**Registration**|The Tracked Entity is the traveler, which is represented by the Tracked Entity Type of ‘person.’ The TEI is configured to collect a geographic ‘point’ during registration. These can be analyzed in a map.| +|**Enrollment details**|Enrollment date
The first Program Stage is configured to appear on the Registration page so that a user does not need to click through to add the first event.| +|**الخصائص**|Attributes include basic personal information and unique case identifiers
- Passport number
- Local Case ID
- Age
- First Name
- Surname
- Country of residence
- Sex
- Date of birth
- Local address
- Home address
- Telephone (local)
- Telephone (foreign)
- Emergency contact
- Emergency contact phone
- Email| +|**Stage 1**
**Screening at POE**
**(non-repeatable)**|This stage records:
- Traveler details (countries visited, flight number, date of departure, etc)
- Examination: recorded temperature
- Symptoms: this list includes symptoms typically checked for both COVID-19 symptoms and symptoms of other potential notifiable diseases
- Case clearance

If the traveler is marked as ‘cleared’, no further follow up is required; the enrollment may be closed. If the traveler requires follow-up, an event can be scheduled for follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 2:**
**Follow-up (within 14 days)**
**(repeatable)**|Data is entered at this stage if any interim follow-up is performed before the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment may be closed if no further monitoring & follow-up is planned in this program.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 3:**
**Follow-up (after 14 days)**
**(non-repeatable)**|Data is entered at this stage at the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)
- Case clearance

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment should be closed at the completion of 14 day follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization. + +![Enrollment](resources/images/POE_image03.png "Enrollment") + +![Program Stage 1 - Screening at POE](resources/images/POE_image04.png "Program Stage 1 - Screening at POE") + +![Program Stage 1 - Screening at POE](resources/images/POE_image05.png "Program Stage 1 - Screening at POE") + +![Program Stage 2: Follow-up (within 14 days)](resources/images/POE_image06.png "Program Stage 2: Follow-up (within 14 days)") + +![Program Stage 3: Follow up (after 14 days)](resources/images/POE_image07.png "Program Stage 3: Follow up (after 14 days)") + +#### How to refer the TEI to another Organisation Unit { #how-to-refer-the-tei-to-another-organisation-unit } + +Primary analysis is completed on the enrolling organisation unit (the port of entry). Referral facility is captured as a Data Element (type: Organisation Unit) in order to display travelers by referral to health facility in the analytics apps (i.e. Event Report). In some use cases, it may be desirable to refer the TEI (the traveler) to another Org Unit for follow-up. + +A TEI can be ‘referred’ to another org unit such as a health facility for one event or permanently. In this case, health facility user must be able to search TEIs enrolled in the relevant Points of Entry org units. For example, if after screening a traveler at the POE, the traveler may be “referred” to a district health office near the traveler’s local address for follow-up by district health staff. After completing the data entry for Stage 1 (screening), the user would refer the TEI to a District Health Center. Read more about referrals in tracker in [DHIS2 User Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/tracking-individual-level-data/tracker-capture.html). + +![alt_text](resources/images/POE_image08.png "image_tooltip") + +### Program Relationships { #program-relationships } + +This program has the relationshipType ‘Has been in contact with’. Users can create a relationship between TEIs enrolled in the POE program and TEIs in other COVID-19 tracker programs (Case-based Surveillance, Contact Registration & Follow-up). The relationship can be added at any point in the program stages during data entry. + +### Program Rules { #program-rules } + +The following program rules have been configured. + +|Program Rule Name|Program Rule Description| +|--|--| +|Calculate and assign patient age in years|Calculate and assign patient age in years| +|Hide countries if not visited|Hide countries if not visited| +|Hide Follow-Up Stages|Hide Follow-Up Stages if the case is cleared at the port of entry| +|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)| +|Hide symptoms if no symptoms present (Follow Up within 14 days)|Hide symptoms if no symptoms present (Follow Up within 14 days)| +|Hide symptoms if no symptoms present (PoE)|Hide symptoms if no symptoms present (PoE)| + +You can read more about program rules here: +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +||| +|--|--| +|COVID-19 travelers screened|Total number of travelers screened and enrolled in screening program from POE| +|COVID-19 travelers cleared at POE|Number of travelers cleared after POE screening (no follow-up required)| +|COVID-19 travelers with symptoms at POE|Number of travelers presenting with symptoms during POE screening| +|COVID-19 travelers cleared after 14 days monitoring|Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period)| +|COVID-19 travelers referred to health facility|Number of travelers that were referred to a health facility at any time during 14 day followup| +|COVID-19 travelers enrolled for 14 day follow-up|Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| +|COVID-19 currently under follow-up|Number of travelers that have not been cleared or referred to a health facility| +|COVID-19 travelers developed symptoms during follow-up|Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)| +|COVID-19 % travelers developed symptoms during 14-day follow-up|Numerator: Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)
Denominator: Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| + +Users can also generate an Event Report to see: + +1. Travelers by nationality and/or originating country +2. Referrals to health facility + +## References { #references } + +* DHIS2 COVID-19 [Tracker Package Installation Guide](covid-19-tracker-installation.html) +* World Health Organisation (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) (interim guidance, published 19 March 2020) + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md new file mode 100644 index 00000000..d1bde3b7 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Points of Entry { #covid-19-points-of-entry } + +## Design { #design } + +[Version 1.0.2](#c19-poe-design) + +## Installation { #installation } + +[Installation Guide](#c19-poe-installation) + +## Release Note { #release-note } + +[Release Note](#c19-poe-release-note) + +## Metadata Reference { #metadata-reference } + +[Version 1.0.2](https://packages.dhis2.org/en/C19_POE/1.0.2/C19_POE_COMPLETE_1.0.2_DHIS2.37.xlsx) + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md new file mode 100644 index 00000000..b458a748 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -0,0 +1,164 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/c19_evt-design.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Surveillance Line-list Design { #c19-evt-design } + +Demo: [https://covid.dhis2.org](https://covid.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Surveillance Event Program System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## السياق{ #background } + +The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +|Type of Surveillance Package|Case-based Surveillance (Tracker)|Surveillance (Event)|Surveillance (Aggregate)| +|--|--|--|--| +|_Description_|Enrolls a case and tracks over time through laboratory confirmation & case outcome|Captures critical case details in line-listing format|Enables daily or weekly reporting of key aggregate data points| +|_Pros_|Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case|More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity|Low complexity, easy to implement, most manageable when cases numbers are high| +|_Cons_|Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation|Does not support case-follow up or other decentralized workflows|Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) + +**This document covers only the design of the surveillance event program package**; separate system design documents are available for DHIS2 Tracker and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +This package is designed as a DHIS2 [Event Program](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#about_event_program). **The Event Program is not designed to capture all data variables contained in the [WHO case reporting template](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx)**. To capture a complete set of WHO case reporting variables, please refer to the DHIS2 COVID-19 Case-based Surveillance Tracker. Rather, the event program is a simplified program that captures a subset of minimum critical data points to facilitate high data quality when the number of caseloads or burden of reporting exceeds capacity for successfully completing the full line-list for suspected COVID-19 cases. For implementers who wish to capture the complete WHO line-listing, please refer to the COVID-19 Case-based Surveillance Tracker Package. + +The COVID-19 Surveillance Event Program data package includes: + +1. Event program and data elements case reporting +2. Core indicators +3. Dashboard + +### Use Case: Simplified line-listing of COVID-19 cases { #use-case-simplified-line-listing-of-covid-19-cases } + +As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The event package is designed to capture the most critical data points in a line-list and analytical capacities for surveillance and response. The event package is designed as a standalone program. However, countries may use the event package in combination with other packages (i.e. event reports and daily aggregate reporting); or, they may shift from tracker to event to aggregate as caseloads and reporting burden increases. **_Countries should plan carefully how they intend to implement these packages in combination, including reporting flows, transitioning from one data model to another, and how to maintain historical data for analysis if transitioning between data models. _** + +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. + +#### Intended users { #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 + +#### Workflow { #workflow } + +Unlike the tracker program, there are limitations to decentralization of the data reporting workflow in an Event program. The most significant limitation is that the Case Outcome (recovery or death) is often not known until days or weeks after the case is reported. The current program design allows for the following workflow options: + +1. Event is created when a suspected case is reported. All known data is entered, but the event is not completed. A user can select an ‘Active Event’ from a working list based on User filters and criteria. When missing data becomes available (i.e. the case outcome), the user can enter the remaining data fields and complete the event. Cases can be identified in the event list by the Case ID data element. See the image below as an example which can be accessed within the Capture App: +![Capture App](resources/images/EVENT_image1.png "Capture App") + +2. Event is created. All case related data is entered retrospectively, including the Outcome. Event is completed. _The limitation is this approach is timeliness of the data reporting, as new suspected cases might not be captured until their outcome which is often too late for decision making._ + +### Program Structure { #program-structure } + +The program is called ‘COVID-19 Cases (events)’ + +|القسم|Description| +|--|--| +|Date of report|Event Date
_Countries may re-name the event date to apply to their protocols._| +|Section 1
**Basic Information**|Records basic demographic data.
_Countries may add data elements as desired._
- **Patient ID**
Can be used to filter events in working lists, eg. Active events
- **Sex**
- **Age**| +|Section 2
Case Details|Records information about the case including symptoms, severity, testing, etc.
- **Symptoms**
Options: Yes / No
Specifies whether a case has any symptoms at time of notification

- **Date of symptoms onset**
Only appears if symptoms are present;
Date of symptoms onset, if available, will replace “Date of Report” in data analytics and reporting.

- **Case Severity (at time of notification)**
Options: Mild / Moderate / Severe / Critical
- **Laboratory tested?**
Options: Yes / No/ Unknown
Specifies whether a case has been laboratory tested for COVID-19

- **Test Result**
Only appears if the case was laboratory tested
Options: Inconclusive / Positive / Negative / Unknown
The program is designed to capture only the final test result. Results for each individual test (if available) and the total number of tests performed are not captured.
- **Case Classification**
Options: Suspected case / Probable case / Laboratory confirmed case
Automatically assigned values
The values are assigned by Program rules in accordance with WHO case definitions
This feature can be useful in filtering active cases in the working lists.| +|Section 3
**Exposures**|- **Has the case traveled in the 14 days prior to symptoms onset?**
Options: Yes / No / Unknown
Specifies travel history of the case.

- **Likely Infection Source**
Options: Imported case* / Local Transmission / Exposure unknown
* Imported case option appears only if the case traveled in the 14 days prior to symptoms onset

- **Specify local source**
Only appears if Likely Infection Source is Local Transmission
Options: Community (workplace, public transport, etc.) / Household / Healthcare Facility / Close Contact with Other Infected Individual / Exposure Unknown

- **Case Type**
Options: New index case / Linked to existing cluster / Unknown
Specifies whether the case is connected to an existing cluster or is a new index case| +|Section 4
**Treatment**|- **Hospitalised**
Options: Yes / No

- **Did the case receive care in an intensive care unit (ICU)?**
Only appears if the case is hospitalised
Options: Yes / No| +|Section 5
**Contacts**|- **Total number of contacts followed for this case**
Records number of contacts| +|Section 6
**Outcome**|- **Health outcome**
Options: Recovered / Death| +|Section 7
**Assigned Date of onset of symptoms**|- **Calculated onset date (for Indicators)**
This section is used only to calculate indicators based on report date vs. date of onset of symptoms]
This automatically assigned date is used in program indicators. Initially, it is the report date. If the date of onset of symptoms is available, the date is replaced by the date of onset of symptoms.| +|**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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Currently, only users assigned to the COVID19 data capture group will have access to capture data in the program. Please refer to the installation guidance for more instructions. + +### Program Rules { #program-rules } + +The following program rules have been configured for the program: + +|Program Rule Name|Program Rule Description| +|--|--| +|Assign Empty Value to Class Classification|Automation: Assign Empty Value to Class Classification| +|Assign Event Date|Automation: Assign Event date if to onset date if no Onset date is available| +|Assign 'Laboratory Confirmed Case' to Case Classification|Automation: Assign 'Laboratory Confirmed Case' to Case Classification| +|Assign Onset Date|Automation: Assign Symptoms Onset Date if available| +|Assign 'Probable Case' to Case Classification|Automation: Assign 'Probable Case' to Case Classification| +|Assign 'Suspected Case' to Case Classification|Automation: Assign Suspected Case' to Case Classification| +|Hide Case Classification Field|Hide Case Classification Field until Lab Test question is answered| +|Hide ICU field|Hide ICU field unless Hospitalised| +|Hide 'Imported Case'|Hide 'Imported Case' if not traveled| +|Hide Onset of Symptoms Date|Hide Onset of Symptoms Date if no symptoms| +|Hide Outcome Options|Hide irrelevant Outcome Options| +|Hide 'Specify Local Infection Source'|Hide 'Specify Local Infection Source' unless Local Transmission is selected| +|Hide Test Result Field|Hide Test Result Field until Lab Test question is answered with yes| +|Hide Test Result Options|Hide Irrelevant Test Result Options| +|Hide Unknown Options|Hide Irrelevant Unknown Options| + +You can read more about program rules here: + +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +From the data captured in the COVID-19 line-listing program, we can calculate the following indicators, including those recommended by the WHO for daily and weekly reporting, present them in a dashboard. All COVID-19 program indicators based on the event program are assigned to the Program Indicator Group ‘COVID-19 Events.’ + +||| +|--|--| +|COVID-19 - Cases admitted in intensive care unit (ICU)|COVID-19 Cases admitted in intensive care unit (ICU)| +|COVID-19 - Cases exposed through healthcare facility|Cases where infection is suspected to have occurred in a health care setting| +|COVID-19 - Cases infected by community transmission|Cases where infection is suspected to have occurred through community spread| +|COVID-19 - Cases infected by household transmission|Cases where infection is suspected to have occurred within the household| +|COVID-19 - Cases infected by local transmission|Cases where infection is suspected to have occurred locally, not in another country| +|COVID-19 - Cases infected through other contact with other infected individual|Cases where infection is suspected to have occurred through other close contact with an infected individual (excluding those listed: household, known cluster, HCF)| +|COVID-19 - Cases linked to known cluster|Cases where infection is suspected to have occurred by linkage to a known cluster of cases| +|COVID-19 - Cases with unknown exposure|Cases where source of infection or exposure is unknown| +|COVID-19 - Deaths|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 - Confirmed Hospitalised Cases|Number of confirmed cases that were admitted into hospital| +|COVID-19 - Imported Cases|Cases where likely source of infection is recorded as another country or imported from another country.| +|COVID-19 - Laboratory confirmed cases|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by report date| +|COVID-19 - Laboratory confirmed cases - by onset of symptoms|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by date of onset of symptoms| +|COVID-19 - Laboratory tested cases|Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)| +|COVID-19 - Probable cases|Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date| +|COVID-19 - Probable cases - by onset of symptoms|Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms| +|COVID-19 - Recovered cases|Number of cases that are recovered (By date of onset of symptoms)| +|COVID-19 - Suspected cases|Total number of cases suspected with COVID-19, by report date| +|COVID-19 - Suspected cases - by onset of symptoms|Total number of cases suspected with COVID-19, by date of onset of symptoms| +|COVID-19 - Suspected cases not tested|Total number of suspected cases without a lab result| +|COVID-19 Event - case fatality rate|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 Deaths by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Confirmed cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Suspected cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| + +## References { #references } + +* [COVID-19 Surveillance, Response & Vaccine Delivery Toolkit](https://dhis2.org/covid-19) +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form +[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md new file mode 100644 index 00000000..243bc1c0 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md @@ -0,0 +1,13 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Surveillance Events { #covid-19-surveillance-events } + +## Design { #design } + +[Version 0.3.2](#c19-evt-design) + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md new file mode 100644 index 00000000..2d1d5128 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md @@ -0,0 +1,22 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_surveillance-digital_data_package-2022.md" +revision_date: '2023-09-01' +tags: +- Implement +--- + +# COVID-19 Surveillance { #covid-19-surveillance } + +DHIS2 released a digital metadata package to accelerate case detection, situation reporting, active surveillance and response for COVID-19. The design is inspired by the Ministry of Health Sri Lanka’s pioneering use of DHIS2 tracker for COVID-19 case detection and draws on years of collaboration with the World Health Organisation (WHO) to develop information system standards for case-based disease surveillance. The COVID-19 digital data package includes standard metadata aligned with the WHO’s [technical guidance on COVID-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and implementation guidance to enable rapid deployment in countries. + +The design of these modules can be adapted, modified and reused for new and emerging infectious disease threats to strengthen health emergency preparedness and response systems in countries. + +## COVID-19 Surveillance Modules { #covid-19-surveillance-modules } + +DHIS2 supports surveillance workflows and automated analysis for key components of routine and active surveillance: + +* **COVID-19 Case Surveillance tracker**: enrolls & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. +* **Contact Registration & Follow-up tracker**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. +* **Ports of Entry Screening & Follow-up tracker**: enrols travellers who have visited high-risk locations at Ports of Entry for 14-day monitoring and follow-up. +* **COVID-19 Aggregate Situation Reports**: an aggregate reporting dataset that captures minimum necessary data points for daily or weekly reporting and includes key information for generating situation reports. + diff --git a/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..27d88ae2 --- /dev/null +++ b/projects/docs-full-site/ar/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implement +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Overview { #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/cs/.cache_timestamp b/projects/docs-full-site/cs/.cache_timestamp index e07f8dcd..f89f5c8d 100644 --- a/projects/docs-full-site/cs/.cache_timestamp +++ b/projects/docs-full-site/cs/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:20:08Z \ No newline at end of file +2024-10-19T21:19:39Z \ 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 4b19a590..d541a2aa 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 fde4c28f..6d584ac1 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 750202da..6b7340fd 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 15c45ae1..df98c83f 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 d46ac814..907a76c1 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 2f72f085..9cdb23c3 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 96d0b22d..c721c6bd 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 2affff31..30423781 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 c2f0e2a3..6bbbde9d 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 4aea8381..86a4bb71 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 1dfca2c9..838e6e56 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # Ú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 f6d15e2a..18d659b2 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 15cd049d..2f7cf11e 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 d4ad339c..a9f7d958 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 6531dc56..dc2671e3 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 b2a98441..a2595b7b 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 0d9fa5a8..e4c45696 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 993769a2..0c6df765 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 f5765e41..dfdd820b 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 9b9e2b8e..e1b15ad3 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 843d6c4c..bbceba1b 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 57fdc78d..500da49b 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 efb81c29..d70bcac6 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # 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 509ce5c2..03a669f8 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: -- DHIS core version 2.38 - Vývoj +- DHIS core version 2.38 --- # Vizualizace { #visualizations } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md index 0bb9d408..b0960017 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Analytika { #analytics } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md index 46c9a4e0..2c097cc9 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md index d7e96e58..4a28ad25 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Schválení dat { #data-approval } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md index 6bdef57a..029b87dc 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Data { #data } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md index 71c92dc6..a3506b48 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-validation.md" revision_date: '2022-06-21' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Ověření dat { #data-validation } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md index d58c25a7..19329332 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # I18n { #i18n } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md index 310730a0..da95dc17 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/overview.md" revision_date: '2023-05-03' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Přehled { #webapi } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md index c163be1e..08540010 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Zprávy { #messaging } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md index 72452278..3f195e99 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md index bc5e3a45..6c0bb831 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata.md" revision_date: '2023-08-03' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Metadata { #metadata } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md index 584e7568..0af1034a 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/scheduling.md" revision_date: '2022-09-13' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Plánování { #webapi_scheduling } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md index 7e5a6333..2651eb0b 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Sdílení { #sharing } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md index 0b72ae4d..6be8ba33 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # SMS { #sms } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md index 70d50492..e8c8355c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS základní verze 2.39 - Vývoj +- DHIS základní verze 2.39 --- # Vizualizace { #visualizations } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md index d09755d7..d0fcf6eb 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Analytika { #analytics } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md index 967fbb4e..0ae0763c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Aplikace { #apps } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md index 7e6a859c..ac990b3c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md index f43a65bd..931f9207 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Schválení dat { #data-approval } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md index 84f06765..29dd5bd2 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md index f2690627..e8d1d0b2 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Výměna dat { #data-exchange } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md index 45c53219..bc46ec12 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Data { #data } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md index 5b421c5a..37afa1d0 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Data store { #data-store } 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 b0d2c624..fc951d81 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 76395c31..1cd577cf 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__event-hooks-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index 22e257f7..353f7aab 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md index 0fde080b..a2121632 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # I18n { #i18n } 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 333e8d9b..27677ec1 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__maintenance-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md index c8aa9ffa..083f0396 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Údržba { #maintenance } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md index b66868ea..67423c35 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Zprávy { #messaging } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index 78dae008..31cb4045 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index 449e89e3..5492dd0b 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Metadata { #metadata } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md index e2f1e53d..cf13df54 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Profil organizační jednotky { #org_unit_profile } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 6bc6f728..0bcb86a3 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md index 014c7f9c..e78fd002 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Plánování { #webapi_scheduling } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index 7f22482e..5b0453b9 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Nastavení a konfigurace { #settings-and-configuration } 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 b9727597..7d91ea0c 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__sms-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md index f7b2ae2a..d46397c3 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # SMS { #sms } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md index 3c3b3128..d3feb49f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Synchronizace { #webapi_synchronization } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md index 7bfbe64f..7d094f7f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md +++ b/projects/docs-full-site/cs/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 základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } 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 042d1d58..5e24a923 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS základní verze 2.40 - Vývoj +- DHIS základní verze 2.40 --- # Trasovač { #tracker } 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 b8a6a910..96344d6f 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 f96660ff..37b355e0 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__analytics-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md index 27397c14..58726452 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/analytics.md" revision_date: '2024-05-02' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Analytika { #analytics } 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 f0144ad6..e7a4cbb6 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: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # 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 2f8aa746..62fb989c 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: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # 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 259486ad..806a6f71 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: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # 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 6139b084..8cbf10e1 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: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md index 0cd7c672..dfa48da2 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-exchange.md" revision_date: '2024-06-26' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Výměna dat { #data-exchange } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md index 7647d933..5f77b9d2 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Data { #data } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md index 47e5a25f..c237512a 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Data store { #data-store } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md index b8ab3cd5..311befd2 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Ověření dat { #data-validation } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md index 5f1743c7..b84dabe3 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # E-mail { #email } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md index d841ec1c..97bafebf 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md index 9ec82064..10f6e3f6 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # I18n { #i18n } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md index b6f120ed..e8737c81 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Přehled { #webapi } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md index 93029fd9..50a55038 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Údržba { #maintenance } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md index 0881d250..71d35437 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Zprávy { #messaging } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md index 0947b6c8..de378c53 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md index 81d41351..eea6993f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Metadata { #metadata } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md index 9b5702c2..5f377385 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Profil organizační jednotky { #org_unit_profile } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md index 667734cb..675ff5eb 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md index ef85d4c3..21027f26 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/route.md" revision_date: '2024-09-24' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Route { #route } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md index a7b2f0d0..fefcd45b 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Plánování { #webapi_scheduling } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md index 8fecb2a3..ea54aefb 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Nastavení a konfigurace { #settings-and-configuration } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md index e1ff12b0..bc78ce0a 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Sdílení { #sharing } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md index e613184f..e22f5d45 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # SMS { #sms } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md index 9fce2ccd..e6ccfa7d 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Synchronizace { #webapi_synchronization } 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 11f11551..4dffd11d 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: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md index d0dcb586..e4aa3fe9 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Trasovač { #tracker } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md index d42ee467..1013c91d 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md +++ b/projects/docs-full-site/cs/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 - Vývoj +- DHIS core version 2.41 --- # Uživatelé { #users } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md index af384b93..8f80646f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- DHIS core version 2.41 - Vývoj +- DHIS core version 2.41 --- # Vizualizace { #visualizations } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index 4c93d5ec..ad94026f 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/cs/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-07-26' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Analytika { #analytics } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index 136cff87..e3409e7e 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Aplikace { #apps } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index fc6fc984..dc868557 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 3dc794d5..17e1b67b 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Schválení dat { #data-approval } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index b79a6fe6..93114bac 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index 15b5d430..1ed31c55 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/cs/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-09-18' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Výměna dat { #data-exchange } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index b3884ff4..e730acec 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Data { #data } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index 6cd4cfc5..705e79c9 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Data store { #data-store } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index 9e852fe1..71c24c89 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Ověření dat { #data-validation } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index d31c07b5..cb7951ad 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 99ccd4e5..119f7195 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # I18n { #i18n } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index 494974f2..a3ce8322 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Přehled { #webapi } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index ac98e0dc..602523d9 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Údržba { #maintenance } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md index 1baa747e..6bb6e2e6 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Zprávy { #messaging } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index 5e9ea152..c11d3147 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index bba3235b..63941d0b 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-07-29' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Metadata { #webapi_metadata } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index 9c293b3b..7b4ed83c 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index 78a1ef19..f006c65e 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Route { #route } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index adf476d7..b9110ae0 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Plánování { #webapi_scheduling } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index 1b6d4969..3277fe77 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Nastavení a konfigurace { #settings-and-configuration } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index 1a7595ca..b45b7c47 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Sdílení { #sharing } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 780be007..2fcc9bb9 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # SMS { #sms } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index 031d4252..a4fce5a7 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Synchronizace { #webapi_synchronization } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index f0e38d97..0b262cba 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/cs/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-09-13' tags: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Uživatelé { #users } diff --git a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index 34298efa..7ec239c4 100644 --- a/projects/docs-full-site/cs/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/cs/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: -- Vývoj - Hlavní verze jádra DHIS +- Vývoj --- # Vizualizace { #visualizations } diff --git a/projects/docs-full-site/cs/IMPLEMENT__DATA-USE__data-visualization-md b/projects/docs-full-site/cs/IMPLEMENT__DATA-USE__data-visualization-md index 904f5343..84901cc2 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__DATA-USE__data-visualization-md +++ b/projects/docs-full-site/cs/IMPLEMENT__DATA-USE__data-visualization-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/data-use/data-visualization.md" -revision_date: '2024-10-17' +revision_date: '2024-10-18' tags: - Implementace --- @@ -27,9 +27,9 @@ Understanding these categories is essential to selecting the correct chart type - **Ordinal** - Categories with a meaningful order (e.g., disease status). These categories have a logical sequence. - For example, disease severity might be classified as mild, moderate, and severe, which has an inherent order. -> **Note**: +> **Note** > ->**Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. +> **Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. ![Variable categories](resources/images/dataviz_001.png) @@ -46,7 +46,7 @@ What’s the best way to choose the right visualization for the data at hand? [F Another Chart Chooser is mapped in the [Extreme Presentation Method](https://extremepresentation.com/). -![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.png) +![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.jpg) The summary below is based on the visualizations available in the core DHIS2 Data Visualizer App. @@ -93,9 +93,9 @@ The summary below is based on the visualizations available in the core DHIS2 Dat ### Specific Visualization Styles { #specific-visualization-styles } ->**Note** +> **Note** > ->**Data speaks louder than words!** +> **Data speaks louder than words!** In data visualization, choosing the right type of chart or graph is crucial for effectively communicating your data. Each visualization style has its strengths and is best suited for specific types of data and analytical purposes. This chapter explores a variety of visualization styles, detailing their applications and best practices. Whether you're looking to show trends over time, compare quantities, highlight correlations, or illustrate parts of a whole, selecting the appropriate visualization method will enhance clarity and insight. By understanding the nuances of each style, you can ensure that your data tells a compelling and accurate story. @@ -103,9 +103,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Correlation { #correlation } ->**Note** +> **Caution** > ->Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. +> Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. - **Scatterplot**: Shows the relationship between two continuous variables, each having its axis. Each point represents an observation's values on the two variables. It's useful for identifying trends, clusters, and outliers. For example, a scatterplot can display the relationship between the number of immunization campaigns conducted in various districts and the resulting immunization coverage rate. @@ -118,9 +118,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Ranking { #ranking } ->**Note** +> **Note** > ->Emphasizes the item's position in an ordered list rather than the absolute value. +> Emphasizes the item's position in an ordered list rather than the absolute value. - **Ordered bars/columns**: Shows ranks of values more easily when sorted. This visualization helps to quickly see the highest and lowest values. An ordered bar column chart can be used to display the number of TB cases in each district, sorted in descending order to highlight the districts with the highest burden. @@ -132,9 +132,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Change Over Time { #change-over-time } ->**Note** +> **Note** > ->Keep gaps between columns small to highlight data shape. +> Keep gaps between columns small to highlight data shape. Use markers for irregular data points. - **Column**: Emphasizes changing trends. Columns are used to show discrete data points over time. For example, monthly case figures can be shown as a column chart. @@ -152,9 +152,9 @@ Use markers for irregular data points. #### Magnitude { #magnitude } ->**Note** +> **Note** > ->Small gaps highlight data shape. Best for a single series of data. +> Small gaps highlight data shape. Best for a single series of data. - **Column/Paired column/bar**: Compare sizes, usually numbers rather than rates or percentages. For instance, HIV case figures for different regions can be compared using a bar chart. In this case, it is appropriate to keep the distance between the columns as they represent separate entities rather than variables through time. @@ -168,9 +168,9 @@ Use markers for irregular data points. #### Part-to-Whole { #part-to-whole } ->**Note** +> **Tip** > ->Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** +> Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** ![Imrpove the visualization choosing the most suitable colour set](resources/images/dataviz_022.png) @@ -206,9 +206,9 @@ Stacked columns or bar charts **should be avoided when** a detailed comparison o - **Choropleth**: Standard for rates on maps. Uses varying shades of a colour to represent data values for different regions. For example, population density by region can be shown using a choropleth map. ->**Note** +> **Note** > ->**Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. +> **Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. ![Map showing the percentage of PTB-BC cases in a region](resources/images/dataviz_013.png) @@ -287,9 +287,9 @@ A visualization should always have: ![Contextualized graph](resources/images/dataviz_024.png) ->**Note**: +> **Caution** > ->Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. +> Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. #### Pie Chart { #pie-chart } diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md new file mode 100644 index 00000000..80e4c203 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -0,0 +1,206 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-design.md" +revision_date: '2023-03-31' +tags: +- Implementace +--- + +# COVID-19 Surveillance - Aggregate System Design Guide { #c19-agg-design } + +## Účel { #purpose } + +Dokument COVID-19 Surveillance Aggregate System Design poskytuje přehled principů návrhu a pokynů použitých k vývoji balíčku digitálních dat pro souhrnný dohled COVID-19. Tento dokument je určen k použití implementátory DHIS2 na národní a regionální úrovni, aby mohli podporovat implementaci a lokalizaci balíčku. Balíček metadat COVID-19 lze přizpůsobit místním potřebám a národním pokynům. Při lokalizaci a přijímání programů obsažených v tomto balíčku by měly být brány v úvahu zejména místní pracovní toky a národní pokyny. + +## Pozadí { #background } + +Tento agregovaný design byl aktualizován, aby odrážel nové požadavky na souhrnné hlášení z [Global surveillance of COVID-19: WHO process for reporting aggregated data](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form), naposledy aktualizováno 7. srpna 2020. Balíček digitálních dat COVID-19 byl vyvinut v reakci na výslovnou potřebu zemí rychle přizpůsobit řešení pro správu dat COVID-19. UiO vyvinula trasovací balíčky COVID-19 pro tři typy datových modelů (trasovač, agregace založené na událostech), aby umožnila zemím vybrat model, který je nejvhodnější pro jejich kontext s ohledem na zátěž nemocí a dostupné zdroje. Níže jsou shrnuty tyto modely a jejich relativní výhody / omezení: + +| **Typ sledovacího balíčku** | **Sledování na základě případu (Trasovač)** | **Řádkový výpis sledování událostí (událost)** | **Sledování případů (souhrn)** | +| --- | --- | --- | --- | +| **Popis** | Zapište případ a sleduje časem laboratorní potvrzení a výsledek případu | Zachycuje podrobnosti kritických případů ve formátu seznamu řádků | Umožňuje týdenní hlášení klíčových agregovaných datových bodů | +| **Výhody** | Vysoce strukturovaná data a více časových dimenzí pro analýzu mohou podporovat decentralizovaný pracovní postup, všechny události spojené s případem | Podrobnější než agregované a dokáže zachytit klíčové časové dimenze (tj. Datum zprávy vs. nástup příznaků); snížená zátěž při zadávání dat ve srovnání se trasovačem a malá složitost | Nízká složitost, snadná implementace, zvládnutelnost, když je počet případů vysoký | +| **Nevýhody** | Břemeno zadávání dat může být ohromující, když počet případů dosáhne prahové hodnoty; složitost implementace | Nepodporuje sledování případů ani jiné decentralizované pracovní postupy | Menší podrobnost pro podrobnou analýzu (tj. Analýza pouze na základě data hlášení případu, omezené členění)| + +**Tento dokument se týká pouze designu agregovaného balíčku**; pro balíčky DHIS2 Tracker a Line-listing (založené na událostech) jsou k dispozici samostatné dokumenty o návrhu systému. Vzhledem k rychlému nárůstu případů mohou některé země bojovat s podáváním zpráv podle jednotlivých případů, protože zátěž je příliš vysoká. Agregovaný balíček je navržen tak, aby splňoval nejkritičtější požadavky na podávání zpráv a analytické kapacity pro dohled a reakci. + +Cíle dozoru COVID-19 jsou: + +1. sledovat trendy choroby, při které dochází k přenosu z člověka na člověka; +2. rychle odhalit nové případy v zemích, kde virus necirkuluje; +3. a poskytovat epidemiologické informace k provádění hodnocení rizik na národní, regionální a globální úrovni; a +4. poskytovat epidemiologické informace jako vodítko pro opatření připravenosti a reakce. + +Návrh systému vychází ze stávajících zásad dozoru nad chorobami a požadavků na informační systém, které byly vyvinuty ve spolupráci WHO a UiO od roku 2017. Balíček COVID-19 byl vyvinut s úmyslem sladit s [technickými pokyny WHO pro dozor a definice případů nCoV-19](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), naposledy aktualizováno 7. srpna 2020. Upozorňujeme, že tento návrh nemusí nutně odrážejí nejnovější dostupné prozatímní globální pokyny vyvinuté WHO, protože aktualizace mohou být vydávány rychle. Národní směrnice a zásady se mohou lišit a doporučuje se přizpůsobit tento balíček místním kontextům. + +## Souhrn návrhu systému { #system-design-summary } + +Při vývoji tohoto konfiguračního balíčku bylo vyvinuto úsilí dodržovat [obecné zásady návrhu](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) UiO a společnou [konvenci pojmenování](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +Souhrnný balíček dozoru COVID-19 obsahuje + +1. Týdenní souhrnná datová sada a datové prvky pro klíčové sledovací zprávy COVID-19 +2. Kategorie pro členění dat +3. Základní indikátory +4. Ovládací panel a jeho položky + +Datová sada zachycuje minimální počet datových bodů, které splňují aktuální požadavky WHO na týdenní podávání zpráv; a vygenerovat základní sadu indikátorů a ovládacích panelů pro rozhodovací orgány na národní i nižší úrovni, aby rychle analyzovaly a reagovaly na trendy v nemoci. + +| **Název** | **Periodicita** | **Účel** | +| --- | --- | --- | +| Souhrnný týdenní dohled | Týdně| Hlášení klíčových údajů z trasování COVID-19 včetně případů, testů a úmrtí. | + +Doporučuje se, aby byl týdenní datový soubor přiřazen organizačním jednotkám na nejnižší úrovni zdravotnického systému, který je vhodný pro vykazování údajů, jako jsou zdravotnická zařízení. + +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). + +### Předpokládaní uživatelé { #intended-users } + +- Uživatelé zdravotnických zařízení: zachyťte a nahlaste klíčová data o případech a úmrtích COVID-19 ve zdravotnickém zařízení +- Dozorčí úředníci: dozorčí úředníci na národní a nižší než národní úrovni mohou být odpovědní za podporu zadávání a analýzy údajů. +- Národní a místní zdravotní úřady: monitorují a analyzují údaje o sledování nemocí prostřednictvím ovládacích panelů a analytických nástrojů k provádění hodnocení rizik a plánování opatření reakce; generovat zprávy pro regionální a globální zprávy + +## Datové sady { #datasets } + +Tento soubor dat je určen k zachycení týdenních dat potřebných pro rychlou reakci na přenos nemoci. Pokud se zpravodajské břemeno stane příliš velkým nebo když již nebude považováno za nouzovou situaci v zemi, může být soubor dat změněn na měsíční podle zásad Ministerstva Zdravotnictví. + +### Daily Surveillance Data Elements { #daily-surveillance-data-elements } + +V následující části jsou uvedeny datové prvky a členění (kombinace kategorií) obsažené v datové sadě: + +| **Datové prvky** | **Kombinace kategorií** | +| --- | --- | +| Nové potvrzené případy | Pohlaví (Muž / Žena / Neznámé) a Věk (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+, neznámý věk) | +| Nové pravděpodobné případy | Pohlaví (Muž / Žena / Neznámé) a Věk (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+, neznámý věk) | +| Nové potvrzené úmrtí | Pohlaví (Muž / Žena / Neznámé) a Věk (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+, neznámý věk) | +| Nové pravděpodobné úmrtí | Pohlaví (Muž / Žena / Neznámé) a Věk (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+, neznámý věk) | +| Nové hospitalizované případy | Žádný | +| Nové propuštěné případy | Žádný | +| Nové případy mezi zdravotníky (potvrzeny + pravděpodobné) | Žádný | +| Nová úmrtí zdravotnických pracovníků (potvrzeno + pravděpodobné) | Žádný | +| Počet osob testovaných na COVID-19 | Žádný | +| Počet osob testovaných pomocí PCR testu | Žádný | +| Klasifikace přenosu | Žádný | + +### Weekly Surveillance Data Entry Form { #weekly-surveillance-data-entry-form } + +- **Část 1: Nové potvrzené a pravděpodobné případy** + +Data should be entered for all new confirmed and probable cases reported during the reporting period. Confirmed cases refer to laboratory confirmed cases per WHO guidance; probable cases are defined by WHO as cases where laboratory test result is inconclusive; however countries may apply their own case definitions. The total column is automatically summed during data entry. +![Picture1](resources/images/AGG_Picture1.png) + +- **Část 2: Nová potvrzená a pravděpodobná úmrtí** + +Je třeba zadat údaje o nových potvrzených a pravděpodobných úmrtích hlášených během sledovaného období. Během zadávání dat se sloupec součtu automaticky sčítá. + +![Obrázek2](resources/images/AGG_Picture2.png) + +- **Část 3: Infekce a úmrtí zdravotnických pracovníků** + +Tato část zachycuje data pro zdravotnické pracovníky' nové potvrzené a pravděpodobné případy, včetně úmrtí hlášených během sledovaného období. + +![Obrázek3](resources/images/AGG_Picture3.png) + +- **Ćást 4: Hospitalizace a propuštění** + +Tato část obsahuje údaje o nové hospitalizaci a propuštění během sledovaného období. + +![Obrázek4](resources/images/AGG_Picture4.png) + +- **Část 5: Provedené testy** + +Tato část obsahuje údaje pro testy prováděné s dalším požadavkem na hlášení testů prováděných pomocí PCR během vykazovaného období + +![Obrázek5](resources/images/AGG_Picture5.png) + +- **Část 6: Klasifikace přenosu** + +Tato část shrnuje hlavní formu klasifikace přenosu, se kterou se setkává nahlašovací jednotka. + +![Obrázek7](resources/images/AGG_Picture6.png) + +### Přizpůsobení formulářů pro zadávání dat { #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) + +## Data Validation { #data-validation } + +Byly nakonfigurovány následující pravidla ověřování dat. Tato ověřovací pravidla se nespouštějí v samotném formuláři pro zadávání údajů, protože se očekává, že bude naléhavé hlášení údajů, kde k událostem dochází v různých časových rámcích (např. Za jeden týden lze zaznamenat pouze 3 nové případy, ale 5 úmrtí). + +| **Název** | **Operátor** | **Návod** | **Popis na levé straně** | **Popis na pravé straně** | +| --- | --- | --- | --- | --- | +| COVID19 - PCR testy \<= testováno | less\_than\_or\_equal\_to | Testováno pomocí PCR by mělo být menší nebo rovné celkovému provedenému testu | Testováno pomocí PCR | Testováno provedeno | +| COVID19 - Nové případy hospitalizace \<= Všechny nové případy | less\_than\_or\_equal\_to | Nové hospitalizované případy by měly být menší nebo rovny všem novým případům | Nové případy hospitalizovány | Všechny nové případy | +| COVID19 - Nové potvrzené úmrtí \<= Nové potvrzené případy | less\_than\_or\_equal\_to | Nové potvrzené úmrtí by mělo být menší nebo rovno novým potvrzeným případům | Nové potvrzené úmrtí | Nové potvrzené případy | +| COVID19 - Pravděpodobná úmrtí \<= Nové pravděpodobné případy | less\_than\_or\_equal\_to | Pravděpodobná úmrtí by měla být menší nebo rovna novým pravděpodobným případům | Pravděpodobná úmrtí | Nové pravděpodobné případy | +| COVID19 - Nová úmrtí mezi zdravotním personálem (potvrzená + pravděpodobná) \<= Všechna úmrtí hlášena | less\_than\_or\_equal\_to | Nová úmrtí mezi zdravotním personálem (potvrzená + pravděpodobná) by měla být menší nebo rovna všem hlášeným úmrtím | Nové úmrtí mezi zdravotním personálem (potvrzeno + pravděpodobné) | Všechna úmrtí hlášena | +| COVID19 - Nové případy mezi zdravotním personálem (potvrzené + pravděpodobné) \<= Všechny nové případy | less\_than\_or\_equal\_to | Nové případy mezi zdravotním personálem (potvrzené + pravděpodobné) by měly být menší nebo stejné jako všechny nové případy | Nové případy mezi zdravotním personálem (potvrzeno + pravděpodobné) | Všechny nové případy | +| COVID19 - Nové úmrtí mezi zdravotním personálem (potvrzeno + pravděpodobné) \<= nové případy mezi zdravotním personálem (potvrzeno + pravděpodobné) | less\_than\_or\_equal\_to | Nová úmrtí mezi zdravotním personálem (potvrzená + pravděpodobná) by měla být menší nebo rovna novým případům mezi zdravotním personálem (potvrzená + pravděpodobná) | Nové úmrtí mezi zdravotním personálem (potvrzeno + pravděpodobné) | Nové případy mezi zdravotním personálem (potvrzeno + pravděpodobné) | + +## Skupiny uživatelů { #user-groups } + +V balíčku metadat jsou zahrnuty následující skupiny uživatelů: + +1. Správce COVID19 - je určen pro správce systému, aby měli práva upravovat metadata +2. Zachycení dat COVID19 - je určeno pro zaměstnance zadávající data, aby měli přístup ke shromažďování dat +3. Přístup COVID19 - určený pro uživatele, jako jsou analytičtí uživatelé, kteří by měli být schopni zobrazit data, ale ne upravovat metadata. + +Další informace naleznete v [instalačních pokynech](covid-19-aggregate-installation.html). + +## Indikátory { #indicators } + +Ze zachycených údajů můžeme vypočítat alespoň následující ukazatele, z nichž mnohé WHO doporučuje pro [týdenní hlášení](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) a představte je na ovládacím panelu. Všechny indikátory programu COVID-19 jsou přiřazeny skupině indikátorů 'COVID19'. + +| **název** | **popis** | +| --- | --- | +| COVID19 - Nové potvrzené úmrtí | Počet nově potvrzených úmrtí | +| COVID19 - Nové případy mezi zdravotním personálem (potvrzeno + pravděpodobné) | Počet nových případů mezi zdravotním personálem (potvrzeno + pravděpodobné) | +| COVID19 - podíl zdravotního personálu mezi hlášenými případy (%) | Podíl zdravotního personálu mezi hlášenými případy (%) | +| COVID19 - Aktivní případy | Počet aktivních případů | +| COVID19 - uzavřené případy | Počet uzavřených případů | +| COVID19 - Nové potvrzené případy | Počet nových potvrzených případů | +| COVID19 - Míra zotavení (%) | Míra vymáhání potvrzených případů | +| COVID19 - Míra úmrtnosti mezi zdravotním personálem (%) | Míra úmrtnosti mezi zdravotním personálem | +| COVID19 - Nové hospitalizované případy | Nové hospitalizované případy | +| COVID19 - Testováno | Celkový počet provedených testů | +| COVID19 - testováno pomocí PCR | Testováno pomocí PCR | +| COVID19 - Míra pozitivity (%) | Míra pozitivity | +| COVID19 - Nové pravděpodobné případy | Počet nových pravděpodobných případů | +| COVID19 - Nové vybité případy | Počet nových propuštěných případů | +| COVID19 - Nové úmrtí mezi zdravotním personálem (potvrzeno + pravděpodobné) | Počet nových úmrtí mezi zdravotním personálem (potvrzeno + pravděpodobné) | +| COVID19 - podíl testů PCR (%) | Podíl provedených testů PCR | +| COVID19 - Všechny případy (Potvrzeno + Pravděpodobné) | Počet všech případů (potvrzeno + pravděpodobné) | +| COVID19 - Nové pravděpodobné úmrtí | Počet nových pravděpodobných úmrtí | +| COVID19 - Míra úmrtnosti (%) | Míra úmrtnosti případů u potvrzených případů | + +## Ovládací panely { #dashboards } + +Klíčové analytické položky byly nakonfigurovány a přidány na řídicí panel „COVID19 - Aggregate Weekly Surveillance“. Mezi tyto položky patří; kontingenční tabulky, grafy a mapa navržené tak, aby poskytovaly vizualizaci dat u některých dat zachycených na základě indikátorů. V procesu přijetí tohoto balíčku mohou uživatelé upravovat nebo vytvářet další položky, které vyhovují jejich analytickým potřebám, a stejně provádět nezbytné úpravy na ovládacím panelu. + +| **název**|**typ**| +| --- | --- | +|COVID19 - Testováno, testy s PCR a míra pozitivity podle subnárodní úrovně v letošním roce |Kontingenční tabulka| +|COVID19 - HW mezi hlášenými případy v tomto roce |Graf| +|COVID19 - Míra úmrtnosti mezi zdravotním personálem.|Graf| +|COVID19 - Nové potvrzené případy a úmrtí za posledních 12 týdnů|Graf| +|COVID19 - provedeny kumulativní testy, hlášené případy, hospitalizováni, propuštěni a úmrtí|Graf| +|COVID19 - kumulativní potvrzené případy na subnárodní úrovni|Mapa| +|COVID19 - Úmrtí podle věkových skupin za poslední týdny|Graf| +|COVID19 - Potvrzené případy podle pohlaví za posledních 14 týdnů|Graf| +|COVID19 - Uzavřené a aktivní případy na subnárodní úrovni v posledních měsících|Graf| +|COVID19 - Míra zotavení a úmrtnost za posledních 12 týdnů|Graf| +|COVID19 - Aktivní a uzavřené případy posledních 12 týdnů|Graf| + +## Reference { #references } + +- Pokyny k instalaci: [https://www.dhis2.org/covid-19](covid-19-aggregate-installation.html) +- WHO Interim guidelines on nCoV-19 surveillance & case definitions (last updated March 20, 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions>]() +- WHO COVID-19 surveillance data dictionary (v6) +[https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98\_2](https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2) +- WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) + [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +- Zprávy o situaci koronaviru WHO + [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports>]() +- Global surveillance of COVID-19: WHO process for reporting aggregated data +[https://www.who.int/publications/i/item/aggregated-weekly-reporting-form](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md new file mode 100644 index 00000000..f3efd2a7 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-installation.md" +revision_date: '2022-11-07' +tags: +- Implementace +--- + +# Aggregate Package Installation Guide { #c19-agg-installation } + +## Přehled { #overview } + +Tento dokument je určen pro průvodce správci procesem instalace standardního konfiguračního balíčku COVID-19 pro DHIS2 pro agregované hlášení. Vyžaduje se dobré porozumění DHIS2. + +Konfigurační balíčky pro DHIS2 se skládají ze souboru metadat ve formátu [JSON] (https://en.wikipedia.org/wiki/JSON), který lze importovat do instance DHIS2, a také z průvodní dokumentace. Balíček poskytuje předdefinovaný standardní obsah podle doporučení WHO. Tento dokument se týká kompletních balíčků, které obsahují konfigurace sběru dat (datové sady, datové prvky, pravidla ověřování) a také analýzy a ovládací panely (oblíbené grafy, mapy a kontingenční tabulky). Toto je určeno pro použití tam, kde není nakonfigurován žádný sběr dat v DHIS2, nebo pokud nahrazujete / revidujete stávající obsah, aby odpovídal doporučením WHO. + +Konfigurační balíčky se skládají ze 4 hlavních komponent: + +* datové soubory s datovými prvky; +* soubor indikátorů; +* analytické výstupy (kontingenční tabulka, datový vizualizér a oblíbené GIS); a +* sada ovládacích panelů. + +Všechny tyto komponenty jsou propojené, tj. Indikátory vycházejí ze zahrnutých datových prvků, analytické výstupy vycházejí ze zahrnutých indikátorů a ovládací panely jsou tvořeny zahrnutými analytickými výstupy. + +## Instalace { #installation } + +Instalace modulu se skládá ze dvou kroků: + +1. [Příprava](#preparation-the-metadata-file) souboru metadat s DHIS2 metadaty. +2. [Import](#import-a-metadata-file-into-dhis2) souboru metadat do DHIS2. +3. [Konfigurace](#additional-configuration) importovaná metadata. +4. [Provádění](#examples-of-other-modifications) úprav specifických pro balíček. + +Tato část se zabývá prvními dvěma kroky přípravy a importu souboru metadat do DHIS2, zatímco postup konfigurace je popsán v další části. Před zahájením procesu instalace a konfigurace v DHIS2 se doporučuje nejprve si přečíst obě části. Kromě zde popsaných obecných kroků mají některé konfigurační balíčky přílohy k instalační příručce, které popisují konkrétní problémy. Ty jsou uvedeny v příslušné sekci [zde](https://dhis2.org/who-package-downloads). + +Postup popsaný v tomto dokumentu by měl být testován v testovacím / fázovacím prostředí před opakováním nebo přenesením do produkční instance DHIS2. + +Více konfiguračních balíčků + +Některé konfigurační balíčky mají překrývající se metadata, například indikátory. To znamená, že v některých situacích mohou být změny metadat konfiguračních balíčků, které byly dříve importovány, přepsány při importu jiného balíčku. Tomu se lze vyhnout importováním metadat „pouze nová“ místo „nových a aktualizací“, ale mějte na paměti, že u obou přístupů budou nutné ruční úpravy. Minimálně musíte zajistit, aby byla metadata používaná více programy [sdílena](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) s příslušnými skupinami uživatelů pro oba programy. + +## Požadavky { #requirements } + +K instalaci konfiguračního balíčku je vyžadován uživatelský účet správce v DHIS2 s oprávněními k přidávání / úpravám (veřejných) objektů metadat, mimo jiné včetně: (ale nejen) + +* datové prvky (včetně kategorií) +* datové sady +* indikátory +* typy indikátorů +* ovládací panely +* datový vizualizér, kontingenční tabulka a oblíbené GIS + +Úplný seznam objektů obsažených v modulu (pro které správce potřebuje oprávnění ke správě) najdete v referenčním dokumentu metadat pro konkrétní konfigurační balíček. + +V případech, kdy jsou nutné úpravy souboru metadat .json konfiguračního balíčku [(viz níže)](https://who.dhis2.org/documentation/installation_guide_complete.html#preparing-the_metadata-file), [textový editor ](https://en.wikipedia.org/wiki/Text_editor) je potřeba - tyto úpravy by neměly být prováděny s textovým procesorem, jako je Microsoft Word. + +Konfigurační balíček lze nainstalovat do DHIS2 prostřednictvím aplikace DHIS2 Health App nebo ručně prostřednictvím souboru .json s metadaty DHIS2 pomocí aplikace [Import / Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) aplikace DHIS2. Postup popsaný ve zbytku této části platí pro proces ručního importu metadat. + +Sekce [Konfigurace](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) platí pro obě metody. + +## Příprava souboru metadat { #preparing-the-metadata-file } + +**POZNÁMKA**: Pokud instalujete balíček na novou instanci DHIS2, můžete přeskočit část „Příprava souboru metadat“ a okamžitě přejít do části „[Import souboru metadat do DHIS2](#import-a-metadata-file-into-DHIS2). “ + +I když to není vždy nutné, může být často výhodné provést určité úpravy souboru metadat před jeho importem do DHIS2. + +## Výchozí dimenze dat { #default-data-dimension } + +V dřívějších verzích DHIS2 byl automaticky vygenerován UID výchozí datové dimenze. Zatímco tedy všechny instance DHIS2 mají výchozí možnost kategorie, kategorii datových prvků, kombinaci kategorií a kombinaci možností kategorie, UID těchto výchozích hodnot se mohou lišit. Novější verze DHIS2 mají pevně zakódované UID pro výchozí dimenzi a tyto UID se používají v konfiguračních balíčcích. + +Aby nedocházelo ke konfliktům při importu metadat, je vhodné vyhledat a nahradit celý soubor .json pro všechny výskyty těchto výchozích objektů a nahradit identifikátory UID souboru .json identifikátory UID databáze, do které bude soubor importován. Tabulka 1 ukazuje UID, která by měla být nahrazena, a také koncové body API pro identifikaci stávajících UID. + +|Objekt|UID|Koncový bod API| +|--|--|--| +|Kategorie|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Možnost kategorie|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Kombinace kategorií|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Kombinace možností kategorie|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| + +Například pokud importujete konfigurační balíček do [https://play.dhis2.org/demo](https://play.dhis2.org/demo), UID výchozí kombinace možností kategorie lze identifikovat pomocí [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) jako `bRowv6yZOF2`. Poté můžete v souboru .json vyhledat a nahradit všechny výskyty souboru `HllvX50cXC0` výrazem `bRowv6yZOF2`. Tato operace hledání a nahrazení musí být provedena pomocí editoru prostého textu, nikoli pomocí textového editoru, jako je Microsoft Word. + +## Typy indikátorů { #indicator-types } + +Typ indikátoru je další typ objektu, který může způsobit konflikt importu, protože se v různých databázích DHIS2 používají určité názvy (např. „Procento“). Vzhledem k tomu, že typy indikátorů jsou definovány jednoduše podle jejich faktoru a bez ohledu na to, zda jsou či nejsou jednoduchými čísly bez jmenovatele, jsou jednoznačné a lze je nahradit pomocí vyhledávání a nahrazení UID. Tím se vyhnete možným konfliktům při importu a vyhnete se vytváření duplicitních typů indikátorů. Tabulka 2 ukazuje identifikátory UID, které lze nahradit, a také koncové body API pro identifikaci stávajících identifikátorů UID. + +|Objekt|UID|Koncový bod API| +|--|--|--| +|Pouze čitatel (číslo)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Procento|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| + +**Poznámka 1**: nahrazením identifikátorů UID, jak je popsáno, a importem souboru .json, bude název (včetně všech překladů) příslušných typů indikátorů aktualizován na názvy obsažené v konfiguračních balíčcích. + +**Poznámka 2**: Alternativním přístupem k opětovnému použití existujících typů indikátorů je import těch, které jsou obsaženy v konfiguračním balíčku, a odstranění stávajících, které se překrývají. To by vyžadovalo aktualizaci všech indikátorů, které používají tyto existující typy indikátorů, na nově importované typy indikátorů, než bude možné typy indikátorů odstranit. + +## Import souboru metadat do DHIS2 { #importing-a-metadata-file-into-dhis2 } + +Soubor metadat .json je importován prostřednictvím aplikace [Import/Export] (https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) systému DHIS2. Před pokusem o skutečný import metadat je vhodné použít funkci „suchý běh“ k identifikaci problémů. Pokud „suchý běh“ hlásí nějaké problémy nebo konflikty, podívejte se na níže uvedenou část [konflikty importu](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts). + +Pokud import „běh nasucho“ / „ověření“ funguje bez chyby, pokuste se importovat metadata. Pokud je import úspěšný bez jakýchkoli chyb, můžete pokračovat v [konfiguraci](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) modulu. V některých případech se konflikty nebo problémy s importem nezobrazí během „běhu nasucho“, ale objeví se při pokusu o skutečný import. V tomto případě bude souhrn importu obsahovat seznam všech chyb, které je třeba vyřešit. + +### Řešení konfliktů importu { #handling-import-conflicts } + +**POZNÁMKA** Pokud importujete do nové instance DHIS2, nebudete se muset starat o konflikty importu, protože v databázi, do které importujete, není nic, co by mohlo být v konfliktu. Postupujte podle pokynů k importu metadat, poté pokračujte k části „[Další konfigurace](#additional-configuration)“. + +Může nastat řada různých konfliktů, i když nejběžnější je, že v konfiguračním balíčku jsou objekty metadat se jménem, zkratkou a / nebo kódem, který již v cílové databázi existuje. Existuje několik alternativních řešení těchto problémů s různými výhodami a nevýhodami. Který z nich je vhodnější, bude záviset například na typu objektu, pro který dojde ke konfliktu. + +#### Alternativa 1 { #alternative-1 } + +Přejmenujte existující objekt, u kterého došlo ke konfliktu. Výhodou tohoto přístupu je, že není nutné upravovat soubor .json, protože změny se místo toho provádějí prostřednictvím uživatelského rozhraní DHIS2. Pravděpodobně to bude méně náchylné k chybám. To také znamená, že konfigurační balíček je ponechán tak, jak je, což může být výhodou, například když se použije školicí materiál a dokumentace založená na konfiguračním balíčku. + +#### Alternativa 2 { #alternative-2 } + +Přejmenujte objekt, u kterého došlo ke konfliktu v souboru .json. Výhodou tohoto přístupu je, že stávající metadata DHIS2 jsou ponechána tak, jak jsou. To může být faktor, když existuje školicí materiál nebo dokumentace, jako jsou SOP datových slovníků propojených s daným objektem, a to nezahrnuje žádné riziko záměny uživatelů úpravou metadat, se kterými jsou obeznámeni. Úprava objektu souboru .json současně znamená, že používání přidružené dokumentace a školicího materiálu se může stát komplikovanějším. + +Všimněte si, že pro alternativu 1 i 2 může být modifikace stejně jednoduchá jako přidání malého pre / post-fix k názvu, aby se minimalizovalo riziko záměny. + +#### Alternativa 3 { #alternative-3 } + +Třetím a komplikovanějším přístupem je úprava souboru .json pro opětovné použití existujících metadat. Například v případech, kdy indikátor pro určitý koncept již existuje (např. „Pokrytí ANC 1“), může být tento indikátor odstraněn ze souboru .json a všechny odkazy na jeho UID nahrazeny odpovídajícím indikátorem, který je již v databázi. Velkou výhodou tohoto .json (který se neomezuje na případy přímého konfliktu importu) je vyhnout se vytváření duplicitních metadat v databázi. Obvykle se však nedoporučuje z několika důvodů: + +* vyžaduje odborné znalosti struktury podrobných metadat DHIS2 +* přístup nefunguje u všech typů objektů. Zejména určité typy objektů mají závislosti, které se tímto způsobem komplikovaně řeší, například v souvislosti s rozčleněními. +* stejně jako u alternativy 2 to znamená, že výsledek instalace není zcela v souladu se standardní konfigurací a školicí materiál a dokumentace vyvinutá pro tuto konfiguraci nemusí být bez úprav použitelné. +* budoucí aktualizace konfiguračního balíčku budou komplikované. + +## Další konfigurace { #additional-configuration } + +Po úspěšném importu všech metadat by měl být modul použitelný pouze s několika drobnými dalšími úpravami. Kromě toho, v závislosti zcela na instanci DHIS2, do které byl modul importován, může být nutná nebo výhodná nějaká další konfigurace a modifikace. Tato část nejprve projde nezbytnými konfiguračními kroky, poté zmíní některé další typy úprav nebo konfigurace, které mohou být relevantní. + +## Požadovaná konfigurace { #required-configuration } + +Než lze konfigurační balíčky použít pro sběr dat, jsou nutné dva kroky. + +* Přiřaďte datovou sadu (datové sady) k příslušným organizačním jednotkám +* Sdílejte datovou sadu (datové sady) s příslušnými skupinami uživatelů +* Přidejte své(ho) uživatele do příslušných skupin uživatelů + +Datové soubory by měly být přiřazeny organizačním jednotkám (zařízením), u nichž se očekává, že budou podávat zprávy o tomto konkrétním datovém souboru. + +Sady dat a možnosti kategorií by měly být sdíleny také s příslušnými skupinami (skupinou) uživatelů pracovníků, kteří jsou odpovědní za zadávání údajů pro tyto soubory dat. + +### Sdílení { #sharing } + +Nejprve budete muset pomocí funkce *Sdílení* DHIS2 konfigurovat, kteří uživatelé (skupiny uživatelů) by měli vidět metadata a data spojená s programem a kdo může registrovat / zadávat data do programu. Sdílení by mělo být nakonfigurováno pro následující: + +* Datové prvky / skupiny datových prvků +* Indikátory / skupiny indikátorů +* Datové Sady +* Ovládací panely + +Balíček obsahuje tři skupiny uživatelů: + +* COVID19 Přístup +* COVID19 admin +* COVID 19 Sběr dat  + +Doporučujeme následující přístup + +|Objekt|Uživatelská skupina||| +|--|--|--|--| +||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| +|_Datové prvky / skupina datových prvků_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata : lze zobrazit
Data: lze zobrazit| +|_Indikátory / skupina indikátorů_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata : lze zobrazit
Data: lze zobrazit| +|_Datové sady_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata: lze zobrazit
Data: lze zachytit a zobrazit| +|_Ovládací panely_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata : lze zobrazit
Data: lze zobrazit| + +### Duplikovaná metadata { #duplicated-metadata } + +I když byla metadata úspěšně importována bez jakýchkoli konfliktů při importu, mohou být v metadatech duplikáty - ať už jde o graf, indikátor, datový prvek nebo kategorii datových prvků, které již existují. Jak bylo uvedeno v části výše o řešení konfliktů, je třeba mít na paměti důležitý problém, že při rozhodování o změnách metadat v DHIS2 je třeba zohlednit i další dokumenty a zdroje, které jsou různými způsoby spojeny s existujícími metadaty a metadata, která byla importována prostřednictvím konfiguračního balíčku. Vyřešení duplikátů tedy není jen otázkou „vyčištění databáze“, ale také zajištěním toho, aby se tak dělo například bez narušení potenciálu integrace s jinými systémy, možnosti použít školicí materiál, porušení SOP atd. To bude velmi závislé na kontextu. + +Je třeba mít na paměti jednu důležitou věc, že DHIS2 má nástroje, které mohou skrýt některé složitosti možných duplikací v metadatech. Například tam, kde existují kategorie duplicitních datových prvků, mohou být tyto duplicity pro koncové uživatele skryty prostřednictvím skupin skupin možností možností nebo mohou být skryty určité objekty metadat pro skupiny uživatelů prostřednictvím sdílení. + +Doporučuje se neodstraňovat ani nenahrazovat indikátory obsažené v konfiguračních balíčcích, přestože stejný indikátor již existuje, aby bylo možné uchovat analytické výstupy (které vycházejí výhradně z indikátorů). To umožní opětovné použití školicích materiálů založených na konfiguračních balíčcích. + +## Příklady dalších úprav { #examples-of-other-modifications } + +Kromě požadované konfigurace existuje řada dalších úprav a konfigurace, které mohou být relevantní v závislosti na konkrétní situaci. Nebude možné poskytnout pokyny a doporučení, která pokrývají všechny různé scénáře, ale zde je uvedena krátká diskuse o některých běžných problémech. + +### Překlady { #translations } + +Je možné, že bude třeba přidat další překlady, pokud jsou zapotřebí jiné jazyky než ty, které jsou součástí. + +### Přidání dalších proměnných { #adding-additional-variables } + +Konfigurační balíčky obsahují klíčové doporučené datové prvky a indikátory. V některých případech však může být nutné přidat další proměnné, které by vyhovovaly informačním potřebám jednotlivých zemí. Ty by mohly být přidány do zahrnutých datových sad. + +### Aktualizace rozložení formulářů pro podávání zpráv { #updating-layout-of-reporting-forms } + +Pro usnadnění práce personálu provádějícího zadávání dat v DHIS2 je někdy žádoucí přidat vlastní formulář pro zadávání dat, který odpovídá formátu papírových formulářů používaných na primární úrovni. + +## Údržba { #maintenance } + +Konfigurační balíčky nevyžadují žádnou zvláštní údržbu, protože jsou tvořeny standardními objekty metadat DHIS2. Před upgradem na nové verze DHIS2 je však důležité otestovat všechny funkce systému obecně na pracovním / testovacím serveru před upgradem produkčních instancí systému. + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md new file mode 100644 index 00000000..65571832 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/overview.md" +revision_date: '2023-03-07' +tags: +- Implementace +--- + +# COVID-19 Aggregate Surveillance { #covid-19-aggregate-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-agg-release-note) + +## Design { #design } + +- [Version 2.0.0](#c19-agg-design) + +## Instalace { #installation } + +- [Installation Guide](#c19-agg-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 2.0.0](https://packages.dhis2.org/en/C19_AGG/2.0.0/DHIS2.39/C19_AGG_COMPLETE_2.0.0_DHIS2.39.xlsx) + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md new file mode 100644 index 00000000..dd1844b4 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md @@ -0,0 +1,26 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implementace +--- + +# Release Note { #c19-agg-release-note } + +To see additional details of the metadata objects mentioned below, refer to the metadata reference documentation of the relevant version. + +## 2.0.0 { #200 } + +* The changes leading to this version were based on the revised [WHO Global surveillance of COVID-19 Weekly Aggregate Report ](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) +* The major were made on the age disaggregations with 5 year age bands used for <20 years and 60+ years spanning upto 80+years. +* Unknown age and Unknown sex were also introduced in the disaggregations to cater data that cannot be categorized with the options provided. +* Data elements for cases and deaths among health workers (Confirmed + Probable), tests with PCR assay, deaths amongst probable cases and health workers were introduced in this version. +* Byly odstraněny datové prvky pro logistiku a případy podle klasifikace přepravy. +* S ohledem na tyto změny byly nově vytvořeny všechny základní metadatové objekty: datové prvky, ukazatele, ovládací panel a jeho položky, datové sady, skupiny ukazatelů a skupiny datových prvků. +* Tato verze má nyní pouze jednu datovou sadu určenou pro týdenní reportování na rozdíl od předchozí verze, která měla 2 datové sady reportované týdně a denně. +* Všechny základní objekty metadat byly kódovány pro podporu mezinárodního standardu pro výměnu souhrnných dat (ADX). + +## 1.0.0 { #100 } + +Initial release of COVID-19 Aggregate Surveillance package + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md new file mode 100644 index 00000000..eaa912ce --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -0,0 +1,289 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-design.md" +revision_date: '2022-09-13' +tags: +- Implementace +--- + +# COVID-19 Case Surveillance & Contact Tracing Design { #c19-cs-design } + +Demo: [https://demos.dhis2.org/covid-19](https://demos.dhis2.org/covid-19) + +## Účel { #purpose } + +Dokument Návrh systému dohledového systému COVID-19 poskytuje přehled koncepčního designu použitého ke konfiguraci balíčku digitálních dat COVID-19 v DHIS2. Balíček COVID-19 byl vyvinut v reakci na výslovnou potřebu zemí rychle přizpůsobit řešení pro správu dat COVID-19. Tento dokument je určen k použití implementátory DHIS2 na národní a regionální úrovni, aby mohli podporovat implementaci a lokalizaci balíčku. Balíček metadat COVID-19 lze přizpůsobit místním potřebám a národním pokynům. Při lokalizaci a přijímání programů obsažených v tomto balíčku by měly být brány v úvahu zejména místní pracovní toky a národní pokyny. + +## Pozadí { #background } + +**Tento design byl aktualizován tak, aby odrážel nové souhrnné požadavky na podávání zpráv z [pokynů WHO k prozatímnímu dohledu aktualizovaných 20. března 2020] [1]**. Balíček digitálních dat COVID-19 byl vyvinut v reakci na vyjádřenou potřebu zemí rychle přizpůsobit řešení pro správu dat COVID-19. UiO vyvinula balíčky sledování COVID-19 pro tři typy datových modelů (tracker, agregát založený na událostech), aby země mohly vybrat model, který je vzhledem k zátěži nemocí a dostupným zdrojům nejvhodnější pro jejich kontext. Tyto modely a jejich relativní výhody/omezení jsou shrnuty níže: + +| Typ balíčku sledování | Case Surveillance (Tracker) | Sledování (událost) | Pozorování (Agregované) | +|---|---|---|---| +| ***Popis*** | Zapisuje případ a sleduje časem laboratorní potvrzení a výsledek případu | Zachycuje podrobnosti kritických případů ve formátu seznamu řádků | Umožňuje denní nebo týdenní hlášení klíčových agregovaných datových bodů | +| ***Klady*** | Vysoce strukturovaná data a více časových dimenzí pro analýzu mohou podporovat decentralizovaný pracovní postup, všechny události spojené s případem | Podrobnější než agregované a dokáže zachytit klíčové časové dimenze (tj. Datum zprávy vs. nástup příznaků); snížená zátěž při zadávání dat ve srovnání se trasovačem a malá složitost | Nízká složitost, snadná implementace, zvládnutelnost, když je počet případů vysoký | +| ***Zápory*** | Břemeno zadávání dat může být ohromující, když počet případů dosáhne prahové hodnoty; složitost implementace | Nepodporuje sledování případů ani jiné decentralizované pracovní postupy | Menší podrobnost pro podrobnou analýzu (tj. Analýza pouze na základě data hlášení případu, omezené členění) | + +**Tento dokument se vztahuje pouze na návrh programového balíčku trasovacího zařízení**; pro dokumenty DHIS2 událostí a agregované balíčky jsou k dispozici samostatné dokumenty návrhu systému. + +WHO „žádá všechny země, aby se připravily na potenciální příchod COVID-19 tím, že připraví systémy reakce na mimořádné události; zvýšení kapacity pro odhalování a péči o pacienty; zajištění toho, aby nemocnice měly prostor, zásoby a potřebný personál; a vývoj záchranných lékařských zásahů.“ + +Cíle dozoru COVID-19 jsou: + +1. sledovat trendy choroby, při které dochází k přenosu z člověka na člověka; +2. rychle odhalit nové případy v zemích, kde virus necirkuluje; +3. a poskytovat epidemiologické informace k provádění hodnocení rizik na národní, regionální a globální úrovni; a +4. poskytovat epidemiologické informace jako vodítko pro opatření připravenosti a reakce. + +The system design builds upon existing case disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 surveillance package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions][2], updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## Souhrn návrhu systému { #system-design-summary } + +The DHIS2 case surveillance tracker metadata was based on the **[WHO COVID-19 case reporting template][3]** and the mapping of data dictionaries can be accessed at: [DHIS2 CBS tracker metadata WHO line-list data dictionary][4]. + +Při vývoji tohoto konfiguračního balíčku bylo vyvinuto úsilí dodržovat [obecné zásady návrhu][5] UiO a společnou [konvenci pojmenování][6]. + +Balíček digitálních dat COVID-19 podporuje sledovací pracovní postupy a automatickou analýzu klíčových komponent rutinního a aktivního sledování. Tento balíček obsahuje trasovač případů a trasovač registrace a sledování kontaktů, které jsou nainstalovány společně ve stejném balíčku metadat. Programy pro trasování jsou optimalizovány tak, aby byly instalovány s dalšími sledovacími balíčky COVID-19, včetně sledovacího zařízení Points of Entry Screening Tracker a agregovaného denního datového souboru sledování. + +1. **[Use Case 1: COVID-19 Case surveillance tracker][7]**: enrols & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. Metadata for the case surveillance tracker is aligned with the WHO [COVID-19 surveillance data dictionary][8] + + > n.b. The COVID-19 case tracker can be implemented either as a ‘standalone’ program for COVID-19 specific disease surveillance as described here; or, COVID-19 concepts can be integrated into an existing case surveillance tracker program if one already exists in-country. Please refer to installation and implementation guidance for more details. + +1. **[Případ použití 2: Registrace a sledování kontaktu][9]**: posiluje aktivní detekci případů prostřednictvím aktivit pro trasování kontaktů, jako je identifikace a sledování kontaktů na podezřelý nebo potvrzený případ COVID-19. + +Balíčky digitálních dat jsou optimalizovány pro sběr dat Android pomocí aplikace DHIS2 Capture, kterou lze zdarma stáhnout v [obchod Google Play][10]. + +## Use Case 1: COVID-19 Case surveillance tracker { #use-case-1-covid-19-case-surveillance-tracker } + +The COVID-19 case surveillance tracker can be adapted and used by countries to supplement existing national disease surveillance programs. The basic case surveillance program is designed to: + +1. Zaregistrujte podezřelé\* případy COVID-19 (*obvykle se objevují ve zdravotnickém zařízení, ale mohou být zapsány i na jiných místech*) +2. Zachyťte klíčové informace o podezřelém případu, včetně demografických údajů a expozic, jako jsou příznaky, kontakt s dříve potvrzeným případem a historie cestování +3. Generovat laboratorní požadavky +4. Záznam laboratorní diagnózy +5. Záznam kontaktu potvrzeného\*\* nebo pravděpodobného\*\*\* případu pro další sledování +6. Záznam výsledku případu +7. Usnadněte oznamování případů a národní / regionální / globální hlášení případů +8. Generujte ovládací panely a analytické nástroje pro sledování trendů nemocí a plánování reakcí + +The design of the case tracker program assumes that [WHO case definitions][1] are followed in the use case; its use can be adapted to local case definitions as needed. The WHO case definitions were updated on March 20, 2020 and noted below. + +> \* Podezřelý případ: A) pacient s akutním respiračním onemocněním (horečka a alespoň jeden příznak respiračního onemocnění (např, kašel, dušnost), A bez jiné etiologie, která by plně vysvětlovala klinický obraz, A s anamnézou cestování nebo pobytu v zemi/oblasti nebo území, kde byl hlášen místní přenos onemocnění COVID-19 během 14 dnů před nástupem příznaků; **NEBO**, B) Pacient s jakýmkoli akutním respiračním onemocněním A který byl v posledních 14 dnech před nástupem příznaků v kontaktu s potvrzeným nebo pravděpodobným případem COVID-19 (viz definice kontaktu); **NEBO,** C) Pacient s těžkou akutní respirační infekcí (horečka a alespoň jeden příznak/příznak respiračního onemocnění (např. kašel, dušnost) A vyžadující hospitalizaci A bez jiné etiologie, která by plně vysvětlovala klinický obraz. +> +>\*\* Pravděpodobný případ: A) podezřelý případ, u kterého je testování na COVID-19 neprůkazné (neprůkazný je výsledek testu hlášený laboratoří) **NEBO,** B) podezřelý případ, u kterého nebylo možné z jakéhokoli důvodu provést testování. +> +>\*\*\* Potvrzený případ: Osoba, u které byla laboratorně potvrzena infekce COVID-19, bez ohledu na klinické příznaky. + +### Určení uživatelé { #intended-users } + +* Uživatelé zdravotnických zařízení: zachycení a zaznamenání podrobností o podezření na případ, včetně klinických příznaků a vystavení; sledovat laboratorní výsledky; zaznamenat výsledek případu +* Uživatelé laboratoře: přijímají laboratorní požadavky a zaznamenávají laboratorní výsledky pro konkrétní podezřelý případ +* Národní a místní zdravotní úřady: monitorují a analyzují údaje o sledování nemocí prostřednictvím ovládacích panelů a analytických nástrojů k provádění hodnocení rizik a plánování opatření reakce; generovat zprávy pro regionální a globální zprávy + +### Workflow: COVID-19 Case Surveillance Tracker { #workflow-covid-19-case-surveillance-tracker } + +![Workflow of the DHIS2 COVID-19 Case Surveillance Tracker](resources/images/sdd-tracker-v3-case1-workflow.png) + +### Struktura: Program sledování případů COVID-19 { #structure-covid-19-case-surveillance-tracker-program } + +![Struktura programu trasování případů COVID-19](resources/images/sdd-tracker-v3-case1-structure-v2.png) + +#### Popis programu: Testování, diagnostika a výsledek případu COVID-19 { #program-description-covid-19-case-testing-diagnosis-outcome } + +| Fáze | Popis | +|---|---| +| **Podrobnosti a atributy zápisu** | Trasovanou entitou je případ, který je reprezentován typem trasované entity "osoba". *Datum zápisu* je datum registrace případu. Související programy jsou *COVID-19 Registrace kontaktu a následná opatření*. Atributy zahrnují následující základní osobní údaje a jedinečné identifikátory případu: *Systémově generované ID případu*, *Místní ID případu*, *Věk*, *Jméno*, *Příjmení*, *Pohlaví*, *Telefonní číslo případu*, *Jméno (rodič nebo opatrovník)*, *Příjmení (rodič nebo opatrovník)*, *Adresa bydliště*, *Fyzická adresa pracoviště/školy*, *Země bydliště*, *Kontaktní číslo zařízení*.| +| **Fáze 1: Klinické vyšetření a expozice** | V této fázi se zaznamenávají klinické příznaky a expozice podezřelého případu, včetně: *příznaky*, *těhotenství a základní onemocnění*, *hospitalizace a izolace*, *expozice během 14 dnů před příznaky*, *cestovní anamnéza*, *kontakt s potvrzeným případem*. Po vyšetření můžete zaznamenat, zda byl případ hospitalizován nebo izolován, a informace o tom. | +| **Fáze 2: Laboratorní požadavek [opakovatelný]** | Požadavek laboratoře zaznamenává důvod testování a další informace, které laboratoř potřebuje ke zpracování vzorku a jeho testování na COVID19. Zde uvedené informace mohou pracovníkům laboratoře pomoci upřednostnit laboratorní testy, když jsou zdroje omezené. Osoba zadávající tyto údaje může být stejná osoba, která zaregistrovala podezřelý případ a zaznamenala klinické vyšetření a expozice pacienta; nebo to může být jiný personál pověřený prováděním laboratorních požadavků. | +| **Fáze 3: Výsledky laboratoře [opakovatelné]** | Fáze Laboratorní výsledky zaznamenává typ a výsledky laboratorního testování. To lze provést přímo v laboratoři nebo jako sekundární zadávání dat. Tato fáze je opakovatelná, protože vzorky pro daný případ mohou být testovány několikrát (tj. V případě neprůkazných laboratorních výsledků lze provést nový laboratorní test a zaznamenat výsledky). | +| **Fáze 4: Výsledné zdraví** | Výsledek zdraví zaznamenává konečný výsledek případu: (zotavený, nezotavený, zemřelý nebo neznámý) včetně případného data propuštění nebo úmrtí. | + +#### Enrollment Stage { #enrollment-stage } + +![Zápis](resources/images/sdd-tracker-v3-case1-enrollment.png) + +#### Program Fáze 1 - Klinické vyšetření a diagnostika { #program-stage-1-clinical-examination-diagnosis } + +##### Oddíl 1 - Klinické příznaky a symptomy { #section-1-clinical-signs-and-symptoms } + +Výběr „ano“ u datového prvku „Jakékoli příznaky nebo příznaky?“ Odhalí zbývající možnosti. + +![Část 1](resources/images/sdd-tracker-v3-case1-stage1-section1.png) + +##### Oddíl 2 - Podrobnosti o těhotenství { #section-2-pregnancy-details } + +Tato část je skrytá, pokud není pohlaví vybráno jako „Žena“. + +![Část 2](resources/images/sdd-tracker-v3-case1-stage1-section2.png) + +##### Oddíl 3 - Základní podmínky / komorbidita { #section-3-underlying-conditionscomorbidity } + +The details of this section are hidden unless “Any underlying conditions” is marked as “Yes”. + +![Část 3](resources/images/sdd-tracker-v3-case1-stage1-section3.png) + +##### Oddíl 4 - Hospitalizace { #section-4-hospitalisation } + +Podrobnosti této sekce jsou skryté, pokud není „Hospitalizováno“ označeno jako „Ano“. + +![Část 4](resources/images/sdd-tracker-v3-case1-stage1-section4.png) + +##### Část 5 - Riziko expozice { #section-5-exposure-risk } + +Tato část se používá k záznamu vystavení + + 1. The fields ***country, city and facility*** are hidden by program rules if the case is not a health care worker; + 2. Pole pro kontaktní ID jsou skryta pravidly programu, pokud případ neměl kontakt s potvrzeným případem do 14 dnů. + +A suspected case’s exposure to a *previously confirmed* case is distinct from prospective contact tracing in Program Stage 5. + +![Část 5](resources/images/sdd-tracker-v3-case1-stage1-section5.png) + +##### Oddíl 6 - Historie cestování { #section-6-travel-history } + +![Část 6](resources/images/sdd-tracker-v3-case1-stage1-section6.png) + +#### Fáze programu 2: Požadavek na laboratoř { #program-stage-2-lab-request } + +![Fáze 2](resources/images/sdd-tracker-v3-case1-stage2.png) + +#### Fáze 3: Výsledky laboratoře { #stage-3-lab-results } + +![Fáze 3](resources/images/sdd-tracker-v3-case1-stage3.png) + +#### Fáze 4: Výsledky v oblasti zdraví { #stage-4-health-outcomes } + +![Fáze 4](resources/images/sdd-tracker-v3-case1-stage4.png) + +### Pravidla programu: COVID19 Case Surveillance Tracker { #program-rules-covid19-case-surveillance-tracker } + +The following program rules have been configured. If a country has an existing case surveillance program and wishes to incorporate elements of the COVID-19 case tracker into their existing program, special attention must be paid to the configuration of program rules. + +| Název pravidla programu | Popis pravidla programu | +|---|---| +| Přiřadit datum zápisu | Tím se přiřadí datum zápisu, pokud není k dispozici datum nástupu proměnné vypočítané datum zahájení (pro indikátory). Tato proměnná se používá jako uživatelský parametr v některých indikátorech programu. | +| Přiřadit datum zahájení| Tím se přiřadí datum nástupu k proměnné vypočítané datum nástupu (pro indikátory). Tato proměnná se používá jako uživatelský parametr v některých indikátorech programu.| +| Vypočítejte a přiřaďte věk pacienta v letech | Vypočítejte a přiřaďte věk pacienta v letech na základě data narození | +| Zobrazit věk pacienta v letech + dnech | Zobrazit věk pacienta v letech + dnech | +| Skrýt datum úmrtí | Skryjte datum úmrtí, pokud smrt není výsledkem zdravotního stavu | +| Skrýt datum propuštění | Skryjte datum propuštění, pokud není žádný výsledek nebo pokud je výsledkem úmrtí | +| Skrýt pole Měřená teplota | Skryjte pole Měřená teplota, dokud nebude vybrána možnost Horečka | +| Pokud není kontakt s jinými potvrzenými případy, skryjte ID potvrzených případů| Skryje všechna kontaktní ID, pokud případ nebyl v žádném kontaktu s jinými potvrzenými případy | +| Skrýt podrobnosti o zdravotnickém pracovníkovi, pokud nejde o zdravotnického pracovníka | Skrýt podrobnosti o zdravotnickém pracovníkovi, pokud nejde o zdravotnického pracovníka | +| Skrýt vysvětlení zdravotního výsledku pokud zdravotní výsledek není jiný | Skrýt vysvětlení zdravotního výsledku pokud zdravotní výsledek není jiný | +| Skrýt podrobnosti o hospitalizaci, pokud hospitalizace není, nebo není známa | Skrýt podrobnosti o hospitalizaci, pokud hospitalizace není, nebo není známa | +| Skrýt datum izolace, pokud případ není v izolaci | Skrýt datum izolace, pokud případ není v izolaci | +| Skrýt podrobnosti o těhotenství u ženy, pokud není těhotná | Skrýt podrobnosti o těhotenství u ženy, pokud není těhotná | +| Skrýt sekci s podrobnostmi o těhotenství, pokud je pohlaví mužské | Skrýt sekci s podrobnostmi o těhotenství, pokud je pohlaví mužské | +| Pokud je vybrána možnost, skrýt důvod vysvětlení testování | Pokud je vybrána možnost, skrýt důvod vysvětlení testování | +| Skrýt podrobnosti o historii cestování, pokud žádné cestování 14 dní před nástupem příznaků neprobíhá | Skrýt podrobnosti o historii cestování, pokud žádné cestování 14 dní před nástupem příznaků neprobíhá | +| Skrýt základní podmínky, pokud je případ nemá | Skrýt základní podmínky, pokud je případ nemá | +| Zobrazit varování, pokud je datum události po datu zápisu | Zobrazit upozornění na dokončení události, pokud je datum události před datem zápisu | + +You can read more about program rules here: [https://docs.dhis2.org/master/en/user/html/configure\_program\_rule.html][11] + +### Programové Indikátory { #program-indicators } + +Z údajů zachycených v programu dozoru nad případy COVID-19 můžeme vypočítat alespoň následující indikátory, včetně těch, které WHO doporučuje pro denní a týdenní souhrnné hlášení, a prezentovat je na ovládacím panelu: + +| Název indikátoru | Popis | +|---|---| +| COVID-19 - Případy ošetřené mechanickou ventilací nebo ECMO nebo přijaté na jednotku intenzivní péče (JIP) | *Případy ošetřené mechanickou ventilací nebo ECMO nebo přijaté na jednotce intenzivní péče (JIP)* | +| Kontakty COVID-19 | *Počítá počet vytvořených vztahů („byl v kontaktu“), které jsou spojeny s případem TEI* | +| COVID-19 - Úmrtí (všechny podezřelé případy) | *COVID-19 souvisejíc úmrtí (úmrtí zaznamenaná mezi všemi podezřelými případy)* | +| COVID-19 - Úmrtí (potvrzené případy) | *COVID-19 související úmrtí (úmrtí zaznamenaná mezi potvrzenými případy)* | +| COVID-19 - Úmrtí (pravděpodobné případy) | *Úmrtí související s COVID-19 (úmrtí zaznamenaná mezi všemi pravděpodobnými případy)* | +| COVID-19 - potvrzené hospitalizované případy | *Počet potvrzených případů, které byly přijaty do nemocnice* | +| COVID-19 - importované případy | *Případy, kdy je pravděpodobný zdroj infekce zaznamenán jako jiná země nebo import z jiné země.* | +| COVID-19 - Laboratorně potvrzené případy | *Podezřelé případy, které byly potvrzeny laboratorním testováním (lze provést více laboratorních testů; tento indikátor předpokládá, že poslední výsledek testu je*„pozitivní“*); zobrazeno podle data hlášení* | +| COVID-19 - Laboratorně potvrzené případy - podle nástupu příznaků | *Podezřelé případy, které byly potvrzeny laboratorním testováním (lze provést více laboratorních testů; tento indikátor předpokládá, že poslední výsledek testu je*„pozitivní“*); zobrazeno podle data nástupu příznaků* | +| COVID-19 - Laboratorně testované případy | *Počet podezřelých případů, u kterých bylo provedeno laboratorní vyšetření (včetně neprůkazných výsledků laboratorního vyšetření)* | +| COVID-19 - Místní případy přenosu | *Počet podezřelých případů, kdy je přenos lokální (žádné cestování v posledních 14 dnech* | +| COVID-19 - Pravděpodobné případy | *Podezřelé případy s neprůkaznými laboratorními výsledky nebo netestované z jakéhokoli důvodu, do oznámeného data* | +| COVID-19 - Pravděpodobné případy - podle nástupu příznaků | *Podezřelé případy s neprůkaznými laboratorními výsledky nebo z jakéhokoli důvodu netestované, podle data nástupu příznaků* | +| COVID-19 - Obnovené potvrzené případy | *Počet laboratorně potvrzených případů s obnoveným výsledkem*| +| COVID-19 - Podezřelé případy | *Celkový počet případů podezření na COVID-19 podle data hlášení* | +| COVID-19 - Podezření na případy - podle nástupu příznaků | *Celkový počet případů podezřelých z užívání přípravku COVID-19, podle data nástupu příznaků* | +| COVID-19 - Podezřelé případy bez pozitivního výsledku testu | *Celkový počet podezřelých případů bez pozitivního laboratorního výsledku* | +| COVID-19 Celkový počet provedených laboratorních testů | *Celkový počet provedených laboratorních testů (počet testů, ne případů)* | +| COVID-19 Celkový počet pozitivních testů | *Celkový počet laboratorních testů vrácených s pozitivními výsledky (počet testů, ne případů* | +| COVID-19 Úmrtí podle pohlaví a věkových skupin | ***Muž**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Žena**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Potvrzené případy podle pohlaví a věkové skupiny | ***Muž**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Žena**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Podezřelé případy podle pohlaví a věkové skupiny | ***Muž**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Žena**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | + +## Uživatelský případ 2: COVID-19 Registrace a sledování kontaktů { #use-case-2-covid-19-contact-registration-follow-up } + +This program can be used in addition to the case surveillance tracker to facilitate the registration and follow-up of contacts of a confirmed case. In this scenario, it is assumed that if any contacts of a confirmed case meet criteria for suspected case and are referred for testing, the case will be enrolled into the COVID-19 Case Surveillance tracker program. + +Program Registrace a sledování kontaktů registruje každý kontakt případu (jak je popsáno v Případu použití případu COVID-19) jako novou instanci trasované entity (osoby) a spojuje je s případem v Programu sledování případů COVID-19 prostřednictvím „vztahu“. Má jednoduchou opakovatelnou následnou fázi, kdy mohou být registrovány příznaky a jakékoli následné sledování. + +### Pracovní postup: Registrace kontaktu a následná opatření { #workflow-contact-registration-follow-up } + +![Průběh registrace kontaktů a následná opatření](resources/images/sdd-tracker-v3-case2-workflow.png) + +### Popis programu: Registrace a sledování kontaktů { #program-description-contact-registration-follow-up } + +| Fáze | Popis | +|---|---| +| **Podrobnosti a atributy zápisu** | Trasovaná entita je reprezentována typem trasované entity "osoba". Související program je *COVID-19 Dohled na základě případů*. Atributy zahrnují následující základní osobní údaje a jedinečné identifikátory případu: *Systémové ID případu*, *Místní ID případu*, *Jméno*, *Příjmení*, *Datum narození*, *Věk*, *Pohlaví*, *Telefonní číslo (místní)*, *Adresa bydliště*, *Země pobytu*. | +| **Fáze 1: Sledování [neopakující se]** | Tato fáze je určena k zaznamenání informací souvisejících s následným dohledáním kontaktu, pokud již byl kontakt identifikován. Je rozdělena do dvou částí: *1. Vztah k případu*, *2. Posouzení expozice* | +| **Fáze 2: Příznaky [opakující se]** | Tato fáze je určena k zaznamenání příznaků případu. Následná kontrola příznaků kontaktu se může opakovat, dokud není ukončena doba sledování (například po 14 dnech nebo podle národních směrnic). Jakmile je období následného sledování ukončeno, může být registrace "ukončena". *1. Příznaky*| + +Kontakty se do indexu přidávají pomocí nabídky vztahů v programu sledování případů: + +![Profil](resources/images/sdd-tracker-v3-case2-profile.png) + +Po výběru možnosti "Přidat" v poli vztahů můžete vybrat vztah a program a buď vybrat stávající osobu, nebo zapsat nový kontakt pomocí zobrazené fáze zápisu. Tím se kontakt zapíše do programu pro registraci a sledování kontaktů. + +![Přidat vztah](resources/images/sdd-tracker-v3-case2-add-relationship.png) + +Přidané kontakty se pak zobrazí na panelu sledování případu ve widgetu vztahů. + +![Widget pro vztahy](resources/images/sdd-tracker-v3-case2-relationships-widget.png) + +Můžete je také zaregistrovat samostatně do programu. Jakmile se zaregistrujete, budete je podle potřeby moci vyhledat pro další sledování. + +#### Zápis { #enrollment } + +![Zápis v případu použití 2](resources/images/sdd-tracker-v3-case2-enrollment-case2.png) + +#### Programová Fáze 1: Následná opatření { #program-stage-1-follow-up } + +![Případ 2 Fáze 1](resources/images/sdd-tracker-v3-case2-stage1.png) + +#### Programová Fáze 2: Příznaky { #program-stage-2-symptoms } + +![Případ 2 Fáze 2](resources/images/sdd-tracker-v3-case2-stage2.png) + +### Indikátory programu: Registrace kontaktu { #program-indicators-contact-registration } + +| Název indikátoru programu | Popis | +|---|---| +| Cestovatelé COVID-19 byli prověřeni | Celkový počet cestujících prověřených a zapsaných do screeningového programu z POE | +| COVID-19 cestující, kteří byli odbaveni na POE | Počet cestujících odbavených po kontrole POE (není nutná žádná další kontrola) | +| COVID-19 cestující s příznaky na POE | Počet cestujících s příznaky během screeningu POE | +| COVID-19 cestující, kteří byli čistí po 14 dnech monitorování | Počet cestujících, kteří jsou vymazáni po 14denním sledování (žádný nástup příznaků během 14denního období) | +| COVID-19 cestující, kteří se obrátili na zdravotnické zařízení | Počet cestujících, kteří byli posláni do zdravotnického zařízení kdykoli během 14denního sledování | +| Cestující COVID-19 se zapsali na 14denní sledování | Počet cestujících, u kterých se při screeningu POE neprojevily příznaky a při screeningu POE nebyli odmazáni | +| COVID-19 je v současné době sledován | Počet cestujících, kteří nebyli odbaveni nebo odesláni do zdravotnického zařízení | +| COVID-19 cestující, u kterých se během sledování objevily příznaky | Počet cestujících, u kterých se během sledování vyvinuly příznaky (nezahrnujte cestující, kteří mají příznaky během screeningu POE) | + +## Reference { #references } + +* Technické pokyny WHO k dozoru a definici případů COVID-19 (poslední aktualizace 20. března 2020)[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* Datový slovník WHO pro formulář hlášení případů COVID-19 [https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* Laboratorní testování WHO na nový koronavirus z roku 2019 (2019-nCoV) v případech podezření u člověka (poslední aktualizace 2. března 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* Úvahy WHO při vyšetřování případů a klastrů COVID-19 (naposledy aktualizováno 13. března 2020)[https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* Koronavirové situační zprávy WHO [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + +[1]: https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf +[2]: https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions +[3]: https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx +[4]: https://drive.google.com/open?id=1vigXHkP7L2hJ2lrZpdf9u4csQtppMH16 +[5]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html +[6]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html +[7]: #use-case-1-covid-19-case-surveillance-tracker +[8]: https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2 +[9]: #use-case-2-covid-19-Contact-registration-follow-up +[10]: https://play.google.com/store/apps/details?id=com.dhis2&hl=en +[11]: https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md new file mode 100644 index 00000000..f245767e --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-installation.md" +revision_date: '2022-09-13' +tags: +- Implementace +--- + +# COVID-19 Surveillance - Installation Guide { #c19-cs-installation } + +## Přehled { #overview } + +Balíček sledovače COVID-19 byl vyvinut pomocí DHIS2.33.2. To bylo provedeno za účelem podpory některých nejnovějších funkcí v DHIS2. Abyste mohli balíček použít, doporučujeme jej nainstalovat do instance DHIS2 pomocí DHIS2 2.33.2 nebo vyšší. Pokud to nastavujete na nové instanci, nahlédněte do [instalačního průvodce DHIS2] (https://docs.dhis2.org/en/manage/performing-system-administration/dhis-core-version-master/installation.html). Tento dokument popisuje instalaci následujících balíčků: + +1. Program sledování trasovaných případů COVID-19 a program registrace a sledování kontaktů COVID-19 +2. Program pro skríning Trasovače vstupních bodů + +Pro každý samostatný balíček, který instalujete, budete muset postupovat podle pokynů v plném rozsahu. + +## Instalace { #installation } + +Instalace modulu se skládá z několika kroků: + +1. [Příprava](#preparation-the-metadata-file) souboru metadat s metadaty DHIS2. +2. [Import](#import-metadata) souboru metadat do DHIS2. +3. [Konfigurace](#additional-configuration) importovaná metadata. +4. [Adaptace](#adapting-the-tracker-program) programu po importu + +Před zahájením procesu instalace a konfigurace v DHIS2 se doporučuje nejprve si přečíst každou část. Byly identifikovány oddíly, které nelze použít, v závislosti na tom, zda importujete do nové instance DHIS2 nebo instance DHIS2 s již existujícími metadaty. Postup popsaný v tomto dokumentu by měl být testován v testovacím / fázovacím prostředí před opakováním nebo přenesením do produkční instance DHIS2. + +## Požadavky { #requirements } + +K instalaci modulu je vyžadován uživatelský účet správce na DHIS2. Postup popsaný v tomto dokumentu by měl být testován v testovacím / fázovém prostředí před provedením na produkční instanci DHIS2. + +Je třeba věnovat velkou pozornost tomu, aby byl samotný server a aplikace DHIS2 dobře zabezpečené, aby se omezil přístup ke shromažďovaným datům. Podrobnosti o zabezpečení systému DHIS2 jsou mimo rozsah tohoto dokumentu a odkazujeme na [dokumentaci DHIS2](https://docs.dhis2.org/). + +## Příprava souboru metadat { #preparing-the-metadata-file } + +**POZNÁMKA**: Pokud instalujete balíček na novou instanci DHIS2, můžete přeskočit část „Příprava souboru metadat“ a okamžitě přejít do části „[Import souboru metadat do DHIS2](#import-metadata).“ + +I když to není vždy nutné, může být často výhodné provést určité úpravy souboru metadat před jeho importem do DHIS2. + +### Výchozí dimenze dat { #default-data-dimension } + +V dřívějších verzích DHIS2 byl automaticky vygenerován UID výchozí datové dimenze. Zatímco tedy všechny instance DHIS2 mají výchozí možnost kategorie, kategorii datových prvků, kombinaci kategorií a kombinaci možností kategorie, UID těchto výchozích hodnot se mohou lišit. Novější verze DHIS2 mají pevně zakódované UID pro výchozí dimenzi a tyto UID se používají v konfiguračních balíčcích. + +Aby nedocházelo ke konfliktům při importu metadat, je vhodné vyhledat a nahradit celý soubor .json pro všechny výskyty těchto výchozích objektů a nahradit identifikátory UID souboru .json identifikátory UID databáze, do které bude soubor importován. Tabulka 1 ukazuje UID, která by měla být nahrazena, a také koncové body API pro identifikaci stávajících UID + +|Objekt|UID|Koncový bod API| +|--|--|--| +|Kategorie|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Možnost kategorie|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Kombinace kategorií|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Kombinace možností kategorie|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| + +Pokud například importujete konfigurační balíček do [https://play.dhis2.org/demo](https://play.dhis2.org/demo), identifikátor UID výchozí kombinace možností kategorie lze identifikovat pomocí jako bRowv6yZOF2. + +Poté můžete vyhledat a nahradit všechny výskyty HllvX50cXC0 s bRowv6yZOF2 v souboru .json, protože to je ID výchozího v systému, do kterého importujete. ***Upozorňujeme, že tato operace hledání a nahrazení musí být provedena pomocí editoru prostého textu***, nikoli pomocí textového editoru, jako je Microsoft Word. + +### Typy indikátorů { #indicator-types } + +Typ indikátoru je další typ objektu, který může způsobit konflikt importu, protože se v různých databázích DHIS2 používají určité názvy (např. „Procento“). Vzhledem k tomu, že typy indikátorů jsou definovány jednoduše podle jejich faktoru a bez ohledu na to, zda se jedná o jednoduchá čísla bez jmenovatele, jsou jednoznačné a lze je nahradit pomocí vyhledávání a nahrazení UID. Tím se vyhnete možným konfliktům při importu a vyhnete se vytváření duplicitních typů indikátorů. Tabulka 2 ukazuje identifikátory UID, které lze nahradit, a také koncové body API pro identifikaci stávajících identifikátorů UID + +|Objekt|UID|Koncový bod API| +|--|--|--| +|Pouze čitatel (číslo)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Procento|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| + +#### TrackedEntityType { #tracked-entity-type } + +Stejně jako typy indikátorů můžete mít ve své databázi DHIS2 již existující trasované typy entit. Odkazy na typ trasované entity by měly být změněny tak, aby odrážely to, co je ve vašem systému, abyste nevytvářeli duplikáty. Tabulka 3 ukazuje identifikátory UID, které lze nahradit, a také koncové body API pro identifikaci stávajících identifikátorů UID + +|Objekt|UID|Koncový bod API| +|--|--|--| +|Osoba|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| + +## Import metadat { #importing-metadata } + +Soubor metadat .json je importován prostřednictvím aplikace [Import/Export] (https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) systému DHIS2. Před pokusem o skutečný import metadat je vhodné použít funkci „suchý běh“ k identifikaci problémů. Pokud „suchý běh“ hlásí nějaké problémy nebo konflikty, podívejte se do níže uvedené části [konflikty importu](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts). Pokud import „na sucho“/„ověření“ funguje bez chyby, zkuste importovat metadata. Pokud import proběhne bez chyb, můžete přejít ke [konfiguraci](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) modulu. V některých případech se konflikty importu nebo problémy nezobrazí během „suchého běhu“, ale zobrazí se při pokusu o skutečný import. V tomto případě bude v souhrnu importu uvedeny všechny chyby, které je třeba vyřešit. + +### Řešení konfliktů importu { #handling-import-conflicts } + +***POZNÁMKA***: Pokud importujete do nové instance DHIS2, nebudete se muset starat o konflikty importu, protože v databázi, do které importujete, není nic, co by bylo v konfliktu. Při importu metadat postupujte podle pokynů, poté pokračujte do části „[Další konfigurace](#additional-configuration)“. + +Může nastat řada různých konfliktů, i když nejběžnější je, že v konfiguračním balíčku jsou objekty metadat se jménem, zkratkou a / nebo kódem, který již v cílové databázi existuje. Existuje několik alternativních řešení těchto problémů s různými výhodami a nevýhodami. Který z nich je vhodnější, bude záviset například na typu objektu, pro který dojde ke konfliktu. + +#### Alternativa 1 { #alternative-1 } + +Přejmenujte existující objekt v databázi DHIS2, u kterého došlo ke konfliktu. Výhodou tohoto přístupu je, že není nutné upravovat soubor .json, protože změny se místo toho provádějí prostřednictvím uživatelského rozhraní DHIS2. Pravděpodobně to bude méně náchylné k chybám. To také znamená, že konfigurační balíček je ponechán tak, jak je, což může být výhodou, například když se použije školicí materiál a dokumentace založená na konfiguračním balíčku. + +#### Alternativa 2 { #alternative-2 } + +Přejmenujte objekt, u kterého došlo ke konfliktu v souboru .json. Výhodou tohoto přístupu je, že stávající metadata DHIS2 jsou ponechána tak, jak jsou. To může být faktor, když existuje školicí materiál nebo dokumentace, jako jsou SOP datových slovníků propojených s daným objektem, a to nezahrnuje žádné riziko záměny uživatelů úpravou metadat, se kterými jsou obeznámeni. + +Všimněte si, že pro alternativu 1 i 2 může být modifikace stejně jednoduchá jako přidání malého pre / post-fix k názvu, aby se minimalizovalo riziko záměny. + +#### Alternativa 3 { #alternative-3 } + +Třetím a komplikovanějším přístupem je úprava souboru .json pro opětovné použití existujících metadat. Například v případech, kdy pro určitý koncept již existuje sada možností (např. „Pohlaví“), by tato sada možností mohla být odstraněna ze souboru .json a všechny odkazy na jeho UID nahrazeny odpovídající sadou možností již v databázi. Velkou výhodou tohoto (která se neomezuje na případy přímého konfliktu importu) je vyhnout se vytváření duplicitních metadat v databázi. Při provádění tohoto typu modifikace je třeba provést několik klíčových úvah: + +* vyžaduje odborné znalosti podrobné struktury metadat DHIS2 +* přístup nefunguje u všech typů objektů. Zejména určité typy objektů mají závislosti, které se tímto způsobem komplikovaně řeší, například v souvislosti s rozčleněními. +* budoucí aktualizace konfiguračního balíčku budou komplikované. + +## Další konfigurace { #additional-configuration } + +Po úspěšném importu všech metadat existuje několik kroků, které je třeba provést, než bude modul funkční. + +### Sdílení { #sharing } + +Nejprve budete muset pomocí funkce *Sdílení* DHIS2 konfigurovat, kteří uživatelé (skupiny uživatelů) by měli vidět metadata a data spojená s programem a kdo může registrovat / zadávat data do programu. Ve výchozím nastavení bylo sdílení nakonfigurováno pro následující: + +* Typ trasované entity +* Program +* Fáze programu +* Ovládací panely + +Balíček obsahuje tři skupiny uživatelů: + +* COVID19 Přístup +* COVID19 admin +* COVID 19 Sběr dat  + +Ve výchozím nastavení je těmto skupinám uživatelů přiřazeno následující + +|Objekt|Uživatelská skupina||| +|--|--|--|--| +||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| +|_*Typ trasované entity*_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata: lze zobrazit
Data: lze zachytit a zobrazit| +|_*Program*_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata: lze zobrazit
Data: lze zachytit a zobrazit| +|_*Fáze programu*_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata: lze zobrazit
Data: lze zachytit a zobrazit| +|_*Ovládací panely*_|Metadata : lze zobrazit
Data: lze zobrazit|Metadata: lze upravovat a prohlížet
Data: lze zobrazit|Metadata : lze zobrazit
Data: lze zobrazit| + +Budete chtít přiřadit své uživatele k příslušné skupině uživatelů na základě jejich role v systému. V závislosti na vašem nastavení můžete chtít povolit sdílení pro jiné objekty v balíčku. Další informace o konfiguraci sdílení najdete v [dokumentaci DHIS2](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). + +### Uživatelské role { #user-roles } + +Uživatelé budou potřebovat uživatelské role, aby mohli pracovat s různými aplikacemi v rámci DHIS2. Doporučují se následující minimální role: + +1. Analýza dat trasovače: Může zobrazit analytiku událostí a přistupovat k ovládacím panelům, zprávám o událostech, vizualizátorům událostí, vizualizátorům dat, kontingenčním tabulkám, zprávám a mapám. +2. Zachycování dat Trasovače: Může přidávat datové hodnoty, aktualizovat trasované entity, prohledávat trasované entity napříč organizačními jednotkami a přistupovat k zachycení trasovačů + +Další informace o konfiguraci rolí uživatelů najdete v [dokumentaci DHIS2](https://docs.dhis2.org). + +### Organizační jednotky { #organisation-units } + +Program musíte přiřadit organizačním jednotkám v rámci vaší vlastní hierarchie, aby bylo možné program vidět v záznamu trasovače. + +### Duplikovaná metadata { #duplicated-metadata } + +**POZNÁMKA**: Tato část platí pouze v případě, že importujete do databáze DHIS2, ve které již existují metadata. Pokud pracujete s novou instancí DHIS2, přeskočte tuto část a přejděte na [Přizpůsobení trasovacího programu](#adapting-the-tracker-program).“ + +I když byla metadata úspěšně importována bez jakýchkoli konfliktů při importu, v metadatech mohou existovat duplikáty - datové prvky, trasované atributy entit nebo sady voleb, které již existují. Jak bylo uvedeno v části výše o řešení konfliktů, je třeba mít na paměti důležitý problém, že rozhodnutí o provádění změn metadat v DHIS2 musí také zohledňovat další dokumenty a zdroje, které jsou různými způsoby spojeny s existujícími metadaty a metadata, která byla importována prostřednictvím konfiguračního balíčku. Vyřešení duplikátů tedy není jen otázkou „vyčištění databáze“, ale také zajištěním toho, aby se tak dělo například bez narušení potenciálu integrace s jinými systémy, možnosti použít školicí materiál, rozbití SOP atd. To bude velmi záviset na kontextu. + +Jedna důležitá věc, kterou je třeba mít na paměti, je, že DHIS2 má nástroje, které mohou skrýt některé složitosti potenciálních duplikací v metadatech. Například tam, kde existují duplicitní sady možností, mohou být skryty pro skupiny uživatelů prostřednictvím [sdílení](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/about-sharing-of-objects.html). + +## Přizpůsobení trasovacího programu { #adapting-the-tracker-program } + +Po importu programu můžete provést určité úpravy programu. Mezi příklady místních úprav, které *lze* provést, patří: + +* Přidání dalších proměnných do formuláře. +* Přizpůsobení názvů datových prvků / možností podle národních konvencí. +* Přidávání překladů do proměnných nebo do formuláře pro zadávání údajů. +* Úprava indikátorů programu na základě místních definic případů + +Důrazně se však doporučuje věnovat velkou pozornost, pokud se rozhodnete změnit nebo odebrat některý ze zahrnutých formulářů / metadat. Existuje nebezpečí, že by úpravy mohly narušit funkčnost, například pravidla programu a indikátory programu. + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md new file mode 100644 index 00000000..97dd74ce --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md @@ -0,0 +1,29 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/overview.md" +revision_date: '2022-11-22' +tags: +- Implementace +--- + +# COVID-19 Case Surveillance { #covid-19-case-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-cs-release-note) + +## Design { #design } + +- [Version 1.0.2](#c19-cs-design) + +## Instalace { #installation } + +- [Installation Guide](#c19-cs-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 1.0.2](https://packages.dhis2.org/en/C19_CS/1.0.2/C19_CS_COMPLETE_1.0.2_DHIS2.37.xlsx) + +## Training Material { #training-material } + +- [COVID-19 Training Material](https://dhis2.org/covid-training-material) + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..26b54588 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implementace +--- + +# Poznámka k vydání { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Přehled { #overview } + +Provedli jsme několik aktualizací stávajícího balíčku, abychom se přizpůsobili novým pokynům COVID-19 [pokyny ke sledování vydané WHO 20. března 2020](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) a zavedly nové komponenty do celkového balíčku podpory. Přečtěte si prosím poznámky zde a kontaktujte nás na diskusním fóru COVID-19 v [community of practice](https://community.dhis2.org/c/implementation/covid-19/) s případnými dotazy. + +**Všechny balíčky metadat a dokumentaci lze stáhnout z [dhis2.org.covid-19](https://www.dhis2.org/covid-19).** + +Balíčky jsou v současné době přeloženy do francouzštiny, španělštiny, portugalštiny a ruštiny a připravují se další jazyky (arabština, laosština, barmština). Můžeme podporovat překlady balíčků metadat na naší globální překladatelské platformě a pozvat komunitu, aby přispěla, pokud má vaše země zájem o překlad balíčku do nového jazyka. [Podívejte se na oznámení naší komunity praxe] (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). Kontaktujte nás prosím na translate@dhis2.org. + +Nové vydání obsahuje: + +1. Program trasování případů COVID-19 +2. COVID-19 Contact Registration & Follow-Up program +3. Souhrnné přehledové hlášení COVID-19 +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Kódy metadat byly aktualizovány tak, aby odpovídaly [Datovému slovníku případových zpráv WHO](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Programové ukazatele byly aktualizovány tak, aby odrážely nové definice případů WHO pro pravděpodobné případy (viz aktualizované definice případů v prozatímních pokynech pro dohled aktualizovaných 20. března 2020 [Prozatímní pokyny pro dohled WHO aktualizovány 20. března 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Věkové legendy byly aktualizovány, aby splňovaly nové pokyny WHO pro týdenní podávání zpráv +4. relationshipType přidán do balíčku metadat +5. Drobné opravy metadat umožňující snazší instalaci balíčku (tj. UID indikátorType odpovídá typu indikátoru obsaženému v agregovaném balíčku) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. Byla přidána nová programová fáze, která umožňuje opakovatelné „sledování“ kontaktu s případem. Toto bylo přidáno, aby odráželo pracovní postupy implementované v Ugandě a Togu, kde lze kontakty opakovaně monitorovat v průběhu 14 dnů, aby se zjistilo, zda existují příznaky. ***program*** je založen na pokynech WHO, které lze nalézt [zde](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), jakož i informace získané prostřednictvím webu [OpenWHO] (https://openwho.org/courses/introduction-to-ncov). +2. Věkové legendy byly aktualizovány, aby splňovaly nové pokyny WHO pro týdenní podávání zpráv +3. relationshipType přidán do balíčku metadat +4. Drobné opravy metadat umožňující snazší instalaci balíčku + +### Souhrnné přehledové zprávy COVID-19 { #covid-19-aggregate-surveillance-reporting } + +Následující aktualizace byly provedeny, aby odrážely nové pokyny v [Pokyny WHO aktualizovány 20. března 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), včetně aktualizovaných globálních souhrnných zpráv pro WHO (týdně a denně) + +1. Věkové kategorie aktualizovány podle nových věkových skupin +2. Byly přidány nové indikátory podílu mužů mezi potvrzenými případy a podílu mužů mezi potvrzenými úmrtími +3. Nový týdenní datový soubor pro zachycení klasifikace přenosu na nižší než národní úrovni (tj. Na krajské úrovni - lze jej podle potřeby přiřadit k jakékoli nižší než národní úrovni v zemi) podle aktualizovaných pokynů WHO pro týdenní podávání zpráv +4. Drobné opravy metadat umožňující snazší instalaci balíčku + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +Případ použití trasovače programu Místa Vstupu byl navržen tak, aby podporoval registraci cestujících vstupujících do země s historií cestování do země / oblasti / teritoria hlásící místní přenos COVID-19, u nichž může být nutné sledovat aby nedošlo k rozvoji příznaků. Je založen na koncepci implementované HISP Srí Lanka na podporu Ministerstva zdravotnictví Srí Lanky s malými změnami, aby byl program obecnější pro globální použití a aby byl v souladu s ostatními sledovacími programy v balíčku COVID-19. Balíček podporuje intervence ve vstupních místech podrobně popsaných ve WHO [technické pokyny pro správu nemocných osob ve vstupních místech](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings). + +Přečtěte si více o programu POE v [dokumentu návrhu systému] (https://docs.dhis2.org/en/topics/metadata/covid-19-surveillance/covid-19-poe-tracker-design.html). + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md new file mode 100644 index 00000000..363cbad9 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -0,0 +1,136 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/c19_poe-design.md" +revision_date: '2022-07-05' +tags: +- Implementace +--- + +# COVID-19 Points of Entry Tracker Design { #c19-poe-design } + +Demo: [https://covid19.dhis2.org/](https://covid19.dhis2.org/demo) + +## Účel { #purpose } + +Dokument COVID-19 Points of Entry (POE) Screening System Design poskytuje přehled koncepčního designu použitého ke konfiguraci balíčku digitálních dat COVID-19 v DHIS2. Balíček COVID-19 byl vyvinut v reakci na výslovnou potřebu zemí rychle přizpůsobit řešení pro správu dat COVID-19. Tento dokument je určen k použití implementátory DHIS2 na národní a regionální úrovni, aby mohli podporovat implementaci a lokalizaci balíčku. Balíček metadat COVID-19 lze přizpůsobit místním potřebám a národním pokynům. Při lokalizaci a přijímání programů obsažených v tomto balíčku by měly být brány v úvahu zejména místní pracovní toky a národní pokyny. + +## Pozadí { #background } + +Points of Entry Screening Tracker je inspirován průkopnickým designem implementovaným HISP Srí Lanka na podporu ministerstva zdravotnictví Srí Lanky. V lednu 2020 provedlo MOH na Srí Lance screeningová opatření v místech vstupu, jako jsou letiště, za účelem identifikace cestujících, kteří mohli být vystaveni nCoV-19. Trasovač DHIS2 měl registrovat cestující vstupující na Srí Lanku, kteří navštívili země zasažené COVID-19. Trasovač DHIS2 umožnil sledování cestujících v terénu po dobu 14 dnů, aby se zajistilo, že se nevyvinou žádné příznaky. Pokud by se příznaky vyvinuly, cestující by byli posláni do zdravotnického zařízení ke klinickému vyšetření a testování. Trasovač POE lze použít v kombinaci s dalšími digitálními datovými balíčky COVID-19, které zahrnují sledování případů a trasování kontaktů. + +Světová zdravotnická organizace (WHO) zveřejnila [technické pokyny pro správu nemocných v místech vstupu](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings). Mezi body vstupu (POE) patří mezinárodní letiště, námořní přístavy a pozemní přechody. Opatření POE zahrnují 1) detekci nemocných cestujících; 2) rozhovor s nemocnými cestujícími pro COVID-19; 3) hlášení výstrah nemocných cestujících s podezřením na infekci COVID-19 a 4) izolace, počáteční řízení případů a doporučení nemocných cestujících s podezřením na infekci COVID-19. Tyto pokyny by měly být konzultovány, včetně národních protokolů pro místa vstupu. + +## Souhrn návrhu systému { #system-design-summary } + +### Případ použití { #use-case } + +Případ použití programu POE trasovač byl navržen tak, aby podporoval registraci cestujících vstupujících do země s historií cestování nebo pobytu v zemi / oblasti / území hlásící místní přenos COVID-19, u nichž může být nutné sledovat, aby bylo zajištěno že se nevyvíjejí žádné příznaky. Pro tento případ použití se předpokládá, že cestující může být 1) podroben detekční kontrole a okamžitému odbavení bez nutnosti následných opatření; 2) vyšetřován a sledován po dobu 14 dnů [s nebo bez izolačních opatření], aby se zajistilo, že se nevyvinou žádné příznaky; nebo 3) prověřeny a odeslány k testování a / nebo počáteční správě případů. Současný návrh navrhuje, aby cestující, který splňuje definici podezřelého případu v zemi, byl zařazen do doplňkového sledovače případu Surveillance (CBS) DHIS2 COVID-19. Například cestující zapsaný v tomto programu, který později splní definici podezřelého případu během sledování (tj. Asymptomatický cestující ze země se známým přenosem je registrován na POE a později se u něj objeví příznaky) je zapsán jako podezřelý případ do program COVID-19 CBS k zachycení všech klinických detailů, expozic a sledování případu prostřednictvím laboratorní diagnostiky a výsledku případu. + +Při vývoji tohoto konfiguračního balíčku bylo vyvinuto úsilí dodržovat [obecné zásady návrhu] (https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) od UiO a společnou [konvenci pojmenování] (https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +Balíčky digitálních dat DHIS2 jsou optimalizovány pro sběr dat Android pomocí aplikace DHIS2 Capture, kterou si můžete zdarma stáhnout v [obchodu Google Play](https://play.google.com/store/apps/details?id=com.dhis2&hl=en). + +### Předpokládaní uživatelé { #intended-users } + +* Uživatelé POE: pracovníci odpovědní za detekční kontrolu cestujících na vstupních místech, jako jsou letiště, námořní přístavy a pozemní přechody, kteří mohou provést počáteční detekční kontrolu na POE, učinit rozhodnutí o odbavení cestujícího a zaregistrovat cestujícího do programu Tracker. +* Pracovníci veřejného zdravotnictví: pracovníci odpovědní za sledování cestujících po dobu 14 dnů, aby se informovali o nástupu příznaků a v případě potřeby poslali osobu k testování. +* Vnitrostátní a místní zdravotní úřady: sledují a analyzují data pomocí ovládacích panelů a analytických nástrojů k provádění hodnocení rizik a plánování opatření reakce. + +### Pracovní postup { #workflow } + +Pracovní postup programu Points of Entry je založen na následujícím scénáři + +![Scénář](resources/images/POE_image01.png "Scénář") + +V tomto návrhu se předpokládá, že cestující dokončí svůj zápis v POE v následujících scénářích: + +1. Cestující je během úvodního vyšetření nebo po 14denním sledování označen jako „čistý“ +2. Cestující je kdykoli během sledování odeslán do zdravotnického zařízení + +**A traveler that is referred to a health facility is expected to be enrolled in the COVID-19 Case-based Surveillance Tracker as a suspected case** (according to national guidelines). Details about a suspected case including clinical exam, exposures, laboratory results and case outcome would be recorded in the CBS program. + +### Structure: Points of Entry Screening Tracker Program { #structure-points-of-entry-screening-tracker-program } + +![Struktura](resources/images/POE_image02.png "Struktura") + +#### Consideration for Organisation Units & Geography { #consideration-for-organisation-units-geography } + +Tento návrh programu předpokládá, že vstupní body, jako jsou letiště, námořní přístavy nebo pozemní přechody, budou vytvořeny jako organizační jednotky zahrnuté v hierarchii Organizačních jednotek. Program by byl přiřazen organizačním jednotkám POE. Primární analýza je založena na zápisu Organizačních jednotek (vstupní body). + +Další geografické komponenty jsou také zachyceny jako jiné dimenze: + +1. Souřadnice TEI: Při registraci cestovatele jako TEI je možné zachytit souřadnice TEI. Ty lze zobrazit v aplikaci Mapy. Místní protokoly mohou zvolit, jaké souřadnice zadat, například místní bydliště TEI, kde může být 14 dní v karanténě. +2. Souřadnice události: pro screeningové a následné fáze lze souřadnice zachytit na události a zobrazit na mapě. Uživatel může například zachytit polohu cestovatele pokaždé, když je sledován (tj. V případě turistů nebo jiných, kteří nejsou v domácí karanténě). + +#### Program Description { #program-description } + +|Fáze|Popis| +|--|--| +|**Registrace**|Trasovaná entita je cestovatel, který je reprezentován typem trasované entity „osoba“. TEI je nakonfigurován tak, aby během registrace shromažďoval geografický „bod“. Ty lze analyzovat na mapě.| +|**Podrobnosti o zápisu**|Datum zápisu
První fáze programu je nakonfigurována tak, aby se zobrazovala na stránce Registrace, takže uživatel nemusí kliknout a přidat první událost.| +|**Atributy**|Atributy zahrnují základní osobní údaje a jedinečných identifikátorů případu
- číslo pasu
- ID místního případu
- Věk
- Jméno
- Příjmení
- země trvalého bydliště
- Pohlaví
- Datum narození
- Místní adresa
- adresa bydliště
- Telefon (místní)
- Telefon (zahraniční)
- Nouzový kontakt
- Telefon pro nouzový kontakt
- E-mail| +|**Fáze 1**
**Screening na POE**
**(neopakující se)**|Tato fáze zaznamenává:
- podrobnosti o cestujících (navštívené země, číslo letu, datum odletu atd.)
- vyšetření: zaznamenaná teplota
- příznaky: tento seznam obsahuje příznaky obvykle kontrolované jak na příznaky COVID-19, tak na příznaky dalších potenciálních chorob podléhajících hlášení
- Vyřešení případu

Pokud je cestující označen jako „čistý“, není nutná žádná další kontrola; zápis může být uzavřen. Pokud cestující vyžaduje sledování, lze naplánovat událost pro sledování.

Formulář pro zadávání dat je po dokončení blokován; bez povolení nelze provádět žádné další změny.| +|**Fáze 2:**
**Sledování (do 14 dnů)**
**(opakovatelné)**|V této fázi se zadávají údaje, pokud dojde k prozatímnímu sledování před koncem 14 dnů. Je možné zachytit souřadnice události (tj. Aktuální polohu cestovatele v době, kdy bylo dokončeno sledování) a zobrazit ji na mapě.
- Příznaky
- Doporučení (uživatel může vybrat organizační jednotku v datovém prvku nakonfigurovaném jako typ Org. jednotky, například pro výběr zdravotnického zařízení, kam byl cestující odkázán po nahlášení příznaků)

Pokud je cestující odkázán na příznaky zdravotnické zařízení pro testování, cestující by měl být zapsán do programu sledování na základě případů. Registrace může být uzavřena, pokud v tomto programu není plánováno žádné další monitorování a následná opatření.

Formulář pro zadávání dat je po dokončení blokován; bez povolení nelze provádět žádné další změny.| +|**Fáze 3:**
**Sledování (po 14 dnech)**
**(neopakující se)**|Data se v této fázi zadávají na konci 14 dnů. Je možné zachytit souřadnice události (tj. Aktuální polohu cestovatele v době, kdy bylo dokončeno sledování) a zobrazit ji na mapě.
- Příznaky
- Doporučení (uživatel může vybrat organizační jednotku v datovém prvku nakonfigurovaném jako typ Organizační jednotky, například pro výběr zdravotnického zařízení, kam byl cestující odkázán po nahlášení příznaků)
- Vymazání případu

a cestující by měl být zařazen do programu sledování na základě případů. Zápis by měla být uzavřen po dokončení 14denního sledování.

Formulář pro zadávání dat je po dokončení blokován; bez povolení nelze provádět žádné další změny. + +![Zápis](resources/images/POE_image03.png "Zápis") + +![Programová Fáze 1 – Promítání v POE](resources/images/POE_image04.png "Programová Fáze 1 - Promítání v POE") + +![Programová Fáze 1 – Promítání v POE](resources/images/POE_image05.png "Programová Fáze 1 - Promítání v POE") + +![Programová fáze 2: Následná kontrola (do 14 dnů)](resources/images/POE_image06.png "Programová fáze 2: Následná kontrola (do 14 dnů)") + +![Programová fáze 3: Následná kontrola (po 14 dnech)](resources/images/POE_image07.png "Programová fáze 3: Následná kontrola (po 14 dnech)") + +#### How to refer the TEI to another Organisation Unit { #how-to-refer-the-tei-to-another-organisation-unit } + +Primární analýza je dokončena na přijímající organizační jednotce (vstupní port). Zařízení doporučení je zachyceno jako datový prvek (typ: organizační jednotka) za účelem zobrazení cestujících podle doporučení do zdravotnického zařízení v analytických aplikacích (tj. Zpráva o události). V některých případech použití může být žádoucí odkázat TEI (cestujícího) na další organizační jednotku k následnému sledování. + +TEI lze ‘předat‘ jiné organizační jednotce, například zdravotnickému zařízení, pro jednu událost nebo trvale. V takovém případě musí být uživatel zdravotnického zařízení schopen vyhledávat TEI zapsané v příslušných organizačních jednotkách bodů vstupu. Pokud například po prověření cestujícího v POE může být cestující „odkázán“ na okresní zdravotní úřad poblíž místní adresy cestujícího, aby jej mohli dále sledovat okresní zdravotníci. Po dokončení zadávání údajů pro 1. fázi (screening) by uživatel doporučil TEI na okresní zdravotní středisko. Přečtěte si více o doporučeních ve trasovači v [Uživatelská dokumentace DHIS2] (https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/tracking-individual-level-data/tracker-capture.html). + +![alt_text](resources/images/POE_image08.png "image_tooltip") + +### Program Relationships { #program-relationships } + +Tento program má vztah typu „Byl v kontaktu“. Uživatelé mohou vytvořit vztah mezi TEI zapsanými v programu POE a TEI v jiných trasovacích programech COVID-19 (Case-based Surveillance, Contact Registration & Follow-up). Vztah lze přidat kdykoli ve fázích programu během zadávání dat. + +### Pravidla programu { #program-rules } + +Byla nakonfigurována následující pravidla programu. + +|Název pravidla programu|Popis pravidla programu| +|--|--| +|Vypočítejte a přiřaďte věk pacienta v letech|Vypočítejte a přiřaďte věk pacienta v letech| +|Skrýt země, pokud nejsou navštíveny|Skrýt země, pokud nejsou navštíveny| +|Skrýt následné fáze|Skrýt následné fáze, pokud je případ vymazán v Bodě vstupu| +|Skrýt příznaky, pokud nejsou přítomny žádné příznaky (sledování na konci 14 dnů)|Skrýt příznaky, pokud nejsou přítomny žádné příznaky (sledování na konci 14 dnů)| +|Skrýt příznaky, pokud nejsou přítomny žádné příznaky (sledování do 14 dnů)|Skrýt příznaky, pokud nejsou přítomny žádné příznaky (sledování do 14 dnů)| +|Skrýt příznaky, pokud nejsou přítomny žádné příznaky (PoE)|Skrýt příznaky, pokud nejsou přítomny žádné příznaky (PoE)| + +You can read more about program rules here: +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +||| +|--|--| +|Cestovatelé COVID-19 byli prověřeni|Celkový počet cestujících prověřených a zapsaných do screeningového programu z POE| +|COVID-19 cestující, kteří byli odbaveni na POE|Počet cestujících odbavených po kontrole POE (není nutná žádná další kontrola)| +|COVID-19 cestující s příznaky na POE|Počet cestujících s příznaky během screeningu POE| +|COVID-19 cestující, kteří byli čistí po 14 dnech monitorování|Počet cestujících, kteří jsou vymazáni po 14denním sledování (žádný nástup příznaků během 14denního období)| +|COVID-19 cestující, kteří se obrátili na zdravotnické zařízení|Počet cestujících, kteří byli posláni do zdravotnického zařízení kdykoli během 14denního sledování| +|Cestující COVID-19 se zapsali na 14denní sledování|Počet cestujících, u kterých se při screeningu POE neprojevily příznaky a při screeningu POE nebyli odmazáni| +|COVID-19 je v současné době sledován|Počet cestujících, kteří nebyli odbaveni nebo odesláni do zdravotnického zařízení| +|COVID-19 cestující, u kterých se během sledování objevily příznaky|Počet cestujících, u kterých se během sledování vyvinuly příznaky (nezahrnujte cestující, kteří mají příznaky během screeningu POE)| +|COVID-19 % cestujících kde se příznaky objevily během 14denního sledování|Čitatel: Počet cestujících, u kterých se během sledování vyvinuly příznaky (kromě cestujících s příznaky během screeningu POE)
Jmenovatel: Počet cestujících, u kterých se při screeningu POE neprojevily příznaky a při screeningu POE nebyli vyčištěni.| + +Uživatelé také mohou vygenerovat zprávu o události, aby viděli: + +1. Cestující podle státní příslušnosti a / nebo země původu +2. Doporučení zdravotnickému zařízení + +## Reference { #references } + +* DHIS2 COVID-19 [Průvodce instalací balíčku Tracker](covid-19-tracker-installation.html) +* Světová zdravotnická organizace (WHO) [technické pokyny pro správu nemocných osob na vstupních místech](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings) (prozatímní pokyny, zveřejněné 19. března 2020) + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md new file mode 100644 index 00000000..18d43780 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implementace +--- + +# COVID-19 Points of Entry { #covid-19-points-of-entry } + +## Design { #design } + +[Verze 1.0.2](#c19-poe-design) + +## Instalace { #installation } + +[Průvodce instalací](#c19-poe-installation) + +## Release Note { #release-note } + +[Poznámka k vydání](#c19-poe-release-note) + +## Metadata Reference { #metadata-reference } + +[Version 1.0.2](https://packages.dhis2.org/en/C19_POE/1.0.2/C19_POE_COMPLETE_1.0.2_DHIS2.37.xlsx) + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md new file mode 100644 index 00000000..802aa536 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -0,0 +1,164 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/c19_evt-design.md" +revision_date: '2022-11-08' +tags: +- Implementace +--- + +# COVID-19 Surveillance Line-list Design { #c19-evt-design } + +Demo: [https://covid.dhis2.org](https://covid.dhis2.org/demo) + +## Účel { #purpose } + +Dokument Návrh programu systému sledování událostí COVID-19 poskytuje přehled principů návrhu a pokynů použitých k vývoji balíčku digitálních dat pro souhrnný dohled COVID-19. Tento dokument je určen k použití implementátory DHIS2 na národní a regionální úrovni, aby mohli podporovat implementaci a lokalizaci balíčku. Balíček metadat COVID-19 lze přizpůsobit místním potřebám a národním pokynům. Při lokalizaci a přijímání programů obsažených v tomto balíčku by měly být brány v úvahu zejména místní pracovní toky a národní pokyny. + +## Pozadí { #background } + +Balíček digitálních dat COVID-19 byl vyvinut v reakci na výslovnou potřebu zemí rychle přizpůsobit řešení pro správu dat COVID-19. UiO vyvinula sledovací balíčky COVID-19 pro tři typy datových modelů (trasovač, agregace založené na událostech), aby umožnila zemím vybrat model, který je nejvhodnější pro jejich kontext s ohledem na zátěž nemocí a dostupné zdroje. Níže jsou shrnuty tyto modely a jejich relativní výhody / omezení: + +|Typ balíčku sledování|Sledování případu (Trasovač)|Sledování (událost)|Pozorování (Agregované)| +|--|--|--|--| +|_Popis_|Zapište případ a sleduje časem laboratorní potvrzení a výsledek případu|Zachycuje podrobnosti kritických případů ve formátu seznamu řádků|Umožňuje denní nebo týdenní hlášení klíčových agregovaných datových bodů| +|_Výhody_|Vysoce strukturovaná data a více časových dimenzí pro analýzu mohou podporovat decentralizovaný pracovní postup, všechny události spojené s případem|Podrobnější než agregované a dokáže zachytit klíčové časové dimenze (tj. Datum zprávy vs. nástup příznaků); snížená zátěž při zadávání dat ve srovnání se trasovačem a malá složitost|Nízká složitost, snadná implementace, zvládnutelnost, když je počet případů vysoký| +|_Nevýhody_|Břemeno zadávání dat může být ohromující, když počet případů dosáhne prahové hodnoty; složitost implementace|Nepodporuje sledování případů ani jiné decentralizované pracovní postupy|Menší podrobnost pro podrobnou analýzu (tj. Analýza pouze na základě data hlášení případu, omezené členění) + +**Tento dokument se vztahuje pouze na návrh programového balíčku událostí dozoru**; pro DHIS2 Trasovač a agregované balíčky jsou k dispozici samostatné dokumenty návrhu systému. + +WHO „žádá všechny země, aby se připravily na potenciální příchod COVID-19 tím, že připraví systémy reakce na mimořádné události; zvýšení kapacity pro odhalování a péči o pacienty; zajištění toho, aby nemocnice měly prostor, zásoby a potřebný personál; a vývoj záchranných lékařských zásahů.“ + +Cíle dozoru COVID-19 jsou: + +1. sledovat trendy choroby, při které dochází k přenosu z člověka na člověka; +2. rychle odhalit nové případy v zemích, kde virus necirkuluje; +3. a poskytovat epidemiologické informace k provádění hodnocení rizik na národní, regionální a globální úrovni; a +4. poskytovat epidemiologické informace jako vodítko pro opatření připravenosti a reakce. + +Návrh systému vychází ze stávajících zásad dozoru nad chorobami a požadavků na informační systém, které byly vyvinuty ve spolupráci WHO a UiO od roku 2017. Balíček COVID-19 byl vyvinut s úmyslem sladit s [technickými pokyny WHO pro dozor a případy nCoV-19 definice](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), naposledy aktualizováno 20. března 2020. Upozorňujeme, že tento návrh nemusí nutně odrážejí nejnovější dostupné prozatímní globální pokyny vyvinuté WHO, protože aktualizace mohou být vydávány rychle. Národní směrnice a zásady se mohou lišit a doporučuje se přizpůsobit tento balíček místním kontextům. + +## Souhrn návrhu systému { #system-design-summary } + +Tento balíček je navržen jako DHIS2 [Event Program](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#about_event_program). **Program událostí není určen k zachycení všech proměnných údajů obsažených v [šabloně pro hlášení případů WHO](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx)**. Chcete-li zachytit kompletní soubor proměnných hlášení případů WHO, nahlédněte do DHIS2 COVID-19 Case-based Surveillance Tracker. Program událostí je spíše zjednodušený program, který zachycuje podmnožinu minimálních kritických datových bodů, aby usnadnil vysokou kvalitu údajů v případech, kdy počet případů nebo zátěž hlášení přesahuje kapacitu pro úspěšné vyplnění celého seznamu řádků pro podezření na případy COVID-19. Pro realizátory, kteří si přejí zachytit kompletní line-list WHO, je určen balíček pro sledování případů COVID-19. + +Datový balíček COVID-19 Surveillance Event Program obsahuje: + +1. Hlášení událostí a datových prvků v programu událostí +2. Základní indikátory +3. Ovládací panel + +### Use Case: Simplified line-listing of COVID-19 cases { #use-case-simplified-line-listing-of-covid-19-cases } + +Vzhledem k rychlému nárůstu počtu případů mohou mít některé země s hlášením případů problémy, protože zátěž bude příliš vysoká. Balíček událostí je navržen tak, aby zachycoval nejkritičtější datové body v podobě řádkového seznamu a analytických kapacit pro dohled a reakci. Balíček událostí je navržen jako samostatný program. Země však mohou balíček událostí používat v kombinaci s dalšími balíčky (tj. hlášení o událostech a denní souhrnné hlášení); nebo mohou přecházet od sledování událostí k souhrnnému hlášení, jakmile se zvýší počet případů a zátěž hlášení. **_Země by měly pečlivě naplánovat, jak hodlají tyto balíčky v kombinaci implementovat, včetně toků hlášení, přechodu z jednoho datového modelu na druhý a způsobu zachování historických dat pro analýzu v případě přechodu mezi datovými modely. _** + +Návrh programu pro vypisování řádků založeného na událostech předpokládá, že [definice případů WHO](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) jsou dodrženy v případě použití; země by se měly řídit vnitrostátními definicemi případů pro klasifikaci případů jako podezřelých, pravděpodobných nebo potvrzených. + +#### Předpokládaní uživatelé { #intended-users } + +* Uživatelé zdravotnických zařízení: zachyťte a nahlaste klíčová data o případech a úmrtích COVID-19 ve zdravotnickém zařízení +* Národní a místní zdravotní úřady: monitorují a analyzují údaje o sledování nemocí prostřednictvím ovládacích panelů a analytických nástrojů k provádění hodnocení rizik a plánování opatření reakce; generovat zprávy pro regionální a globální zprávy + +#### Pracovní postup { #workflow } + +Na rozdíl od trasovacího programu existují omezení decentralizace pracovního postupu hlášení dat v programu událostí. Nejvýznamnějším omezením je, že výsledek případu (uzdravení nebo úmrtí) není často znám až do dnů nebo týdnů po nahlášení případu. Aktuální návrh programu umožňuje následující možnosti pracovního postupu: + +1. Událost se vytvoří, když je nahlášen podezřelý případ. Jsou zadány všechny známé údaje, ale událost není dokončena. Uživatel může vybrat "aktivní událost" z pracovního seznamu na základě uživatelských filtrů a kritérií. Jakmile jsou k dispozici chybějící údaje (tj. výsledek případu), může uživatel zadat zbývající datová pole a událost dokončit. Případy lze v seznamu událostí identifikovat pomocí datového prvku Case ID. Jako příklad viz obrázek níže, který je přístupný v aplikaci Capture App: +![Capture App](resources/images/EVENT_image1.png "Capture App") + +2. Událost je vytvořena. Všechny údaje související s případy se zadávají zpětně, včetně výsledku. Událost je dokončena. _Omezením tohoto přístupu je včasnost vykazování údajů, protože nové podezřelé případy nemusí být zachyceny až do jejich výsledku, který je často příliš pozdě na rozhodování._ + +### Struktura programu { #program-structure } + +Tento program se nazývá „Případy (události) COVID-19“ + +|Sekce|Popis| +|--|--| +|Datum zprávy|Datum události
_Země mohou datum události přejmenovat, aby se vztahovalo na jejich protokoly._| +|Část 1
**Základní informace**|Zaznamenává základní demografické údaje.
_Země mohou podle potřeby přidávat datové prvky._
- **ID pacienta**
Lze použít k filtrování událostí v pracovních seznamech, např. Aktivní události
- **Pohlaví**
- **Věk**| +|Část 2
Podrobnosti případu|Zaznamenává informace o případu včetně příznaků, závažnosti, testování atd.
- **Příznaky**
Možnosti: Ano / Ne
Určuje, zda má případ v době oznámení nějaké příznaky

**Datum nástupu příznaků**
Zobrazí se, pouze pokud jsou přítomny příznaky;
Datum nástupu příznaků, pokud je k dispozici, nahradí v analýze a hlášení dat „Datum hlášení“.

- **Závažnost případu (v době oznámení)**
Možnosti: Mírné / Střední / Těžké / Kritické
- **Laboratorně testováno?**
Možnosti: Ano / Ne / Neznámý
Určuje, zda byl případ laboratorně testován na COVID-19

- **Výsledek testu**
Zobrazí se pouze v případě, že byl případ laboratorně testován
Možnosti: Nejasný / Pozitivní / Negativní / Neznámý
Program je navržen tak, aby zachytil pouze konečný výsledek testu. Výsledky jednotlivých testů (jsou-li k dispozici) a celkový počet provedených testů se nezachycují.
- **Klasifikace případů**
Možnosti: Podezřelý případ / Pravděpodobný případ / Laboratorně potvrzený případ
Automaticky přiřazené hodnoty
Hodnoty jsou přiřazeny pravidly programu v souladu s definicemi případu WHO
Tato funkce může být užitečná při filtrování aktivních případů v pracovních seznamech.| +|Část 3
**Expozice**|- **Cestoval případ 14 dní před nástupem příznaků?**
Možnosti: Ano / Ne / Neznámý
Určuje historii cestování případu.

- **Pravděpodobný zdroj infekce**
Možnosti: Importovaný případ* / Místní přenos / Nakažení neznámé
* Možnost importovaného případu se zobrazí pouze v případě, že případ vycestoval do 14 dnů před nástupem příznaků

- **Uveďte místní zdroj**
Zobrazí se, pouze pokud je pravděpodobným zdrojem infekce místní přenos
Možnosti: Komunita (pracoviště, veřejná doprava atd.) / Domácnost / Zdravotnické zařízení / Blízký kontakt s jiným infikovaným jednotlivcem / Neznámé nakažení

**Typ případu**
Možnosti: Nový případ indexu / Propojeno se stávajícím klastrem / Neznámý
Určuje, zda je případ připojen ke stávajícímu klastru nebo jde o nový případ indexu| +|Část 4
**Léčba**|- **Hospitalizován**
Možnosti: Ano / Ne

- **Dostal případ péči na jednotce intenzivní péče (JIP)?**
Zobrazí se pouze v případě, že je případ hospitalizován
Možnosti: Ano / Ne| +|Část 5
**Kontakty**|- **Celkový počet kontaktů sledovaných v tomto případě**
Zaznamenává počet kontaktů| +|Část 6
**Výsledek**|- **Výsledný zdravotní stav**
Možnosti: Uzdravení / Úmrtí| +|Část 7
**Přiřazeno Datum nástupu příznaků**|- **Vypočítané datum nástupu (pro indikátory)**
Tato část se používá pouze k výpočtu indikátorů na základě data zprávy vs. data nástupu příznaků]
Toto automaticky přiřazené datum se používá v indikátorech programu. Zpočátku je to datum zprávy. Pokud je k dispozici datum nástupu příznaků, je datum nahrazeno datem nástupu příznaků.| +|**Status**|**Toto je obecné pole obsažené ve všech programech událostí**
**úplná událost**
Možnost: ano
Událost by měla být označena jako „úplná“, pouze pokud bylo dokončeno zadávání všech údajů. Pokud uživatel čeká na vyplnění určitých polí (například výsledek případu), událost by neměla být dokončena.
Události, které nejsou označeny jako „Dokončeno“, jsou udržovány jako aktivní a lze je snáze vyhledat uživatelem v pracovním seznamu| +|Část 9
**Komentáře**|- **Komentáře**
Nepovinné komentáře a poznámky. Tyto komentáře se v analytice nezobrazí a lze k nim přistupovat pouze prostřednictvím aplikace Capture, která slouží k zadávání údajů uvedených v řádcích.| + +### Skupiny uživatelů { #user-groups } + +V balíčku metadat jsou zahrnuty následující skupiny uživatelů: + +1. Správce COVID19 - je určen pro správce systému, aby měli práva upravovat metadata +2. Zachycení dat COVID19 - je určeno pro zaměstnance zadávající data, aby měli přístup ke shromažďování dat +3. Přístup COVID19 - je určen pro uživatele, například analytiky, kteří by měli mít možnost prohlížet data, ale ne upravovat metadata. + +V současné době mají přístup ke sběru dat v programu pouze uživatelé zařazení do skupiny pro sběr dat COVID19. Další pokyny naleznete v pokynech k instalaci. + +### Pravidla programu { #program-rules } + +Pro program byla nakonfigurována následující pravidla programu: + +|Název pravidla programu|Popis pravidla programu| +|--|--| +|Přiřaďte prázdnou hodnotu klasifikaci třídy|Automatizace: Přiřazení prázdné hodnoty klasifikaci třídy| +|Přiřadit datum události|Automatizace: Přiřadit datum události, pokud není k dispozici datum zahájení| +|Přiřadit „Laboratorně potvrzený případ“ ke klasifikaci případů|Automatizace: Přiřaďte „Laboratorně potvrzený případ“ ke klasifikaci případů| +|Přiřadit datum zahájení|Automatizace: Přiřadit datum nástupu příznaků, pokud je k dispozici| +|Přiřadit „Pravděpodobný případ“ ke klasifikaci případů|Automatizace: Přiřadit „Pravděpodobný případ“ ke klasifikaci případů| +|Přiřadit „Podezřelý případ“ ke klasifikaci případů|Automatizace: Přiřadit Podezřelý případ ke klasifikaci případů| +|Skrýt pole klasifikace případů|Skrýt pole klasifikace případů, dokud nebude zodpovězena otázka laboratorního testu| +|Skrýt pole JIP|Skrýt pole JIP, pokud nebude hospitalizován| +|Skrýt 'Importovaný případ'|Pokud necestoval, skrýt „dovezený případ“| +|Skrýt datum nástupu příznaků|Skrýt datum počátku příznaků, pokud se neobjeví žádné příznaky| +|Skrýt možnosti výsledku|Skrýt irelevantní možnosti výsledku| +|Skrýt 'Specifikujte místní zdroj infekce'|Skrýt možnost „Specifikovat místní zdroj infekce“ pokud není vybrán místní přenos.| +|Skrýt pole výsledku testu|Skrýt pole s výsledky testu, dokud na otázku laboratorního testu neodpovíte ano| +|Skrýt možnosti výsledku testu|Skrýt irelevantní možnosti výsledku testu| +|Skrýt neznámé možnosti|Skrýt irelevantní neznámé možnosti| + +Více o pravidlech programu si můžete přečíst zde: + +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +Z údajů zachycených v programu s řádkovým výpisem COVID-19 můžeme vypočítat následující indikátory, včetně indikátorů doporučených WHO pro denní a týdenní reportování, prezentovat je na ovládacím panelu. Všechny indikátory programu COVID-19 založené na programu událostí jsou přiřazeny skupině indikátorů programu „Události COVID-19“. + +||| +|--|--| +|COVID-19 - Případy přijaté na jednotce intenzivní péče (JIP)|COVID-19 Případy přijaté na jednotce intenzivní péče (JIP)| +|COVID-19 - Případy nakažení prostřednictvím zdravotnického zařízení|Případy, kdy existuje podezření na infekci v prostředí zdravotní péče| +|COVID-19 - Případy infikované komunitním přenosem|Případy, kdy existuje podezření na infekci šířením komunity| +|COVID-19 - Případy infikované přenosem z domácnosti|Případy, kdy existuje podezření na infekci v domácnosti| +|COVID-19 - Případy infikované místním přenosem|Případy, kdy je podezření, že k infekci došlo lokálně, nikoli v jiné zemi| +|COVID-19 - Případy infikované jiným kontaktem s jiným infikovaným jednotlivcem|Případy, kdy existuje podezření na infekci jiným blízkým kontaktem s infikovanou osobou (kromě těch, které jsou uvedeny v seznamu: domácnost, známý klastr, HCF)| +|COVID-19 - Případy spojené se známým klastrem|Případy, u nichž existuje podezření na infekci spojením se známým klastrem případů| +|COVID-19 - Případy s neznámým nakažením|Případy, kdy není znám zdroj infekce nebo nakažení| +|COVID-19 - Úmrtí|Úmrtí související s COVID-19 (úmrtí zaznamenaná u všech podezřelých případů)| +|COVID-19 - potvrzené hospitalizované případy|Počet potvrzených případů, které byly přijaty do nemocnice| +|COVID-19 - importované případy|Případy, kdy je pravděpodobný zdroj infekce zaznamenán jako jiná země nebo dovezený z jiné země.| +|COVID-19 - Laboratorně potvrzené případy|Podezřelé případy, které byly potvrzeny laboratorním testováním (lze provést více laboratorních testů; tento indikátor předpokládá, že výsledek posledního testu je „pozitivní“); zobrazeno podle data zprávy| +|COVID-19 - Laboratorně potvrzené případy - podle nástupu příznaků|Podezřelé případy, které byly potvrzeny laboratorním testováním (lze provést více laboratorních testů; tento indikátor předpokládá, že výsledek posledního testu je „pozitivní“); zobrazeno podle data nástupu příznaků| +|COVID-19 - Laboratorně testované případy|Počet podezřelých případů, které byly podrobeny laboratornímu testu (včetně neprůkazných výsledků laboratorních testů)| +|COVID-19 - Pravděpodobné případy|Podezřelé případy s neprůkaznými laboratorními výsledky nebo netestované z jakéhokoli důvodu k datu nahlášení| +|COVID-19 - Pravděpodobné případy - podle nástupu příznaků|Podezřelé případy s neprůkaznými laboratorními výsledky nebo netestované z jakéhokoli důvodu podle data nástupu příznaků| +|COVID-19 – obnovené případy|Počet uzdravených případů (podle data nástupu příznaků)| +|COVID-19 - Podezřelé případy|Celkový počet případů s podezřením na COVID-19 podle data nahlášení| +|COVID-19 - Podezření na případy - podle nástupu příznaků|Celkový počet případů s podezřením na COVID-19 podle data nástupu příznaků| +|COVID-19 – Podezřelé případy nebyly testovány|Celkový počet podezřelých případů bez laboratorního výsledku| +|Událost COVID-19 – úmrtnost případů|Úmrtí související s COVID-19 (úmrtí zaznamenaná u všech podezřelých případů)| +|COVID-19 Úmrtí podle pohlaví a věkových skupin|Muž, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Žena, 0-4, 5-14 , 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Potvrzené případy podle pohlaví a věkové skupiny|Muž, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Žena, 0-4, 5-14 , 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Podezřelé případy podle pohlaví a věkové skupiny|Muž, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Žena, 0-4, 5-14 , 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| + +## Reference { #references } + +* [Sada nástrojů pro sledování, odezvu a očkování COVID-19](https://dhis2.org/covid-19) +* WHO Technické pokyny pro dohled nad COVID-19 a definice případů (poslední aktualizace 20. března 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* Datový slovník WHO pro formulář hlášení případů COVID-19 +[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* Laboratorní testování WHO na nový koronavirus z roku 2019 (2019-nCoV) v případech podezření u člověka (poslední aktualizace 2. března 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* Úvahy WHO při vyšetřování případů a klastrů COVID-19 (naposledy aktualizováno 13. března 2020)[https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* Zprávy o situaci koronaviru WHO +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md new file mode 100644 index 00000000..de1db1da --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md @@ -0,0 +1,13 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implementace +--- + +# COVID-19 Surveillance Events { #covid-19-surveillance-events } + +## Design { #design } + +[Version 0.3.2](#c19-evt-design) + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md new file mode 100644 index 00000000..d6106a6b --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md @@ -0,0 +1,22 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_surveillance-digital_data_package-2022.md" +revision_date: '2023-09-01' +tags: +- Implementace +--- + +# COVID-19 Surveillance { #covid-19-surveillance } + +DHIS2 released a digital metadata package to accelerate case detection, situation reporting, active surveillance and response for COVID-19. The design is inspired by the Ministry of Health Sri Lanka’s pioneering use of DHIS2 tracker for COVID-19 case detection and draws on years of collaboration with the World Health Organisation (WHO) to develop information system standards for case-based disease surveillance. The COVID-19 digital data package includes standard metadata aligned with the WHO’s [technical guidance on COVID-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and implementation guidance to enable rapid deployment in countries. + +The design of these modules can be adapted, modified and reused for new and emerging infectious disease threats to strengthen health emergency preparedness and response systems in countries. + +## COVID-19 Surveillance Modules { #covid-19-surveillance-modules } + +DHIS2 supports surveillance workflows and automated analysis for key components of routine and active surveillance: + +* **COVID-19 Case Surveillance tracker**: enrolls & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. +* **Contact Registration & Follow-up tracker**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. +* **Ports of Entry Screening & Follow-up tracker**: enrols travellers who have visited high-risk locations at Ports of Entry for 14-day monitoring and follow-up. +* **COVID-19 Aggregate Situation Reports**: an aggregate reporting dataset that captures minimum necessary data points for daily or weekly reporting and includes key information for generating situation reports. + diff --git a/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..26b54588 --- /dev/null +++ b/projects/docs-full-site/cs/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implementace +--- + +# Poznámka k vydání { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Přehled { #overview } + +Provedli jsme několik aktualizací stávajícího balíčku, abychom se přizpůsobili novým pokynům COVID-19 [pokyny ke sledování vydané WHO 20. března 2020](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) a zavedly nové komponenty do celkového balíčku podpory. Přečtěte si prosím poznámky zde a kontaktujte nás na diskusním fóru COVID-19 v [community of practice](https://community.dhis2.org/c/implementation/covid-19/) s případnými dotazy. + +**Všechny balíčky metadat a dokumentaci lze stáhnout z [dhis2.org.covid-19](https://www.dhis2.org/covid-19).** + +Balíčky jsou v současné době přeloženy do francouzštiny, španělštiny, portugalštiny a ruštiny a připravují se další jazyky (arabština, laosština, barmština). Můžeme podporovat překlady balíčků metadat na naší globální překladatelské platformě a pozvat komunitu, aby přispěla, pokud má vaše země zájem o překlad balíčku do nového jazyka. [Podívejte se na oznámení naší komunity praxe] (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). Kontaktujte nás prosím na translate@dhis2.org. + +Nové vydání obsahuje: + +1. Program trasování případů COVID-19 +2. COVID-19 Contact Registration & Follow-Up program +3. Souhrnné přehledové hlášení COVID-19 +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Kódy metadat byly aktualizovány tak, aby odpovídaly [Datovému slovníku případových zpráv WHO](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Programové ukazatele byly aktualizovány tak, aby odrážely nové definice případů WHO pro pravděpodobné případy (viz aktualizované definice případů v prozatímních pokynech pro dohled aktualizovaných 20. března 2020 [Prozatímní pokyny pro dohled WHO aktualizovány 20. března 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Věkové legendy byly aktualizovány, aby splňovaly nové pokyny WHO pro týdenní podávání zpráv +4. relationshipType přidán do balíčku metadat +5. Drobné opravy metadat umožňující snazší instalaci balíčku (tj. UID indikátorType odpovídá typu indikátoru obsaženému v agregovaném balíčku) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. Byla přidána nová programová fáze, která umožňuje opakovatelné „sledování“ kontaktu s případem. Toto bylo přidáno, aby odráželo pracovní postupy implementované v Ugandě a Togu, kde lze kontakty opakovaně monitorovat v průběhu 14 dnů, aby se zjistilo, zda existují příznaky. ***program*** je založen na pokynech WHO, které lze nalézt [zde](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), jakož i informace získané prostřednictvím webu [OpenWHO] (https://openwho.org/courses/introduction-to-ncov). +2. Věkové legendy byly aktualizovány, aby splňovaly nové pokyny WHO pro týdenní podávání zpráv +3. relationshipType přidán do balíčku metadat +4. Drobné opravy metadat umožňující snazší instalaci balíčku + +### Souhrnné přehledové zprávy COVID-19 { #covid-19-aggregate-surveillance-reporting } + +Následující aktualizace byly provedeny, aby odrážely nové pokyny v [Pokyny WHO aktualizovány 20. března 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), včetně aktualizovaných globálních souhrnných zpráv pro WHO (týdně a denně) + +1. Věkové kategorie aktualizovány podle nových věkových skupin +2. Byly přidány nové indikátory podílu mužů mezi potvrzenými případy a podílu mužů mezi potvrzenými úmrtími +3. Nový týdenní datový soubor pro zachycení klasifikace přenosu na nižší než národní úrovni (tj. Na krajské úrovni - lze jej podle potřeby přiřadit k jakékoli nižší než národní úrovni v zemi) podle aktualizovaných pokynů WHO pro týdenní podávání zpráv +4. Drobné opravy metadat umožňující snazší instalaci balíčku + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +Případ použití trasovače programu Místa Vstupu byl navržen tak, aby podporoval registraci cestujících vstupujících do země s historií cestování do země / oblasti / teritoria hlásící místní přenos COVID-19, u nichž může být nutné sledovat aby nedošlo k rozvoji příznaků. Je založen na koncepci implementované HISP Srí Lanka na podporu Ministerstva zdravotnictví Srí Lanky s malými změnami, aby byl program obecnější pro globální použití a aby byl v souladu s ostatními sledovacími programy v balíčku COVID-19. Balíček podporuje intervence ve vstupních místech podrobně popsaných ve WHO [technické pokyny pro správu nemocných osob ve vstupních místech](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/points-of-entry-and-mass-gatherings). + +Přečtěte si více o programu POE v [dokumentu návrhu systému] (https://docs.dhis2.org/en/topics/metadata/covid-19-surveillance/covid-19-poe-tracker-design.html). + diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md index 77f15904..53d264fb 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.3/ReleaseNote-2.3.0.md" revision_date: '2020-11-03' tags: -- DHIS core version 2.35 - Android app version 2.3.0 - Implementace +- DHIS core version 2.35 --- # Poznámka k vydání aplikace DHIS2 pro Android verze 2.3 { #dhis2-android-app-version-23-release-note } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md index 37960aae..e1602d13 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.4/ReleaseNote-2.4.0.md" revision_date: '2021-04-27' tags: -- Android app version 2.4.0 -- DHIS core version 2.36 - Implementace +- DHIS core version 2.36 +- Android app version 2.4.0 --- # DHIS2 Android App version 2.4 Release Notes { #dhis2-android-app-version-24-release-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md index deff91f4..6689cc14 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.5/ReleaseNote-2.5.0.md" revision_date: '2021-11-24' tags: -- Android app version 2.5.0 - DHIS core verze 2.37 - Implementace +- Android app version 2.5.0 --- # DHIS2 Android App version 2.5 Release Notes { #dhis2-android-app-version-25-release-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md index 9b5ab676..e6690dbf 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.6/ReleaseNote-2.6.0.md" revision_date: '2022-04-18' tags: +- Implementace - DHIS core version 2.38 - Android app version 2.6.0 -- Implementace --- # DHIS2 Android App version 2.6 Release Notes { #dhis2-android-app-version-26-release-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md index e1e8a97d..8798dc07 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.7/ReleaseNote-2.7.0.md" revision_date: '2023-05-11' tags: -- DHIS základní verze 2.39 - Android app version 2.7.0 - Implementace +- DHIS základní verze 2.39 --- # DHIS2 Android App version 2.7 Release Notes { #dhis2-android-app-version-27-release-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md index 03f422ec..3d2ab5c8 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.8/ReleaseNote-2.8.0.md" revision_date: '2023-05-08' tags: -- DHIS základní verze 2.40 - Android app version 2.8.0 - Implementace +- DHIS základní verze 2.40 --- # DHIS2 Android App version 2.8 Release Notes { #dhis2-android-app-version-28-release-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md index b401b76f..440b5b3b 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/2.9/android-releases/2.9/ReleaseNote-2.9.0.md" revision_date: '2023-11-20' tags: -- DHIS základní verze 2.40 -- Android app version 2.9.0 - Implementace +- Android app version 2.9.0 +- DHIS základní verze 2.40 --- # DHIS2 Android App version 2.9 Release Notes { #dhis2-android-app-version-29-release-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md index e91a4c24..5aa101b2 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/ReleaseNote-2.35.0.md" revision_date: '2020-10-22' tags: -- DHIS core version 2.35 - Implementace +- DHIS core version 2.35 --- # Poznámka k verzi DHIS verze 2.35 { #dhis-version-235-release-note } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md index 5b4f6534..36a34e64 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.35 - Implementace +- DHIS core version 2.35 --- # 2.35 Poznámky k upgradu { #235-upgrade-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md index 50544028..5ff49100 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/ReleaseNote-2.36.md" revision_date: '2021-10-27' tags: -- DHIS core version 2.36 - Implementace +- DHIS core version 2.36 --- # DHIS version 2.36 Release Note { #dhis-version-236-release-note } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md index 3bd8796a..11c794d5 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.36 - Implementace +- DHIS core version 2.36 --- # 2.36 Upgrade Notes { #236-upgrade-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md index 1f2db296..2837f5fc 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/ReleaseNote-2.38.md" revision_date: '2022-10-12' tags: -- DHIS core version 2.38 - Implementace +- DHIS core version 2.38 --- # DHIS version 2.38 Release Note { #dhis-version-238-release-note } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md index 5b0e216c..cd5973ab 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.38 - Implementace +- DHIS core version 2.38 --- # 2.38 Upgrade Notes { #238-upgrade-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md index ab3380b5..6d852846 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/ReleaseNote-2.39.md" revision_date: '2023-01-26' tags: -- DHIS základní verze 2.39 - Implementace +- DHIS základní verze 2.39 --- # DHIS version 2.39 Release Note { #dhis-version-239-release-note } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md index 6cced6c7..898c95d0 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/README.md" revision_date: '2023-08-30' tags: -- DHIS základní verze 2.39 - Implementace +- DHIS základní verze 2.39 --- # 2.39 Upgrade Notes { #239-upgrade-notes } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md index c4dea8d0..c8bb8390 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/ReleaseNote-2.40.md" revision_date: '2023-05-12' tags: -- DHIS základní verze 2.40 - Implementace +- DHIS základní verze 2.40 --- # DHIS2 version 40 Release Note { #dhis2-version-40-release-note } diff --git a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md index 82922c46..f12c544b 100644 --- a/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md +++ b/projects/docs-full-site/cs/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/README.md" revision_date: '2023-08-30' tags: -- DHIS základní verze 2.40 - Implementace +- DHIS základní verze 2.40 --- # 2.40 Upgrade Notes { #240-upgrade-notes } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md index 2519230f..52b53a6c 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.39 +- Správa --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md index e04896b6..d4d7841b 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.39 +- Správa --- # Instalace { #installation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md index ce86aec0..6ba4e4c6 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.39 +- Správa --- # Aktualizace { #upgrading-dhis2 } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md index 84757b41..a86c66ca 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.39 +- Správa --- # Používání komunikačních bran pro hlášení SMS { #sms_report_sending } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md index ef10424d..bd2a0c05 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.40 +- Správa --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md index 554f1ccb..f98e4536 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.40 +- Správa --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md index a732fdfb..418ea2c7 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.40 +- Správa --- # Instalace { #installation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md index 90ae79bd..c7cc5129 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__monitoring-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.40 +- Správa --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md index a6cecec2..b8fe3775 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.40 +- Správa --- # Aktualizace { #upgrading-dhis2 } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md index 32298ca0..35387a9b 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS základní verze 2.40 +- Správa --- # Používání komunikačních bran pro hlášení SMS { #sms_report_sending } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md index 3b773afe..18967d70 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS core version 2.41 +- Správa --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md index c6a7a4c0..a21337bd 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS core version 2.41 +- Správa --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md index 5ceb4cc1..6e21188d 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS core version 2.41 +- Správa --- # Instalace { #installation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md index c83a86da..2972ab94 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__monitoring-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS core version 2.41 +- Správa --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md index 2429683c..264abce1 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS core version 2.41 +- Správa --- # Aktualizace { #upgrading-dhis2 } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md index 16519a1d..4e040c7e 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/cs/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: -- Správa - DHIS core version 2.41 +- Správa --- # Používání komunikačních bran pro hlášení SMS { #sms_report_sending } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index 652e97e1..7325e216 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/cs/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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # Audit { #audit } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index c267c5bd..782119f9 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/cs/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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index 8c9078b6..d3fc41c8 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/cs/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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # Instalace { #installation } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index ea00e1e2..0ac3bbab 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/cs/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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index e989ab67..baffc051 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/cs/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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # Aktualizace { #upgrading-dhis2 } diff --git a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index f1fb7631..6eeba277 100644 --- a/projects/docs-full-site/cs/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/cs/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: -- Správa - Hlavní verze jádra DHIS +- Správa --- # Používání komunikačních bran pro hlášení SMS { #sms_report_sending } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index c06e227c..d3a17e0d 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/cs/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: -- App version 1.0 - Použití +- App version 1.0 --- ## Procházení Trasovače Akcí { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index 7c76835d..ec348de4 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/cs/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: -- App version 1.0 - Použití +- App version 1.0 --- # Propojený ovládací panel Trasovač Akcí a Demo server { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index 56417bc2..b88fae51 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/cs/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: -- App version 1.0 - Použití +- App version 1.0 --- # Údržba aplikace Trasovač Akcí { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index 10b41073..b25bb75d 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/cs/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: -- App version 1.0 - Použití +- App version 1.0 --- # Plánování akcí v Trasovači Akcí { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index 982fab17..1af944d9 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/cs/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: -- App version 1.0 - Použití +- App version 1.0 --- # Trasování akcí v Trasovači Akcí { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index 1ff9c533..605b181a 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Instalace aplikace BNA { #installing-the-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index ae19a7ad..12ed893e 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Údržba aplikace BNA { #bna-app-maintenance } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index bf72f851..6fd72fe6 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Analýza a interpretace BNA { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index 97d5104c..b6f2b174 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Architektura aplikace BNA { #bna-app-architecture } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index cabd0cd8..1058c567 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Ovládací panel analýzy úzkých míst BNA a Demo server { #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index a818c7e6..dd23cef7 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Konfigurace intervencí aplikace BNA { #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index 8c91568b..cb74cf7e 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Vizualizační operace { #visualization-operations } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index 74550cef..282b9097 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Přijetí používání aplikace BNA { #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index 614f43d5..3d247353 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Budování kapacit { #capacity-building } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index fed1cdd8..a689d5df 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Školení koncových uživatelů { #end-user-training } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index 64c2e0c7..c3ebe62c 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Průvodce implementací aplikace BNA { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index 99dd056d..06f547d4 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Koncepty integrace pro aplikaci BNA. { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index 2a60e5a8..89e39af4 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Příležitosti a výzvy { #opportunities-and-challenges } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index d73244e0..074db1aa 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Plánování a organizace { #planning-and-organising } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index 7023e8fa..cf89cdfc 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Nastavení nové aplikace BNA { #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index 13bc0bd1..5f0b3a60 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/cs/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: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Podpora a rozšiřování aplikací BNA { #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index ff9ca569..39a917d8 100644 --- a/projects/docs-full-site/cs/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/cs/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: '2021-09-09' tags: -- App version 1.2.2 - Použití +- App version 1.2.2 --- # Škálování a udržitelnost { #scale-up-and-sustainability } diff --git a/projects/docs-full-site/es_419/.cache_timestamp b/projects/docs-full-site/es_419/.cache_timestamp index 92651298..7246eff6 100644 --- a/projects/docs-full-site/es_419/.cache_timestamp +++ b/projects/docs-full-site/es_419/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:21:11Z \ No newline at end of file +2024-10-19T21:20:44Z \ No newline at end of file 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 4310e607..d57fccd4 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 3d886e5d..3dafbcb5 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 76ac28ad..18d08b84 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 29dbe962..d964c4e4 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 ef03de66..cc346281 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 bf4c81f3..662df0bc 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 84974de1..b1c85096 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 374ac720..fc5ef350 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 e111f3e9..3275ea2d 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 c3d21672..084c65c1 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 bb3c62aa..c62344e6 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 24f3b654..7f67922c 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 e5b6b7da..8dbd0cdc 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # Metadata Gist API { #gist_api } 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 4c0477ff..4870fea4 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # Metadata { #metadata } 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 ddd26911..e63158db 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # New Tracker { #new-tracker } 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 f1efaddf..76d191c3 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 013a7a61..b6e859a9 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 3eb152de..43201b33 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 43ae94e4..8c6d9cbd 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,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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # Compartir { #sharing } 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 c78abddc..694cf495 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 c1ce8070..e00235c3 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 818fb7d9..22486712 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 1c53ad18..88458057 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # 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 c6e10407..a79a48f5 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: -- DHIS core version 2.38 - Desarrollar +- DHIS core version 2.38 --- # Visualizations { #visualizations } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md index 0e91550d..ab346282 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Analytics { #analytics } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md index 00492099..d0882990 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md index f72e6a26..0493427f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Data approval { #data-approval } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md index 4be6b397..c677285f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Data { #data } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md index 471653a8..9c52d759 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-validation.md" revision_date: '2022-06-21' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md index 3ca3275b..9dc10679 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # I18n { #i18n } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md index 1ec45d4f..a8617ab2 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/overview.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Overview { #webapi } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md index 5284c82e..d261d27c 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Messaging { #messaging } 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 c91d1f4d..13ac58e8 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Metadata Gist API { #gist_api } 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 28370848..0d1c3a53 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata.md" revision_date: '2023-08-03' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Metadata { #metadata } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md index 7e02b111..7f17c455 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/scheduling.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Scheduling { #webapi_scheduling } 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 ba5ede08..370b8ec1 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Compartir { #sharing } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md index b2858ab0..e1b371ee 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # SMS { #sms } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md index 13aabc8c..cd3df35f 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Sincronización { #webapi_synchronization } 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 d92f2fc9..b652dd40 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.39 - Desarrollar +- DHIS core version 2.39 --- # Visualizations { #visualizations } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md index 9bcbed6c..1b5eece1 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md +++ b/projects/docs-full-site/es_419/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 - Desarrollar +- DHIS core version 2.40 --- # Analytics { #analytics } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md index dc36c0db..b5a700cb 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md +++ b/projects/docs-full-site/es_419/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 - Desarrollar +- DHIS core version 2.40 --- # Apps { #apps } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md index f701d775..ebe01a01 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Audit { #audit } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md index daf0de3e..48989c49 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Data approval { #data-approval } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md index be9342c1..7ab79d32 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Data entry { #data-entry } 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 e99d8fc8..d7124dad 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md index ccedede1..ab89916b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Data { #data } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md index 917b08ac..773fd403 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md +++ b/projects/docs-full-site/es_419/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 - Desarrollar +- DHIS core version 2.40 --- # Data store { #data-store } 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 786e6afa..5559371e 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 eca0d88e..094d300e 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__event-hooks-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index fac60843..04162658 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md index 575097ed..c91d3a79 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # I18n { #i18n } 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 bff16f06..ade1de92 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 7bcb3bc6..7aeabcbc 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__messaging-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md index b99f7c2f..32141b01 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Messaging { #messaging } 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 1891a330..e7987ac7 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Metadata Gist API { #gist_api } 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 5b4d1220..75efd292 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Metadata { #metadata } 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 5359d0ca..68ec4b68 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__route-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 55850739..76db044d 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/es_419/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 - Desarrollar +- DHIS core version 2.40 --- # Route { #route } 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 843b7d05..72a81b38 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 7df39498..8b6b1da1 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 982e86a3..117ec4ae 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,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 - Desarrollar +- DHIS core version 2.40 --- # Compartir { #sharing } 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 bf697b1c..147cb3f7 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__synchronization-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md index 373961c4..fd1b4ce7 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Sincronización { #webapi_synchronization } 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 35fe416b..85aaedf3 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 } 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 237fcb25..c7dfcd47 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS core version 2.40 - Desarrollar +- DHIS core version 2.40 --- # Tracker { #tracker } 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 50483410..0dee5b43 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 13157dba..5cc61893 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 } 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 d4ef6087..a30ef29c 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/analytics.md" revision_date: '2024-05-02' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Analytics { #analytics } 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 9e1b26a2..22526536 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: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # 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 1894c6f6..d7721dc6 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: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # 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 f578c121..f5e38b08 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: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # 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 2b63128b..f35cda7e 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: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # 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 49e2daf9..f640b849 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-exchange.md" revision_date: '2024-06-26' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md index 0bf90a1d..7473e1fd 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Data { #data } 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 bdcfcb8b..513ea946 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Data store { #data-store } 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 72c951ff..007dc32a 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Data validation { #data-validation } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md index 9d639d67..87e490fe 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Email { #email } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md index c5382dfc..a04f7c16 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md index a2990d8e..4a480fb2 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # I18n { #i18n } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md index 786550be..cf051237 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Overview { #webapi } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md index 7900fa57..f9353e54 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md index 1154f1c9..a69b09c9 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Messaging { #messaging } 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 8f6a3f8e..fb5fb1a0 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Metadata Gist API { #gist_api } 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 35adfcea..4c2ff76e 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Metadata { #metadata } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md index 2a0368da..7a016780 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Perfil de la unidad organizativa { #org_unit_profile } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md index ea7f49c1..734982e5 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md index d79681df..3c33772b 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/route.md" revision_date: '2024-09-24' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Route { #route } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md index 87fbe2a2..34e89256 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Scheduling { #webapi_scheduling } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md index dbe1faad..6adba73a 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Settings and configuration { #settings-and-configuration } 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 cdeb89c5..c3944df7 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Compartir { #sharing } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md index ad050a89..a895adf5 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # SMS { #sms } diff --git a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md index 8ecacba3..aecf4671 100644 --- a/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md +++ b/projects/docs-full-site/es_419/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Sincronización { #webapi_synchronization } 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 21bb016b..49f5ae81 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: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } 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 23cc8a4d..7632155f 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Tracker { #tracker } 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 25239419..762751e3 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 7bbc9016..e58023c1 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- DHIS core version 2.41 - Desarrollar +- DHIS core version 2.41 --- # Visualizations { #visualizations } 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 f6f5ff56..4cd08809 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-07-26' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Analytics { #analytics } 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 0556d26d..872b017f 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 ff004af4..b1de9117 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 1c3454a4..cb1401db 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 418983e5..2c480e5c 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 fb627b2a..15540805 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-09-18' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data exchange { #data-exchange } 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 a38b7c03..9aa9998f 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 ffb8be40..fc976653 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data store { #data-store } 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 b280d021..b820738f 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # Data validation { #data-validation } 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 dc6f6fd7..1c11721f 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 b96a0725..b152b51c 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 004a2e86..8829f31c 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 d0d2b81a..89e82a32 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 ee7634fb..1ddb3c50 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 601f7fba..ecb25ce4 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 c4d99bed..d0ba553d 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # Metadata Gist API { #gist_api } 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 e9e1c57a..2210e0de 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-07-29' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # Metadata { #webapi_metadata } 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 b932d389..e4c1c3fd 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 634a4dc8..5c245384 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 28d95434..3620a9a0 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 55ca6217..72c58b5b 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 c0f751b3..d02b006b 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,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: -- Desarrollar - DHIS core version master +- Desarrollar --- # Compartir { #sharing } 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 52744567..ce988a04 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 10e60e9a..b2fe303b 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # Sincronización { #webapi_synchronization } 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 eeae1bee..909f0b8a 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-09-13' tags: -- Desarrollar - DHIS core version master +- Desarrollar --- # 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 8097b68c..93705e4e 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: -- Desarrollar - DHIS core version master +- Desarrollar --- # Visualizations { #visualizations } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__DATA-USE__data-visualization-md b/projects/docs-full-site/es_419/IMPLEMENT__DATA-USE__data-visualization-md index a3d51a2b..e1c29f5a 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__DATA-USE__data-visualization-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__DATA-USE__data-visualization-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/data-use/data-visualization.md" -revision_date: '2024-10-17' +revision_date: '2024-10-18' tags: - Implementar --- @@ -27,9 +27,9 @@ Understanding these categories is essential to selecting the correct chart type - **Ordinal** - Categories with a meaningful order (e.g., disease status). These categories have a logical sequence. - For example, disease severity might be classified as mild, moderate, and severe, which has an inherent order. -> **Note**: +> **Note** > ->**Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. +> **Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. ![Variable categories](resources/images/dataviz_001.png) @@ -46,7 +46,7 @@ What’s the best way to choose the right visualization for the data at hand? [F Another Chart Chooser is mapped in the [Extreme Presentation Method](https://extremepresentation.com/). -![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.png) +![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.jpg) The summary below is based on the visualizations available in the core DHIS2 Data Visualizer App. @@ -93,9 +93,9 @@ The summary below is based on the visualizations available in the core DHIS2 Dat ### Specific Visualization Styles { #specific-visualization-styles } ->**Note** +> **Note** > ->**Data speaks louder than words!** +> **Data speaks louder than words!** In data visualization, choosing the right type of chart or graph is crucial for effectively communicating your data. Each visualization style has its strengths and is best suited for specific types of data and analytical purposes. This chapter explores a variety of visualization styles, detailing their applications and best practices. Whether you're looking to show trends over time, compare quantities, highlight correlations, or illustrate parts of a whole, selecting the appropriate visualization method will enhance clarity and insight. By understanding the nuances of each style, you can ensure that your data tells a compelling and accurate story. @@ -103,9 +103,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Correlation { #correlation } ->**Note** +> **Caution** > ->Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. +> Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. - **Scatterplot**: Shows the relationship between two continuous variables, each having its axis. Each point represents an observation's values on the two variables. It's useful for identifying trends, clusters, and outliers. For example, a scatterplot can display the relationship between the number of immunization campaigns conducted in various districts and the resulting immunization coverage rate. @@ -118,9 +118,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Ranking { #ranking } ->**Note** +> **Note** > ->Emphasizes the item's position in an ordered list rather than the absolute value. +> Emphasizes the item's position in an ordered list rather than the absolute value. - **Ordered bars/columns**: Shows ranks of values more easily when sorted. This visualization helps to quickly see the highest and lowest values. An ordered bar column chart can be used to display the number of TB cases in each district, sorted in descending order to highlight the districts with the highest burden. @@ -132,9 +132,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Change Over Time { #change-over-time } ->**Note** +> **Note** > ->Keep gaps between columns small to highlight data shape. +> Keep gaps between columns small to highlight data shape. Use markers for irregular data points. - **Column**: Emphasizes changing trends. Columns are used to show discrete data points over time. For example, monthly case figures can be shown as a column chart. @@ -152,9 +152,9 @@ Use markers for irregular data points. #### Magnitude { #magnitude } ->**Note** +> **Note** > ->Small gaps highlight data shape. Best for a single series of data. +> Small gaps highlight data shape. Best for a single series of data. - **Column/Paired column/bar**: Compare sizes, usually numbers rather than rates or percentages. For instance, HIV case figures for different regions can be compared using a bar chart. In this case, it is appropriate to keep the distance between the columns as they represent separate entities rather than variables through time. @@ -168,9 +168,9 @@ Use markers for irregular data points. #### Part-to-Whole { #part-to-whole } ->**Note** +> **Tip** > ->Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** +> Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** ![Imrpove the visualization choosing the most suitable colour set](resources/images/dataviz_022.png) @@ -206,9 +206,9 @@ Stacked columns or bar charts **should be avoided when** a detailed comparison o - **Choropleth**: Standard for rates on maps. Uses varying shades of a colour to represent data values for different regions. For example, population density by region can be shown using a choropleth map. ->**Note** +> **Note** > ->**Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. +> **Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. ![Map showing the percentage of PTB-BC cases in a region](resources/images/dataviz_013.png) @@ -287,9 +287,9 @@ A visualization should always have: ![Contextualized graph](resources/images/dataviz_024.png) ->**Note**: +> **Caution** > ->Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. +> Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. #### Pie Chart { #pie-chart } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md new file mode 100644 index 00000000..783c93ef --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -0,0 +1,206 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-design.md" +revision_date: '2023-03-31' +tags: +- Implementar +--- + +# COVID-19 Surveillance - Aggregate System Design Guide { #c19-agg-design } + +## Purpose { #purpose } + +The COVID-19 Surveillance Aggregate System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Antecedentes { #background } + +This aggregate design has been updated to reflect new aggregate reporting requirements from the [Global surveillance of COVID-19: WHO process for reporting aggregated data](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form), last updated on August 7, 2020. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| **Type of Surveillance Package** | **Case-based Surveillance (Tracker)** | **Case surveillance line-listing (Event)** | **Case surveillance (Aggregate)** | +| --- | --- | --- | --- | +| **Descripción** | Enrolls a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables weekly reporting of key aggregate data points | +| **Pros** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| **Cons** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation)| + +**This document covers only the design of the aggregate package**; separate system design documents are available for DHIS2 Tracker and Line-listing (event-based) packages. As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The aggregate package is designed to meet the most critical reporting requirements and analytical capacities for surveillance and response. + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated August 7, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +The aggregate COVID-19 surveillance package includes + +1. Weekly aggregate data set and data elements for key COVID-19 surveillance reporting +2. Categories for data disaggregation +3. Core indicators +4. Dashboard and its items + +The dataset captures a minimum number of data points that meet the current WHO weekly reporting requirements; and generate a core set of indicators and dashboards for national and sub-national decision-makers to rapidly analyze and respond to disease trends. + +| **Nombre** | **Periodicity** | **Purpose** | +| --- | --- | --- | +| Aggregate Weekly Surveillance | Weekly| Reporting of key COVID-19 surveillance data including cases, tests and deaths. | + +It is recommended that the weekly dataset is assigned to Organisation Units at the lowest level of the health system feasible for reporting data, such as health facilities. + +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 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. +- 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 + +## Datasets { #datasets } + +This dataset is intended to capture weekly data needed for rapid response to disease transmission. If the burden of reporting becomes too great or when it is no longer considered an emergency situation in the country, the data set may be changed to monthly according to MOH policies. + +### Daily Surveillance Data Elements { #daily-surveillance-data-elements } + +The following lists the data elements and disaggregation (category combinations) included in the data set: + +| **Elementos de datos** | **Category Combinations** | +| --- | --- | +| New Confirmed Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Confirmed Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Hospitalized Cases | Ninguno | +| New Discharged Cases | Ninguno | +| New Cases Among Health Workers (Confirmed + Probable) | Ninguno | +| New Deaths Among Health Workers (Confirmed + Probable) | Ninguno | +| Number of Persons Tested for COVID-19 | Ninguno | +| Number of persons Tested with PCR Assay | Ninguno | +| Transmission Classification | Ninguno | + +### Weekly Surveillance Data Entry Form { #weekly-surveillance-data-entry-form } + +- **Section 1: New confirmed and probable Cases** + +Data should be entered for all new confirmed and probable cases reported during the reporting period. Confirmed cases refer to laboratory confirmed cases per WHO guidance; probable cases are defined by WHO as cases where laboratory test result is inconclusive; however countries may apply their own case definitions. The total column is automatically summed during data entry. +![Picture1](resources/images/AGG_Picture1.png) + +- **Section 2: New confirmed and probable deaths** + +Data should be entered for new confirmed and probable deaths reported during the reporting period. The total column is automatically summed during data entry. + +![Picture2](resources/images/AGG_Picture2.png) + +- **Section 3: Health worker infection and death** + +This section captures data for health workers' new confirmed and probable cases including deaths reported during the reporting period. + +![Picture3](resources/images/AGG_Picture3.png) + +- **Section 4: Hospitalisation and discharges** + +This section captures data for new hospitalisation and discharges during the reporting period. + +![Picture4](resources/images/AGG_Picture4.png) + +- **Section 5: Tests conducted** + +This section captures data for tests conducted with additional requirement to report tests conducted using PCR during the reporting period + +![Picture5](resources/images/AGG_Picture5.png) + +- **Section 6: Transmission Classification** + +This section summarizes the major form of transmission classification experienced by the reporting unit. + +![Picture7](resources/images/AGG_Picture6.png) + +### 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) + +## Data Validation { #data-validation } + +The following data validation rules have been configured. These validation rules do not run in the data entry form itself as it is anticipated that the urgent reporting of data where events occur in different time frames (e.g. one week can see only 3 new cases but 5 deaths). + +| **Nombre** | **Operator** | **Instruction** | **Left side description** | **Right side description** | +| --- | --- | --- | --- | --- | +| COVID19 - PCR tests \<= tested | less\_than\_or\_equal\_to | Tested with PCR should be less than or equal to total tests conducted | Tested with PCR | Tested conducted | +| COVID19 - New Cases hospitalised \<= All New Cases | less\_than\_or\_equal\_to | New Cases hospitalised should be less than or equal to all new cases | New Cases hospitalised | All New Cases | +| COVID19 - New confirmed deaths \<= New confirmed cases | less\_than\_or\_equal\_to | New confirmed deaths should be less than or equal to New confirmed cases | New confirmed deaths | New confirmed cases | +| COVID19 - Probable deaths \<= New probable cases | less\_than\_or\_equal\_to | Probable deaths should be less than or equal to New probable cases | Probable deaths | New probable cases | +| COVID19 - New deaths among HW (confirmed + probable) \<= All deaths reported | less\_than\_or\_equal\_to | New deaths among HW (confirmed + probable) should be less than or equal to All deaths reported | New deaths among HW (confirmed + probable) | All deaths reported | +| 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) | + +## Grupos de Usuarios { #user-groups } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Please refer to the [installation guidance](covid-19-aggregate-installation.html) for more information. + +## Indicators { #indicators } + +From the data captured, we can calculate at least the following indicators, many of which are recommended by the WHO for [weekly reporting](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) and present them in a dashboard. All COVID-19 program indicators are assigned to the Indicator Group 'COVID19'. + +| **name** | **description** | +| --- | --- | +| COVID19 - New Confirmed Deaths | Number of new confirmed deaths | +| COVID19 - New Cases Among HW (Confirmed + Probable) | Number of New Cases Among HW (Confirmed + Probable) | +| COVID19 - Proportion of HW amongst reported cases (%) | Proportion of HW amongst reported cases (%) | +| COVID19 - Active cases | Number of of active cases | +| COVID19 - Closed cases | Number of closed cases | +| COVID19 - New Confirmed cases | Number of new Confirmed cases | +| COVID19 - Recovery rate (%) | Recovery rate of confirmed cases | +| COVID19 - Case fatality rate among HW (%) | Case fatality rate among HW | +| COVID19 - New Hospitalized Cases | New Hospitalized Cases | +| COVID19 - Tested | Total number of tests conducted | +| COVID19 - Tested with PCR Assay | Tested with PCR assay | +| COVID19 - Positivity rate (%) | Positivity rate | +| COVID19 - New Probable Cases | Number of new probable cases | +| COVID19 - New Discharged Cases | Number of new discharged cases | +| COVID19 - New Deaths Among HW (Confirmed + Probable) | Number of new deaths among HW (Confirmed + Probable) | +| COVID19 - Proportion of PCR tests (%) | Proportion of PCR tests conducted | +| COVID19 - All cases (Confirmed + Probable) | Number of all cases (Confirmed + Probable) | +| COVID19 - New Probable Deaths | Number of new probable deaths | +| COVID19 - Case fatality rate (%) | Case fatality rate among confirmed cases | + +## Dashboards { #dashboards } + +Key analytic items have been configured and added onto the dashboard “COVID19 - Aggregate Weekly Surveillance”. These items include; pivot tables, charts and a map designed to provide data visualization for some of the data captured based on the indicators. In the process of adopting this package, users can modify or create additional items as suits their analytical needs and equally make the necessary adjustments to the dashboard. + +| **name**|**type**| +| --- | --- | +|COVID19 - Tested, tests with PCR and positivity rate by subnational level this year |Pivot table| +|COVID19 - HW amongst reported cases this year |Chart| +|COVID19 - Fatality rate amongst HW.|Chart| +|COVID19 - New confirmed cases and deaths in the last 12 weeks|Chart| +|COVID19 - Cumulative tests conducted, cases reported, hospitalised, discharged and deaths|Chart| +|COVID19 - Cumulative confirmed cases by subnational|Map| +|COVID19 - Deaths by age groups last weeks|Chart| +|COVID19 - Confirmed cases by sex in the last 14 weeks|Chart| +|COVID19 - Closed and active cases at subnational last months|Chart| +|COVID19 - Case recovery and fatality rates last 12 weeks|Chart| +|COVID19 - Active and Closed Cases last 12 weeks|Chart| + +## Referencias { #references } + +- Installation guidance: [https://www.dhis2.org/covid-19](covid-19-aggregate-installation.html) +- WHO Interim guidelines on nCoV-19 surveillance & case definitions (last updated March 20, 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions>]() +- WHO COVID-19 surveillance data dictionary (v6) +[https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98\_2](https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2) +- WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) + [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +- WHO Coronavirus situation reports + [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports>]() +- Global surveillance of COVID-19: WHO process for reporting aggregated data +[https://www.who.int/publications/i/item/aggregated-weekly-reporting-form](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md new file mode 100644 index 00000000..1d150c66 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-installation.md" +revision_date: '2022-11-07' +tags: +- Implementar +--- + +# Aggregate Package Installation Guide { #c19-agg-installation } + +## 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. + +The configuration packages for DHIS2 consists of a metadata file in [JSON](https://en.wikipedia.org/wiki/JSON) format which can be imported into a DHIS2 instance, as well as accompanying documentation. The package provides pre-defined, standard content according to WHO recommendations. This document is concerned with complete packages that include configurations of data collection (data sets, data elements, validation rules) as well as analysis and dashboards (chart, map and pivot table favourites). This is intended for use where there is no data collection configured in DHIS2, or if replacing/revising existing content to align with WHO recommendations. + +The configuration packages consists of 4 main components: + +* data sets with data elements; +* a set of indicators; +* analytical outputs (pivot table, data visualizer and GIS favourites); and +* a set of dashboards. + +These components are all linked, i.e. the indicators are based on the included data elements, the analytical outputs are based on the included indicators, and the dashboards are made up of the included analytical outputs. + +## Instalación { #installation } + +Installation of the module consists of two steps: + +1. [Preparing](#preparing-the-metadata-file) a metadata file with DHIS2 metadata. +2. [Importing](#importing-a-metadata-file-into-dhis2) a metadata file into DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Performing](#examples-of-other-modifications) package-specific modifications. + +This section deals with the first two steps of preparing and importing the metadata file into DHIS2, whilst the configuration procedure is discussed in the next section. It is recommended to first read through both sections before starting the installation and configuration process in DHIS2. In addition to the general steps described here, some of the configuration packages have annexes to the installation guide, describing particular issues. These are listed in the appropriate section [here](https://dhis2.org/who-package-downloads). + +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. + +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. + +## 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): + +* data elements (including categories) +* data sets +* indicators +* indicator types +* dashboards +* data visualizer, pivot table and GIS favourites + +The full list of objects included in the module (for which the administrator needs authorities to manage) can be found in the Metadata reference document for the particular configuration package. + +In cases where modifications to the .json metadata file of the configuration package are necessary [(see below)](https://who.dhis2.org/documentation/installation_guide_complete.html#preparing-the_metadata-file), a [text editor](https://en.wikipedia.org/wiki/Text_editor) is needed - these modifications should not be done with a word processor such as Microsoft Word. + +The configuration package can be installed in DHIS2 through the DHIS2 Health App, or manually through a .json file with DHIS2 metadata using the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. The procedure described in the rest of this section applies to the process of manually importing metadata. + +The [Configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) section applies for both methods. + +## 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).” + +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. + +## 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. + +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 base de datos 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. + +|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| +|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. + +## 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. + +|Objeto|UID|API endpoint| +|--|--|--| +|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. + +**Note 2**: An alternative approach to re-using the existing indicator types is to import those included in the configuration package, and removing the existing ones that overlap. This would require all indicators that use these existing indicator types to be updated to the newly imported indicator types, before the indicator types can be deleted. + +## Importing a metadata file into DHIS2 { #importing-a-metadata-file-into-dhis2 } + +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 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 appears when the actual import is attempted. In this case, the import summary will list any errors that need to be resolved. + +### 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. + +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. + +#### 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. + +#### 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. + +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. + +#### 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 +* 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. +* las futuras actualizaciones del paquete de configuración serán complicadas. + +## Additional Configuration { #additional-configuration } + +Once all metadata has been successfully imported, the module should be useable with only a few minor additional adjustments. In addition, depending entirely on the DHIS2 instance the module has been imported into, some additional configuration and modification might be necessary or advantageous. This section will first go through the necessary configuration steps, then mention some of the other types of modifications or configuration that might be relevant. + +## Required configuration { #required-configuration } + +Before the configuration packages can be used for data collection, there are two steps that are required. + +* Assign the data set(s) to appropriate organisation units +* Share the data set(s) with appropriate user groups +* Add your user(s) to the appropriate user groups + +The data sets should be assigned to the organisation units (facilities) which are expected to report on that particular data set. + +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. + +### 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: + +* Data elements/Data element groups +* Indicators/Indicator groups +* Data Sets +* Tableros + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +We recommend the following access + +|Objeto|User Group||| +|--|--|--|--| +||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| +|_Data Elements/Data element group_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadatos: puede ver
Datos: puede ver| +|_Indicators/Indicator group_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadatos: puede ver
Datos: puede ver| +|_Data sets_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadata : can view
Data: can capture and can view| +|_Dashboards_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadatos: puede ver
Datos: puede ver| + +### 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. + +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 data element categories exists these duplications can be hidden to end users through category option group sets, or certain metadata objects can be hidden for groups of users through sharing. + +It is recommended not to remove or replace the indicators included in configuration packages even though the same indicator already exists, so that the analytical outputs (which as based exclusively on indicators) can be kept. This will allow training material based on the configuration packages to be re-used. + +## Examples of other modifications { #examples-of-other-modifications } + +In addition to the required configuration, there are a number of other modifications and configuration that might be relevant, depending on the specific situation. It will not be possible to provide guidance and recommendations that cover all the different scenarios, but a brief discussion of some common problems are presented here. + +### Translations { #translations } + +Additional translations might have to be added, if other languages than those included are needed. + +### Adding additional variables { #adding-additional-variables } + +The configuration packages includes key recommended data elements and indicators. However, it might in some cases be necessary to add additional variables to address country-specific information needs. These could be added to the included data sets. + +### Updating layout of reporting forms { #updating-layout-of-reporting-forms } + +To facilitate the work of personnel doing data entry in DHIS2, it is sometimes desirable to add a custom data entry form that match the format of paper forms used at the primary level. + +## Maintenance { #maintenance } + +No particular maintenance is required for the configuration packages, since they are made up of standard DHIS2 metadata objects. However, before upgrading to new versions of DHIS2, it is important to test all functionality of the system in general on a staging/test server before upgrading any production instances of the system. + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md new file mode 100644 index 00000000..c969829e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/overview.md" +revision_date: '2023-03-07' +tags: +- Implementar +--- + +# COVID-19 Aggregate Surveillance { #covid-19-aggregate-surveillance } + +## Nota de lanzamiento { #release-note } + +- [Release Note](#c19-agg-release-note) + +## Diseño { #design } + +- [Version 2.0.0](#c19-agg-design) + +## Instalación { #installation } + +- [Installation Guide](#c19-agg-installation) + +## Referencia de metadatos { #metadata-reference } + +- [Version 2.0.0](https://packages.dhis2.org/en/C19_AGG/2.0.0/DHIS2.39/C19_AGG_COMPLETE_2.0.0_DHIS2.39.xlsx) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md new file mode 100644 index 00000000..e584b01a --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md @@ -0,0 +1,26 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implementar +--- + +# Release Note { #c19-agg-release-note } + +To see additional details of the metadata objects mentioned below, refer to the metadata reference documentation of the relevant version. + +## 2.0.0 { #200 } + +* The changes leading to this version were based on the revised [WHO Global surveillance of COVID-19 Weekly Aggregate Report ](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) +* The major were made on the age disaggregations with 5 year age bands used for <20 years and 60+ years spanning upto 80+years. +* Unknown age and Unknown sex were also introduced in the disaggregations to cater data that cannot be categorized with the options provided. +* Data elements for cases and deaths among health workers (Confirmed + Probable), tests with PCR assay, deaths amongst probable cases and health workers were introduced in this version. +* Data elements for logistics and cases by transmission classifications were removed. +* Considering these changes, all the core metadata objects; data elements, indicators, dashboard and its items, dataSets, indicator groups and data elements groups were newly created. +* This version now has only one dataSet designed for weekly reporting unlike in the previous version that had 2 dataSets reported weekly and daily basis. +* All the core metadata objects have been coded in support for international standard for aggregate data exchange (ADX). + +## 1.0.0 { #100 } + +Initial release of COVID-19 Aggregate Surveillance package + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md new file mode 100644 index 00000000..d44be85d --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -0,0 +1,291 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-design.md" +revision_date: '2022-09-13' +tags: +- Implementar +--- + +# COVID-19 Case Surveillance & Contact Tracing Design { #c19-cs-design } + +Demo: [https://demos.dhis2.org/covid-19](https://demos.dhis2.org/covid-19) + +## Purpose { #purpose } + +The COVID-19 Surveillance System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Antecedentes { #background } + +**This design has been updated to reflect new aggregate reporting requirements from the [WHO interim surveillance guidelines updated March 20, 2020][1]**. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| Type of Surveillance Package | Case Surveillance (Tracker) | Surveillance (Event) | Surveillance (Aggregate) | +|---|---|---|---| +| ***Description*** | Enrols a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables daily or weekly reporting of key aggregate data points | +| ***Pros*** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| ***Cons*** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) | + +**This document covers only the design of the surveillance tracker program package**; separate system design documents are available for DHIS2 event and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing case disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 surveillance package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions][2], updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +The DHIS2 case surveillance tracker metadata was based on the **[WHO COVID-19 case reporting template][3]** and the mapping of data dictionaries can be accessed at: [DHIS2 CBS tracker metadata WHO line-list data dictionary][4]. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles][5] and a common [naming convention][6]. + +The COVID-19 digital data package supports surveillance workflows and automated analysis for key components of routine and active surveillance. This package includes a Case Surveillance Tracker and Contact registration & follow-up tracker, which are installed together in the same metadata package. The tracker programs are optimized to be installed with other COVID-19 surveillance packages, including the Points of Entry Screening Tracker and aggregate daily surveillance dataset. + +1. **[Use Case 1: COVID-19 Case surveillance tracker][7]**: enrols & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. Metadata for the case surveillance tracker is aligned with the WHO [COVID-19 surveillance data dictionary][8] + + > n.b. The COVID-19 case tracker can be implemented either as a ‘standalone’ program for COVID-19 specific disease surveillance as described here; or, COVID-19 concepts can be integrated into an existing case surveillance tracker program if one already exists in-country. Please refer to installation and implementation guidance for more details. + +1. **[Use Case 2: Contact registration & follow-up][9]**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. + +Digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [Google Play store][10]. + +## Use Case 1: COVID-19 Case surveillance tracker { #use-case-1-covid-19-case-surveillance-tracker } + +The COVID-19 case surveillance tracker can be adapted and used by countries to supplement existing national disease surveillance programs. The basic case surveillance program is designed to: + +1. Enroll suspected\* COVID-19 cases (*generally appearing at a health facility, but may be enrolled at other places*) +2. Capture key information about the suspected case including demographics and exposures, such as symptoms, contact with a previously confirmed case & travel history +3. Generate lab requests +4. Record laboratory diagnosis +5. Record contacts of a confirmed\*\* or probable\*\*\* case for follow-up +6. Record case outcome +7. Facilitate case notification and national/regional/global case reporting +8. Generate dashboards and analytics tools for monitoring disease trends and planning response efforts + +The design of the case tracker program assumes that [WHO case definitions][1] are followed in the use case; its use can be adapted to local case definitions as needed. The WHO case definitions were updated on March 20, 2020 and noted below. + +> \* Suspected case: A) a patient with acute respiratory illness (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness of breath), AND with no other aetiology that fully explains the clinical presentation AND a history of travel to or residence in a country/area or territory reporting local transmission of COVID-19 disease during the 14 days prior to symptom onset; **OR**, B) A patient with any acute respiratory illness AND having been in contact with a confirmed or probable COVID-19 case (see definition of contact) in the last 14 days prior to onset of symptoms; **OR,** C) A patient with severe acute respiratory infection (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness breath) AND requiring hospitalization AND with no other aetiology that fully explains the clinical presentation. +> +>\*\* Probable case: A) a suspect case for whom testing for COVID-19 is inconclusive (inconclusive being the result of the test reported by the laboratory) **OR,** B) a suspect case for whom testing could not be performed for any reason. +> +>\*\*\* Confirmed case: A person with laboratory confirmation of COVID-19 infection, irrespective of clinical signs and symptoms. + +### 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 +* 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 + +### Workflow: COVID-19 Case Surveillance Tracker { #workflow-covid-19-case-surveillance-tracker } + +![Workflow of the DHIS2 COVID-19 Case Surveillance Tracker](resources/images/sdd-tracker-v3-case1-workflow.png) + +### Structure: COVID-19 Case Surveillance Tracker Program { #structure-covid-19-case-surveillance-tracker-program } + +![Structure of the COVID-19 Case Surveillance Tracker Program](resources/images/sdd-tracker-v3-case1-structure-v2.png) + +#### Program Description: COVID-19 Case Testing, Diagnosis & Outcome { #program-description-covid-19-case-testing-diagnosis-outcome } + +| Stage | Descripción | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is the case, which is represented by a Tracked Entity Type of ‘person.’ The *Enrollment date* is the date of registration of the case. The Related programs is *COVID-19 Contact registration & follow-up*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *Age*, *First Name*, *Surname*, *Sex*, *Case phone number*, *First Name (parent or care)*, *Surname (parent or carer)*, *Home Address*, *Workplace/school physical address*, *Country of Residence*, *Facility contact number*| +| **Stage 1: Clinical Examination and Exposures** | This stage records a suspected case’s clinical symptoms and exposures including: *Symptoms*, *Pregnancy and underlying conditions*, *Hospitalisation and Isolation*, *Exposures in 14 days prior to symptoms*, *Travel history*, *Contact with confirmed case*. After examination, you can record if the case has been hospitalised or isolated, and information surrounding this. | +| **Stage 2: Lab Request [repeatable]** | The lab request records the reason for testing and other information that a lab needs to process a sample and test it for COVID19. The information provided here can help lab personnel prioritize lab tests when resources are limited. The person entering this data could be the same person who registered the suspected case and recorded the patient’s clinical exam and exposures; or may be other personnel charged with making lab requests. | +| **Stage 3: Lab Results [repeatable]** | The Lab Results stage records the type and results from laboratory testing. It can be done directly at the lab or as secondary data entry. This stage is repeatable as samples for a given case may be tested multiple times (i.e. in the case of an inconclusive laboratory results, a new lab test can be conducted and results recorded). | +| **Stage 4: Health Outcome** | The health outcome records the final outcome of the case: (recovered, not recovered, dead or unknown) including date of discharge or death as applicable. | + +#### Enrollment Stage { #enrollment-stage } + +![Enrollment](resources/images/sdd-tracker-v3-case1-enrollment.png) + +#### Program Stage 1 - Clinical Examination & Diagnosis { #program-stage-1-clinical-examination-diagnosis } + +##### Section 1 - Clinical Signs and symptoms { #section-1-clinical-signs-and-symptoms } + +Selecting “yes” to the Data Element ‘Any signs or symptoms?’ reveals the rest of the options. + +![Section 1](resources/images/sdd-tracker-v3-case1-stage1-section1.png) + +##### Section 2 - Pregnancy Details { #section-2-pregnancy-details } + +This section is hidden unless gender is selected as ‘Female.’ + +![Section 2](resources/images/sdd-tracker-v3-case1-stage1-section2.png) + +##### Section 3 - Underlying Conditions/Comorbidity { #section-3-underlying-conditionscomorbidity } + +The details of this section are hidden unless “Any underlying conditions” is marked as “Yes”. + +![Section 3](resources/images/sdd-tracker-v3-case1-stage1-section3.png) + +##### Section 4 - Hospitalisation { #section-4-hospitalisation } + +The details of this section is hidden unless “Hospitalised” is marked as “Yes”. + +![Section 4](resources/images/sdd-tracker-v3-case1-stage1-section4.png) + +##### Section 5 - Exposure Risk { #section-5-exposure-risk } + +This section is used to record exposures + + 1. The fields ***country, city and facility*** are hidden by program rules if the case is not a health care worker; + 2. The fields for contact IDs are hidden by program rules if the case has not had contact with a confirmed case in 14 days. + +A suspected case’s exposure to a *previously confirmed* case is distinct from prospective contact tracing in Program Stage 5. + +![Section 5](resources/images/sdd-tracker-v3-case1-stage1-section5.png) + +##### Section 6 - Travel History { #section-6-travel-history } + +![Section 6](resources/images/sdd-tracker-v3-case1-stage1-section6.png) + +#### Program Stage 2: Lab Request { #program-stage-2-lab-request } + +![Stage 2](resources/images/sdd-tracker-v3-case1-stage2.png) + +#### Stage 3: Lab Results { #stage-3-lab-results } + +![Stage 3](resources/images/sdd-tracker-v3-case1-stage3.png) + +#### Stage 4: Health Outcomes { #stage-4-health-outcomes } + +![Stage 4](resources/images/sdd-tracker-v3-case1-stage4.png) + +### Program Rules: COVID19 Case Surveillance Tracker { #program-rules-covid19-case-surveillance-tracker } + +The following program rules have been configured. If a country has an existing case surveillance program and wishes to incorporate elements of the COVID-19 case tracker into their existing program, special attention must be paid to the configuration of program rules. + +| Program Rule Name | Program Rule Description | +|---|---| +| Assign Enrollment Date | This assigns the enrollment date if there is no onset date available to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators. | +| Assign Onset Date| This assigns the onset date to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators.| +| Calculate and assign patient age in years | Calculate and assign patient age in years based on DOB | +| Display patient age in years + days | Display patient age in years + days | +| Hide Date of Death | Hide the Date of Death unless Death is the health outcome | +| Hide Date of Discharge | Hide Date of Discharge if no outcome or if the outcome is death | +| Hide Measured Temperature field | Hide Measured Temperature field until Fever is selected | +| Hide confirmed case ID's if no contact with other confirmed cases| Hides any contact ID's if the case has not been in any contact with other confirmed cases | +| Hide health care worker details if not a health worker | Hide health care worker details if not a health worker | +| Hide health outcome explanation if health outcome is not other | Hide health outcome explanation if health outcome is not other | +| Hide hospitalisation details if hospitalisation is no or unknown | Hide hospitalisation details if hospitalisation is no or unknown | +| Hide isolation date if case is not in isolation | Hide isolation date if case is not in isolation | +| Hide pregnancy details for a female if not pregnant | Hide pregnancy details for a female if not pregnant | +| Hide pregnancy details section if sex is male | Hide pregnancy details section if sex is male | +| Hide reason for testing explanation if an option is selected | Hide reason for testing explanation if an option is selected | +| Hide travel history details if no travel 14 days prior to symptom onset | Hide travel history details if no travel 14 days prior to symptom onset | +| Hide underlying conditions if case does not have any | Hide underlying conditions if case does not have any | +| Show warning if the event date is after the enrollment date | Show warning on completion of an event if the event date is before the enrollment date | + +You can read more about program rules here: [https://docs.dhis2.org/master/en/user/html/configure\_program\_rule.html][11] + +### Indicadores de programa { #program-indicators } + +From the data captured in the COVID-19 case surveillance program, we can calculate at least the following indicators including those recommended by the WHO for daily and weekly aggregate reporting and present them in a dashboard: + +| Indicator name | Descripción | +|---|---| +| COVID-19 - Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU) | *Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU)* | +| COVID-19 Contacts | *Counts the number of relationships (‘has been in contact with’) created that are linked to the case TEI* | +| COVID-19 - Deaths (all suspected cases) | *COVID-19 related deaths (deaths recorded among all suspected cases)* | +| COVID-19 - Deaths (confirmed cases) | *COVID-19 related deaths (deaths recorded among confirmed cases)* | +| COVID-19 - Deaths (probable cases) | *COVID-19 related deaths (deaths recorded among all probable cases)* | +| COVID-19 - Confirmed Hospitalised Cases | *Number of confirmed cases that were admitted into hospital* | +| COVID-19 - Imported Cases | *Cases where likely source of infection is recorded as another country or imported from another country.* | +| COVID-19 - Laboratory confirmed cases | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by report date* | +| COVID-19 - Laboratory confirmed cases - by onset of symptoms | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by date of onset of symptoms* | +| COVID-19 - Laboratory tested cases | *Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)* | +| COVID-19 - Local transmission cases | *Number of suspected cases where transmission is local (no travel in last 14 days* | +| COVID-19 - Probable cases | *Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date* | +| COVID-19 - Probable cases - by onset of symptoms | *Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms* | +| COVID-19 - Recovered confirmed cases | *Number of laboratory confirmed cases with outcome recovered*| +| COVID-19 - Suspected cases | *Total number of cases suspected with COVID-19, by report date* | +| COVID-19 - Suspected cases - by onset of symptoms | *Total number of cases suspected with COVID-19, by date of onset of symptoms* | +| COVID-19 - Suspected cases without a positive test result | *Total number of suspected cases without a positive lab result* | +| COVID-19 Total number of laboratory tests conducted | *Total number of lab tests conducted (count of tests, not cases)* | +| COVID-19 Total number of positive tests | *Total number of lab tests returned with positive results (count of tests, not cases* | +| COVID-19 Deaths by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Confirmed cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Suspected cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | + +## Use Case 2: COVID-19 Contact registration & follow-up { #use-case-2-covid-19-contact-registration-follow-up } + +This program can be used in addition to the case surveillance tracker to facilitate the registration and follow-up of contacts of a confirmed case. In this scenario, it is assumed that if any contacts of a confirmed case meet criteria for suspected case and are referred for testing, the case will be enrolled into the COVID-19 Case Surveillance tracker program. + +The Contact registration & follow-up program registers each contact of a case (as described in COVID-19 Case Surveillance Use Case) as a new Tracked Entity Instance (person) and links them to the case in the COVID-19 Case Surveillance Program via a ‘relationship.’ It has a simple repeatable follow-up stage where symptoms and any follow-up undertaken can be registered. + +### Workflow: Contact registration & follow-up { #workflow-contact-registration-follow-up } + +![Worflow of the Contact registration & follow-up](resources/images/sdd-tracker-v3-case2-workflow.png) + +### Program Description: Contact registration & follow-up { #program-description-contact-registration-follow-up } + +| Stage | Descripción | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is represented by a Tracked Entity Type of ‘person.’ The Related program is *COVID-19 Case based surveillance*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *First Name*, *Surname*, *Date of birth*, *Age*, *Sex*, *Phone number (local)*, *Home Address*, *Country of Residence* | +| **Stage 1: Follow-Up [non-repeatable]** | This stage is meant to record information related to contact tracing follow up, given that a contact has already been identified. It is divided into two sections: *1. Relation with case*, *2. Exposure Assessment* | +| **Stage 2: Symptoms[repeatable]** | This stage is intended to record symptoms of the case. Follow-up to check on the symptoms of a contact can be repeated until the follow-up period is complete (for example, after 14 days or according to national guidelines). When follow-up period is complete, the enrollment can be ‘completed.’ *1. Symptoms*| + +Contacts are added to the index case using the relationships menu in the case surveillance program: + +![Profile](resources/images/sdd-tracker-v3-case2-profile.png) + +Once you select “Add” from the relationships box, you are able to select the relationship and program and either select an existing person or enroll a new contact using the enrollment stage that appears. This will enroll the contact into the contact registration and follow-up +program. + +![Add a relationship](resources/images/sdd-tracker-v3-case2-add-relationship.png) + +Contacts that are added will then be listed on the case’s tracker dashboard in the relationship +widget + +![Relationships widget](resources/images/sdd-tracker-v3-case2-relationships-widget.png) + +You may also enroll them separately into the program. Once enrolled, you will be able to find them for the follow-up as required. + +#### Inscripción { #enrollment } + +![iEnrollment in the use case 2](resources/images/sdd-tracker-v3-case2-enrollment-case2.png) + +#### Program Stage 1 : Follow - Up { #program-stage-1-follow-up } + +![Case 2 Stage 1](resources/images/sdd-tracker-v3-case2-stage1.png) + +#### Program Stage 2 : Symptoms { #program-stage-2-symptoms } + +![Case 2 Stage 2](resources/images/sdd-tracker-v3-case2-stage2.png) + +### Program Indicators: Contact Registration { #program-indicators-contact-registration } + +| Program Indicator Name | Descripción | +|---|---| +| COVID-19 travelers screened | Total number of travelers screened and enrolled in screening program from POE | +| COVID-19 travelers cleared at POE | Number of travelers cleared after POE screening (no follow-up required) | +| COVID-19 travelers with symptoms at POE | Number of travelers presenting with symptoms during POE screening | +| COVID-19 travelers cleared after 14 days monitoring | Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period) | +| COVID-19 travelers referred to health facility | Number of travelers that were referred to a health facility at any time during 14 day followup | +| COVID-19 travelers enrolled for 14 day follow-up | Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening | +| COVID-19 currently under follow-up | Number of travelers that have not been cleared or referred to a health facility | +| COVID-19 travelers developed symptoms during follow-up | Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening) | + +## Referencias { #references } + +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form [https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + +[1]: https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf +[2]: https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions +[3]: https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx +[4]: https://drive.google.com/open?id=1vigXHkP7L2hJ2lrZpdf9u4csQtppMH16 +[5]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html +[6]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html +[7]: #use-case-1-covid-19-case-surveillance-tracker +[8]: https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2 +[9]: #use-case-2-covid-19-Contact-registration-follow-up +[10]: https://play.google.com/store/apps/details?id=com.dhis2&hl=en +[11]: https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md new file mode 100644 index 00000000..ba3aaa27 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-installation.md" +revision_date: '2022-09-13' +tags: +- Implementar +--- + +# COVID-19 Surveillance - Installation Guide { #c19-cs-installation } + +## 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: + +1. COVID-19 Case-based Surveillance Tracker program & COVID-19 Contact Registration & Follow-Up program +2. Points of Entry Screening Tracker program + +You will have to follow the instructions in full for each separate package that you install. + +## Instalación { #installation } + +La instalación del módulo consta de varios pasos: + +1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. +2. [Importar](#importing-metadata) el archivo de metadatos en DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Adaptar](#adapting-the-tracker-program) el programa después de ser importado + +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. + +## Requisitos { #requirements } + +Para instalar el módulo, se requiere una cuenta de usuario administrador en DHIS2. El procedimiento descrito en este documento debe probarse en un entorno de prueba/preparación antes de realizarse en una instancia de producción de 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/). + +## 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).” + +Si bien no siempre es necesario, a menudo puede resultar ventajoso realizar ciertas modificaciones en el archivo de metadatos antes de importarlo a DHIS2. + +### Dimensión de datos predeterminada { #default-data-dimension } + +En las primeras versiones de DHIS2, el UID de la dimensión de datos predeterminada se generaba 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 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 + +|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| +|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. + +### Tipos de indicadores { #indicator-types } + +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 simplemente por su factor y si son o no números simples sin denominador, no son ambiguos y pueden reemplazarse mediante una búsqueda y reemplazo de los UID. Esto evita posibles conflictos de importación y evita la creación de tipos de indicadores duplicados. La Tabla 2 muestra los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes. + +|Objeto|UID|API endpoint| +|--|--|--| +|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 } + +Al igual que los tipos de indicadores, es posible que ya existan tipos de entidades tracker en su base de datos DHIS2. Las referencias al tipo de entidad tracker deben cambiarse para reflejar lo que hay en su sistema para no crear duplicados. La Tabla 3 muestra los UID que podrían reemplazarse, así como los API endpoints para identificar los UID existentes + +|Objeto|UID|API endpoint| +|--|--|--| +|Persona|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| + +## 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. + +### 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. + +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. + +#### Alternativa 1 { #alternative-1 } + +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 vaya a utilizar material de formación y documentación basados en el paquete de configuración. + +#### Alternativa 2 { #alternative-2 } + +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. + +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. + +#### Alternativa 3 { #alternative-3 } + +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: + +* 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 } + +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: + +* Tipo de entidad Tracked +* Programa +* Etapas del programa +* Tableros + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +By default the following is assigned to these user groups + +|Objeto|User Group||| +|--|--|--|--| +||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| +|_*Tracked entity type*_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadatos : puede ver
Datos: puede ver y capturar| +|_*Program*_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadatos : puede ver
Datos: puede ver y capturar| +|_*Program Stages*_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadatos : puede ver
Datos: puede ver y capturar| +|_*Dashboards*_|Metadatos: puede ver
Datos: puede ver|Metadatos : puede ver y editar
Datos: puede ver|Metadatos: puede ver
Datos: puede ver| + +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. + +### Roles de usuario { #user-roles } + +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. 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. + +### Unidades organizativas { #organisation-units } + +Debe asignar el programa a unidades organizativas dentro de su propia jerarquía para poder ver el programa en Tracker - captura de datos. + +### 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).” + +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). + +## Adaptar el programa { #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. +* 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 + +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__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md new file mode 100644 index 00000000..bc802bc5 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md @@ -0,0 +1,29 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/overview.md" +revision_date: '2022-11-22' +tags: +- Implementar +--- + +# COVID-19 Case Surveillance { #covid-19-case-surveillance } + +## Nota de lanzamiento { #release-note } + +- [Release Note](#c19-cs-release-note) + +## Diseño { #design } + +- [Version 1.0.2](#c19-cs-design) + +## Instalación { #installation } + +- [Installation Guide](#c19-cs-installation) + +## Referencia de metadatos { #metadata-reference } + +- [Version 1.0.2](https://packages.dhis2.org/en/C19_CS/1.0.2/C19_CS_COMPLETE_1.0.2_DHIS2.37.xlsx) + +## Training Material { #training-material } + +- [COVID-19 Training Material](https://dhis2.org/covid-training-material) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..57a3fb4e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md new file mode 100644 index 00000000..f03eeee8 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -0,0 +1,136 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/c19_poe-design.md" +revision_date: '2022-07-05' +tags: +- Implementar +--- + +# COVID-19 Points of Entry Tracker Design { #c19-poe-design } + +Demo: [https://covid19.dhis2.org/](https://covid19.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Points of Entry (POE) Screening System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Antecedentes { #background } + +The Points of Entry Screening Tracker is inspired by the pioneering design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health. In January 2020, the Sri Lanka MOH implemented screening measures at ports of entry like airports to identify travelers who may have been exposed to nCoV-19. DHIS2 tracker was to enroll travelers entering Sri Lanka who had visited countries impacted by COVID-19. DHIS2 tracker enabled follow-up with travelers at field level for 14 days to ensure no symptoms developed. If symptoms developed, travelers would be referred to a health facility for clinical examination and testing. The POE tracker can be used in combination with other COVID-19 digital data packages that include case surveillance and contact tracing. + +The World Health Organisation (WHO) has published [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). Points of entry (POE) include international airports, seaports and land crossings. POE measures include 1) detection of ill travellers; 2) interview of ill travellers for COVID-19; 3) reporting of alerts of ill travellers with suspected COVID-19 infection and 4) isolation, initial case management and referral of ill travellers with suspected COVID-19 infection. These guidelines should be consulted, in addition to national protocols for points of entry. + +## System Design Summary { #system-design-summary } + +### Caso de uso { #use-case } + +The POE tracker program use case was designed to support the registration of travelers 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. For this use case, it is assumed that a traveler may be 1) screened and cleared immediately with no follow-up needed; 2) screened and followed up for 14 days [with or without isolation measures] to ensure no symptoms develop; or 3) screened and referred for testing and/or initial case management. The current design proposes that a traveler meeting the country’s definition of a suspected case would be enrolled into the complementary DHIS2 COVID-19 Case-Based Surveillance (CBS) Tracker. For example, a traveler enrolled in this program who later meets the definition of a suspected case during follow-up (i.e. an asymptomatic traveler from a country with known transmission is registered at the POE and later develops symptoms) is enrolled as a suspected case into the COVID-19 CBS program to capture all clinical details, exposures and follow the case through laboratory diagnosis and case outcome. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +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 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. +* National and local health authorities: monitor and analyse data through dashboards and analytics tools to conduct risk assessments and plan response measures. + +### Workflow { #workflow } + +The Points of Entry program workflow is based on the following scenario + +![Scenario](resources/images/POE_image01.png "Scenario") + +In this design, it is assumed a traveler would complete their enrollment in the POE under the following scenarios: + +1. Traveler is marked as ‘cleared’ during initial screening or after 14 day follow-up +2. Traveler is referred to health facility at any point during follow-up + +**A traveler that is referred to a health facility is expected to be enrolled in the COVID-19 Case-based Surveillance Tracker as a suspected case** (according to national guidelines). Details about a suspected case including clinical exam, exposures, laboratory results and case outcome would be recorded in the CBS program. + +### Structure: Points of Entry Screening Tracker Program { #structure-points-of-entry-screening-tracker-program } + +![Structure](resources/images/POE_image02.png "Structure") + +#### Consideration for Organisation Units & Geography { #consideration-for-organisation-units-geography } + +This program design assumes that Points of Entry such as airports, seaports or land crossings will be created as organisation units included in the OU hierarchy. The program would be assigned to the POE org units. Primary analysis is based on the enrolling Org Unit (the port of entry). + +Additional geographical components are also captured as other dimensions: + +1. TEI coordinates: It is possible to capture TEI coordinates when registering the traveler as TEI. These can be displayed in the maps app. Local protocols may choose what coordinates to enter, for example the TEI’s local residence where he/she may be self-quarantined for 14 days. +2. Event coordinates: for screening and follow-up stages, coordinates can be captured on the event and displayed in a map. For example, the user may capture a traveler’s location each time they are followed up (i.e. in the case of tourists or others not in home quarantine). + +#### Program Description { #program-description } + +|Stage|Descripción| +|--|--| +|**Registration**|The Tracked Entity is the traveler, which is represented by the Tracked Entity Type of ‘person.’ The TEI is configured to collect a geographic ‘point’ during registration. These can be analyzed in a map.| +|**Enrollment details**|Enrollment date
The first Program Stage is configured to appear on the Registration page so that a user does not need to click through to add the first event.| +|**Atributos**|Attributes include basic personal information and unique case identifiers
- Passport number
- Local Case ID
- Age
- First Name
- Surname
- Country of residence
- Sex
- Date of birth
- Local address
- Home address
- Telephone (local)
- Telephone (foreign)
- Emergency contact
- Emergency contact phone
- Email| +|**Stage 1**
**Screening at POE**
**(non-repeatable)**|This stage records:
- Traveler details (countries visited, flight number, date of departure, etc)
- Examination: recorded temperature
- Symptoms: this list includes symptoms typically checked for both COVID-19 symptoms and symptoms of other potential notifiable diseases
- Case clearance

If the traveler is marked as ‘cleared’, no further follow up is required; the enrollment may be closed. If the traveler requires follow-up, an event can be scheduled for follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 2:**
**Follow-up (within 14 days)**
**(repeatable)**|Data is entered at this stage if any interim follow-up is performed before the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment may be closed if no further monitoring & follow-up is planned in this program.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 3:**
**Follow-up (after 14 days)**
**(non-repeatable)**|Data is entered at this stage at the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)
- Case clearance

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment should be closed at the completion of 14 day follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization. + +![Enrollment](resources/images/POE_image03.png "Enrollment") + +![Program Stage 1 - Screening at POE](resources/images/POE_image04.png "Program Stage 1 - Screening at POE") + +![Program Stage 1 - Screening at POE](resources/images/POE_image05.png "Program Stage 1 - Screening at POE") + +![Program Stage 2: Follow-up (within 14 days)](resources/images/POE_image06.png "Program Stage 2: Follow-up (within 14 days)") + +![Program Stage 3: Follow up (after 14 days)](resources/images/POE_image07.png "Program Stage 3: Follow up (after 14 days)") + +#### How to refer the TEI to another Organisation Unit { #how-to-refer-the-tei-to-another-organisation-unit } + +Primary analysis is completed on the enrolling organisation unit (the port of entry). Referral facility is captured as a Data Element (type: Organisation Unit) in order to display travelers by referral to health facility in the analytics apps (i.e. Event Report). In some use cases, it may be desirable to refer the TEI (the traveler) to another Org Unit for follow-up. + +A TEI can be ‘referred’ to another org unit such as a health facility for one event or permanently. In this case, health facility user must be able to search TEIs enrolled in the relevant Points of Entry org units. For example, if after screening a traveler at the POE, the traveler may be “referred” to a district health office near the traveler’s local address for follow-up by district health staff. After completing the data entry for Stage 1 (screening), the user would refer the TEI to a District Health Center. Read more about referrals in tracker in [DHIS2 User Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/tracking-individual-level-data/tracker-capture.html). + +![alt_text](resources/images/POE_image08.png "image_tooltip") + +### Program Relationships { #program-relationships } + +This program has the relationshipType ‘Has been in contact with’. Users can create a relationship between TEIs enrolled in the POE program and TEIs in other COVID-19 tracker programs (Case-based Surveillance, Contact Registration & Follow-up). The relationship can be added at any point in the program stages during data entry. + +### Program Rules { #program-rules } + +The following program rules have been configured. + +|Program Rule Name|Program Rule Description| +|--|--| +|Calculate and assign patient age in years|Calculate and assign patient age in years| +|Hide countries if not visited|Hide countries if not visited| +|Hide Follow-Up Stages|Hide Follow-Up Stages if the case is cleared at the port of entry| +|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)| +|Hide symptoms if no symptoms present (Follow Up within 14 days)|Hide symptoms if no symptoms present (Follow Up within 14 days)| +|Hide symptoms if no symptoms present (PoE)|Hide symptoms if no symptoms present (PoE)| + +You can read more about program rules here: +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +||| +|--|--| +|COVID-19 travelers screened|Total number of travelers screened and enrolled in screening program from POE| +|COVID-19 travelers cleared at POE|Number of travelers cleared after POE screening (no follow-up required)| +|COVID-19 travelers with symptoms at POE|Number of travelers presenting with symptoms during POE screening| +|COVID-19 travelers cleared after 14 days monitoring|Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period)| +|COVID-19 travelers referred to health facility|Number of travelers that were referred to a health facility at any time during 14 day followup| +|COVID-19 travelers enrolled for 14 day follow-up|Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| +|COVID-19 currently under follow-up|Number of travelers that have not been cleared or referred to a health facility| +|COVID-19 travelers developed symptoms during follow-up|Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)| +|COVID-19 % travelers developed symptoms during 14-day follow-up|Numerator: Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)
Denominator: Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| + +Users can also generate an Event Report to see: + +1. Travelers by nationality and/or originating country +2. Referrals to health facility + +## Referencias { #references } + +* DHIS2 COVID-19 [Tracker Package Installation Guide](covid-19-tracker-installation.html) +* World Health Organisation (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) (interim guidance, published 19 March 2020) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md new file mode 100644 index 00000000..eaa2b386 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implementar +--- + +# COVID-19 Points of Entry { #covid-19-points-of-entry } + +## Diseño { #design } + +[Version 1.0.2](#c19-poe-design) + +## Instalación { #installation } + +[Installation Guide](#c19-poe-installation) + +## Nota de lanzamiento { #release-note } + +[Release Note](#c19-poe-release-note) + +## Referencia de metadatos { #metadata-reference } + +[Version 1.0.2](https://packages.dhis2.org/en/C19_POE/1.0.2/C19_POE_COMPLETE_1.0.2_DHIS2.37.xlsx) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md new file mode 100644 index 00000000..f3fbe84e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -0,0 +1,164 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/c19_evt-design.md" +revision_date: '2022-11-08' +tags: +- Implementar +--- + +# COVID-19 Surveillance Line-list Design { #c19-evt-design } + +Demo: [https://covid.dhis2.org](https://covid.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Surveillance Event Program System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Antecedentes { #background } + +The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +|Type of Surveillance Package|Case-based Surveillance (Tracker)|Surveillance (Event)|Surveillance (Aggregate)| +|--|--|--|--| +|_Description_|Enrolls a case and tracks over time through laboratory confirmation & case outcome|Captures critical case details in line-listing format|Enables daily or weekly reporting of key aggregate data points| +|_Pros_|Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case|More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity|Low complexity, easy to implement, most manageable when cases numbers are high| +|_Cons_|Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation|Does not support case-follow up or other decentralized workflows|Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) + +**This document covers only the design of the surveillance event program package**; separate system design documents are available for DHIS2 Tracker and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +This package is designed as a DHIS2 [Event Program](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#about_event_program). **The Event Program is not designed to capture all data variables contained in the [WHO case reporting template](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx)**. To capture a complete set of WHO case reporting variables, please refer to the DHIS2 COVID-19 Case-based Surveillance Tracker. Rather, the event program is a simplified program that captures a subset of minimum critical data points to facilitate high data quality when the number of caseloads or burden of reporting exceeds capacity for successfully completing the full line-list for suspected COVID-19 cases. For implementers who wish to capture the complete WHO line-listing, please refer to the COVID-19 Case-based Surveillance Tracker Package. + +The COVID-19 Surveillance Event Program data package includes: + +1. Event program and data elements case reporting +2. Core indicators +3. Tablero (Dashboard) + +### Use Case: Simplified line-listing of COVID-19 cases { #use-case-simplified-line-listing-of-covid-19-cases } + +As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The event package is designed to capture the most critical data points in a line-list and analytical capacities for surveillance and response. The event package is designed as a standalone program. However, countries may use the event package in combination with other packages (i.e. event reports and daily aggregate reporting); or, they may shift from tracker to event to aggregate as caseloads and reporting burden increases. **_Countries should plan carefully how they intend to implement these packages in combination, including reporting flows, transitioning from one data model to another, and how to maintain historical data for analysis if transitioning between data models. _** + +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 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 + +#### Workflow { #workflow } + +Unlike the tracker program, there are limitations to decentralization of the data reporting workflow in an Event program. The most significant limitation is that the Case Outcome (recovery or death) is often not known until days or weeks after the case is reported. The current program design allows for the following workflow options: + +1. Event is created when a suspected case is reported. All known data is entered, but the event is not completed. A user can select an ‘Active Event’ from a working list based on User filters and criteria. When missing data becomes available (i.e. the case outcome), the user can enter the remaining data fields and complete the event. Cases can be identified in the event list by the Case ID data element. See the image below as an example which can be accessed within the Capture App: +![Capture App](resources/images/EVENT_image1.png "Capture App") + +2. Event is created. All case related data is entered retrospectively, including the Outcome. Event is completed. _The limitation is this approach is timeliness of the data reporting, as new suspected cases might not be captured until their outcome which is often too late for decision making._ + +### Program Structure { #program-structure } + +The program is called ‘COVID-19 Cases (events)’ + +|Section|Descripción| +|--|--| +|Date of report|Event Date
_Countries may re-name the event date to apply to their protocols._| +|Section 1
**Basic Information**|Records basic demographic data.
_Countries may add data elements as desired._
- **Patient ID**
Can be used to filter events in working lists, eg. Active events
- **Sex**
- **Age**| +|Section 2
Case Details|Records information about the case including symptoms, severity, testing, etc.
- **Symptoms**
Options: Yes / No
Specifies whether a case has any symptoms at time of notification

- **Date of symptoms onset**
Only appears if symptoms are present;
Date of symptoms onset, if available, will replace “Date of Report” in data analytics and reporting.

- **Case Severity (at time of notification)**
Options: Mild / Moderate / Severe / Critical
- **Laboratory tested?**
Options: Yes / No/ Unknown
Specifies whether a case has been laboratory tested for COVID-19

- **Test Result**
Only appears if the case was laboratory tested
Options: Inconclusive / Positive / Negative / Unknown
The program is designed to capture only the final test result. Results for each individual test (if available) and the total number of tests performed are not captured.
- **Case Classification**
Options: Suspected case / Probable case / Laboratory confirmed case
Automatically assigned values
The values are assigned by Program rules in accordance with WHO case definitions
This feature can be useful in filtering active cases in the working lists.| +|Section 3
**Exposures**|- **Has the case traveled in the 14 days prior to symptoms onset?**
Options: Yes / No / Unknown
Specifies travel history of the case.

- **Likely Infection Source**
Options: Imported case* / Local Transmission / Exposure unknown
* Imported case option appears only if the case traveled in the 14 days prior to symptoms onset

- **Specify local source**
Only appears if Likely Infection Source is Local Transmission
Options: Community (workplace, public transport, etc.) / Household / Healthcare Facility / Close Contact with Other Infected Individual / Exposure Unknown

- **Case Type**
Options: New index case / Linked to existing cluster / Unknown
Specifies whether the case is connected to an existing cluster or is a new index case| +|Section 4
**Treatment**|- **Hospitalised**
Options: Yes / No

- **Did the case receive care in an intensive care unit (ICU)?**
Only appears if the case is hospitalised
Options: Yes / No| +|Section 5
**Contacts**|- **Total number of contacts followed for this case**
Records number of contacts| +|Section 6
**Outcome**|- **Health outcome**
Options: Recovered / Death| +|Section 7
**Assigned Date of onset of symptoms**|- **Calculated onset date (for Indicators)**
This section is used only to calculate indicators based on report date vs. date of onset of symptoms]
This automatically assigned date is used in program indicators. Initially, it is the report date. If the date of onset of symptoms is available, the date is replaced by the date of onset of symptoms.| +|**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.| + +### Grupos de Usuarios { #user-groups } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Currently, only users assigned to the COVID19 data capture group will have access to capture data in the program. Please refer to the installation guidance for more instructions. + +### Program Rules { #program-rules } + +The following program rules have been configured for the program: + +|Program Rule Name|Program Rule Description| +|--|--| +|Assign Empty Value to Class Classification|Automation: Assign Empty Value to Class Classification| +|Assign Event Date|Automation: Assign Event date if to onset date if no Onset date is available| +|Assign 'Laboratory Confirmed Case' to Case Classification|Automation: Assign 'Laboratory Confirmed Case' to Case Classification| +|Assign Onset Date|Automation: Assign Symptoms Onset Date if available| +|Assign 'Probable Case' to Case Classification|Automation: Assign 'Probable Case' to Case Classification| +|Assign 'Suspected Case' to Case Classification|Automation: Assign Suspected Case' to Case Classification| +|Hide Case Classification Field|Hide Case Classification Field until Lab Test question is answered| +|Hide ICU field|Hide ICU field unless Hospitalised| +|Hide 'Imported Case'|Hide 'Imported Case' if not traveled| +|Hide Onset of Symptoms Date|Hide Onset of Symptoms Date if no symptoms| +|Hide Outcome Options|Hide irrelevant Outcome Options| +|Hide 'Specify Local Infection Source'|Hide 'Specify Local Infection Source' unless Local Transmission is selected| +|Hide Test Result Field|Hide Test Result Field until Lab Test question is answered with yes| +|Hide Test Result Options|Hide Irrelevant Test Result Options| +|Hide Unknown Options|Hide Irrelevant Unknown Options| + +You can read more about program rules here: + +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +From the data captured in the COVID-19 line-listing program, we can calculate the following indicators, including those recommended by the WHO for daily and weekly reporting, present them in a dashboard. All COVID-19 program indicators based on the event program are assigned to the Program Indicator Group ‘COVID-19 Events.’ + +||| +|--|--| +|COVID-19 - Cases admitted in intensive care unit (ICU)|COVID-19 Cases admitted in intensive care unit (ICU)| +|COVID-19 - Cases exposed through healthcare facility|Cases where infection is suspected to have occurred in a health care setting| +|COVID-19 - Cases infected by community transmission|Cases where infection is suspected to have occurred through community spread| +|COVID-19 - Cases infected by household transmission|Cases where infection is suspected to have occurred within the household| +|COVID-19 - Cases infected by local transmission|Cases where infection is suspected to have occurred locally, not in another country| +|COVID-19 - Cases infected through other contact with other infected individual|Cases where infection is suspected to have occurred through other close contact with an infected individual (excluding those listed: household, known cluster, HCF)| +|COVID-19 - Cases linked to known cluster|Cases where infection is suspected to have occurred by linkage to a known cluster of cases| +|COVID-19 - Cases with unknown exposure|Cases where source of infection or exposure is unknown| +|COVID-19 - Deaths|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 - Confirmed Hospitalised Cases|Number of confirmed cases that were admitted into hospital| +|COVID-19 - Imported Cases|Cases where likely source of infection is recorded as another country or imported from another country.| +|COVID-19 - Laboratory confirmed cases|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by report date| +|COVID-19 - Laboratory confirmed cases - by onset of symptoms|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by date of onset of symptoms| +|COVID-19 - Laboratory tested cases|Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)| +|COVID-19 - Probable cases|Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date| +|COVID-19 - Probable cases - by onset of symptoms|Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms| +|COVID-19 - Recovered cases|Number of cases that are recovered (By date of onset of symptoms)| +|COVID-19 - Suspected cases|Total number of cases suspected with COVID-19, by report date| +|COVID-19 - Suspected cases - by onset of symptoms|Total number of cases suspected with COVID-19, by date of onset of symptoms| +|COVID-19 - Suspected cases not tested|Total number of suspected cases without a lab result| +|COVID-19 Event - case fatality rate|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 Deaths by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Confirmed cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Suspected cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| + +## Referencias { #references } + +* [COVID-19 Surveillance, Response & Vaccine Delivery Toolkit](https://dhis2.org/covid-19) +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form +[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md new file mode 100644 index 00000000..0b72ba1e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md @@ -0,0 +1,13 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implementar +--- + +# COVID-19 Surveillance Events { #covid-19-surveillance-events } + +## Diseño { #design } + +[Version 0.3.2](#c19-evt-design) + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md new file mode 100644 index 00000000..d88e8be9 --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md @@ -0,0 +1,22 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_surveillance-digital_data_package-2022.md" +revision_date: '2023-09-01' +tags: +- Implementar +--- + +# COVID-19 Surveillance { #covid-19-surveillance } + +DHIS2 released a digital metadata package to accelerate case detection, situation reporting, active surveillance and response for COVID-19. The design is inspired by the Ministry of Health Sri Lanka’s pioneering use of DHIS2 tracker for COVID-19 case detection and draws on years of collaboration with the World Health Organisation (WHO) to develop information system standards for case-based disease surveillance. The COVID-19 digital data package includes standard metadata aligned with the WHO’s [technical guidance on COVID-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and implementation guidance to enable rapid deployment in countries. + +The design of these modules can be adapted, modified and reused for new and emerging infectious disease threats to strengthen health emergency preparedness and response systems in countries. + +## COVID-19 Surveillance Modules { #covid-19-surveillance-modules } + +DHIS2 supports surveillance workflows and automated analysis for key components of routine and active surveillance: + +* **COVID-19 Case Surveillance tracker**: enrolls & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. +* **Contact Registration & Follow-up tracker**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. +* **Ports of Entry Screening & Follow-up tracker**: enrols travellers who have visited high-risk locations at Ports of Entry for 14-day monitoring and follow-up. +* **COVID-19 Aggregate Situation Reports**: an aggregate reporting dataset that captures minimum necessary data points for daily or weekly reporting and includes key information for generating situation reports. + diff --git a/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..57a3fb4e --- /dev/null +++ b/projects/docs-full-site/es_419/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md index e67d331e..0441c9cb 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.3/ReleaseNote-2.3.0.md" revision_date: '2020-11-03' tags: -- DHIS core version 2.35 - Android app version 2.3.0 - Implementar +- DHIS core version 2.35 --- # DHIS2 Android App version 2.3 Release Note { #dhis2-android-app-version-23-release-note } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md index 45be5f0a..33ee35b9 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.4/ReleaseNote-2.4.0.md" revision_date: '2021-04-27' tags: -- Android app version 2.4.0 -- DHIS core version 2.36 - Implementar +- DHIS core version 2.36 +- Android app version 2.4.0 --- # DHIS2 Android App version 2.4 Release Notes { #dhis2-android-app-version-24-release-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md index 12f3da29..20cc0283 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.5/ReleaseNote-2.5.0.md" revision_date: '2021-11-24' tags: -- Android app version 2.5.0 - DHIS core version 2.37 - Implementar +- Android app version 2.5.0 --- # DHIS2 Android App version 2.5 Release Notes { #dhis2-android-app-version-25-release-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md index b28809a9..18293d51 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.6/ReleaseNote-2.6.0.md" revision_date: '2022-04-18' tags: +- Implementar - DHIS core version 2.38 - Android app version 2.6.0 -- Implementar --- # DHIS2 Android App version 2.6 Release Notes { #dhis2-android-app-version-26-release-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md index c000179f..bca0d65f 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.7/ReleaseNote-2.7.0.md" revision_date: '2023-05-11' tags: -- DHIS core version 2.39 - Android app version 2.7.0 - Implementar +- DHIS core version 2.39 --- # DHIS2 Android App version 2.7 Release Notes { #dhis2-android-app-version-27-release-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md index 98dd07be..56e0fb60 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.8/ReleaseNote-2.8.0.md" revision_date: '2023-05-08' tags: -- DHIS core version 2.40 - Android app version 2.8.0 - Implementar +- DHIS core version 2.40 --- # DHIS2 Android App version 2.8 Release Notes { #dhis2-android-app-version-28-release-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md index 4faf2c7a..107b9f63 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/2.9/android-releases/2.9/ReleaseNote-2.9.0.md" revision_date: '2023-11-20' tags: -- DHIS core version 2.40 -- Android app version 2.9.0 - Implementar +- Android app version 2.9.0 +- DHIS core version 2.40 --- # DHIS2 Android App version 2.9 Release Notes { #dhis2-android-app-version-29-release-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md index 03bc7913..94fd244d 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/ReleaseNote-2.35.0.md" revision_date: '2020-10-22' tags: -- DHIS core version 2.35 - Implementar +- DHIS core version 2.35 --- # DHIS version 2.35 Release Note { #dhis-version-235-release-note } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md index 04b93294..35865646 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.35 - Implementar +- DHIS core version 2.35 --- # 2.35 Upgrade Notes { #235-upgrade-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md index 733a02b1..0da8781c 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/ReleaseNote-2.36.md" revision_date: '2021-10-27' tags: -- DHIS core version 2.36 - Implementar +- DHIS core version 2.36 --- # DHIS version 2.36 Release Note { #dhis-version-236-release-note } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md index 7a66236a..a2d79b34 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.36 - Implementar +- DHIS core version 2.36 --- # 2.36 Upgrade Notes { #236-upgrade-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md index a12fe709..0dc149ee 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/ReleaseNote-2.38.md" revision_date: '2022-10-12' tags: -- DHIS core version 2.38 - Implementar +- DHIS core version 2.38 --- # DHIS version 2.38 Release Note { #dhis-version-238-release-note } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md index 28dfa515..2ce81038 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.38 - Implementar +- DHIS core version 2.38 --- # 2.38 Upgrade Notes { #238-upgrade-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md index 2da82f13..ae65667b 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/ReleaseNote-2.39.md" revision_date: '2023-01-26' tags: -- DHIS core version 2.39 - Implementar +- DHIS core version 2.39 --- # DHIS version 2.39 Release Note { #dhis-version-239-release-note } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md index 15a4957c..a3fa8aae 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.39 - Implementar +- DHIS core version 2.39 --- # 2.39 Upgrade Notes { #239-upgrade-notes } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md index 953b1e7f..7cead5ba 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/ReleaseNote-2.40.md" revision_date: '2023-05-12' tags: -- DHIS core version 2.40 - Implementar +- DHIS core version 2.40 --- # DHIS2 version 40 Release Note { #dhis2-version-40-release-note } diff --git a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md index 53159870..9e5fa8ff 100644 --- a/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md +++ b/projects/docs-full-site/es_419/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.40 - Implementar +- DHIS core version 2.40 --- # 2.40 Upgrade Notes { #240-upgrade-notes } 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 f802c8a9..a7461778 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 97bd0d27..fa2a934e 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 } 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 d0a24dbd..0e82eb18 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 5f18d07c..e3a4178f 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 b6c97839..09fd0071 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 f10bf807..a2b3120b 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 41a2d101..57da9f8e 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,8 +2,8 @@ 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 } 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 e0c7f25f..67cd3c89 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 } 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 3c08c5d7..285a5223 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 4b46a40e..9b69a893 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 bf5bb113..3689506d 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 b33fe2e5..49343282 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 2c80b95f..b5c43993 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,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: -- Gestionar - DHIS core version 2.41 +- Gestionar --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } 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 7c418a8e..1bccc374 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 } 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 50df2877..a025838e 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 fe6838db..f5d7597d 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 80389d2c..8464e7dc 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 fd1b0cc2..b6738798 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 8b64615b..3646f6a8 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,8 +2,8 @@ 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 } 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 ff81c086..364e7cd0 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 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index ef19e985..68a96235 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/es_419/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: -- Gestionar - DHIS core version master +- Gestionar --- # Monitoring { #monitoring } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index 0636518b..bc28984a 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/es_419/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: -- Gestionar - DHIS core version master +- Gestionar --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index d0f802b8..0bea08d7 100644 --- a/projects/docs-full-site/es_419/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/es_419/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: -- Gestionar - DHIS core version master +- Gestionar --- # Using Gateways for SMS reporting { #sms_report_sending } diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__DESIGN__hiv-logistics-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__DESIGN__hiv-logistics-md index 8f682a1d..ecfab19d 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__DESIGN__hiv-logistics-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-110__DESIGN__hiv-logistics-md @@ -8,7 +8,7 @@ tags: # HIV logistics { #hiv-agg-stk-design } -## HIV logistics design { #hiv-logistics-design } +## VIH diseño de logística { #hiv-logistics-design } Los metadatos de logística están diseñados para armonizarse conceptualmente entre diferentes programas de salud. Para facilitar la adopción de estos paquetes en los países, hemos incluido los metadatos específicos del programa en los metadatos existentes de DHIS2 para programas de VIH. Por lo tanto, el paquete HMIS agregado para el VIH incluye: diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-120__DESIGN__hiv-logistics-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-120__DESIGN__hiv-logistics-md index 886c8cb2..0c8a7c5a 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-120__DESIGN__hiv-logistics-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-120__DESIGN__hiv-logistics-md @@ -5,7 +5,7 @@ revision_date: "2022-11-11" # HIV logistics { #hiv-agg-stk-design } -## HIV logistics design { #hiv-logistics-design } +## VIH diseño de logística { #hiv-logistics-design } Los metadatos de logística están diseñados para armonizarse conceptualmente entre diferentes programas de salud. Para facilitar la adopción de estos paquetes en los países, hemos incluido los metadatos específicos del programa en los metadatos existentes de DHIS2 para programas de VIH. Por lo tanto, el paquete HMIS agregado para el VIH incluye: diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-121__DESIGN__hiv-logistics-md b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-121__DESIGN__hiv-logistics-md index a83f3efb..f97c3d4d 100644 --- a/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-121__DESIGN__hiv-logistics-md +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__HIV__HIV-HMIS__VERSION-121__DESIGN__hiv-logistics-md @@ -8,7 +8,7 @@ tags: # HIV logistics { #hiv-agg-stk-design } -## HIV logistics design { #hiv-logistics-design } +## VIH diseño de logística { #hiv-logistics-design } Los metadatos de logística están diseñados para armonizarse conceptualmente entre diferentes programas de salud. Para facilitar la adopción de estos paquetes en los países, hemos incluido los metadatos específicos del programa en los metadatos existentes de DHIS2 para programas de VIH. Por lo tanto, el paquete HMIS agregado para el VIH incluye: diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-AGGREGATE__VERSION-121__data-quality-dashboard-design-md b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-AGGREGATE__VERSION-121__data-quality-dashboard-design-md new file mode 100644 index 00000000..2625b49a --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-AGGREGATE__VERSION-121__data-quality-dashboard-design-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/MAL_AGG/blob/master/docs/mal_agg_dq-design.md" +revision_date: "2022-06-09" +--- + +# Malaria Data Quality Dashboard { #malaria-data-quality-dashboard } + +## Introducción { #introduction } + +The WHO Malaria Data Quality (DQ) dashboard is an addendum to the [malaria burden reduction aggregate package](https://dhis2.org/who-package-downloads/#malaria). Like all the aggregate packages, this has been developed as an installable solution for countries to update their DHIS2-based HMIS, specifically the malaria aggregate indicators and dashboard. + +This chapter provides an overview of the design principles that have been applied within the core DHIS2 features for monitoring and improvement of data quality through DHIS2 dashboards. This dashboard complements other DHIS2 apps and tools such as the [WHO Data Quality App for DHIS2](https://docs.dhis2.org/en/use/optional-apps/who-data-quality-tool/installation-and-configuration.html). This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localization of the package and this package can be adapted to local needs and national guidelines. + +The objectives of the data quality dashboard are to: + +1. Bring key data quality metrics to the users routinely through use of DHIS2 dashboards to facilitate data quality improvement activities; +2. Monitor completeness and timeliness of reporting malaria data; +3. Monitor completeness of reporting of core malaria data variables in the monthly health facility reporting form; +4. Monitor internal consistency between variables to detect inconsistencies for quality improvements; +5. Compare trends of key malaria indicators at the various reporting levels and rapidly detect anomalies as red flags for poor data quality. + +The system design builds upon existing malaria aggregate guidelines principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. It is important to note that national guidelines and policies may vary and therefore it is recommended to adapt this package to local contexts. + +## Design Summary { #design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://who.dhis2.org/documentation/general_design_principles.html) and a common [naming convention](https://who.dhis2.org/documentation/naming_convention.html). + +The malaria Data Quality dashboard includes: + +1. Indicators: data quality indicators and other relevant indicators borrowed from malaria burden reduction package.. +2. Visualizations/analytic items: charts and pivot tables to visualize indicator performance +3. Dashboard: designed to present the visuals/analytic items (charts and tables) in a logical way to users + +Like all dashboard packages for DHIS2, the data visualizations are configured to display data for the organisation units for which the user has data capture access in the user configuration. In this way, the dashboard can be used at national, district or other sub-national levels to monitor data quality for the geographic area most relevant to the user. This enables actions to improve data quality to be taken as close to the point of data collection and validation as possible. Configuration of users and assignment to user groups to be able to access the dashboard should be considered within country context to ensure access is provided properly to users. + +### Intended users { #intended-users } + +- Health facility users: monitor completeness and consistency of data reported from the facility, which could support onsite data reviews, checking for data quality errors and cleaning for quality improvement (according to national policies & SOPs) +- District health managers: monitor data quality and detect facilities where data quality improvement may be needed; use the dashboard to provide feedback loops to facilities and plan data quality improvement follow-ups or other technical assistance activities +- National malaria program managers: monitor data quality and develop national data quality improvement plans; understand the potential biases in the routine data set to improve their ability to analyze routine malaria data and consider data quality limitations + +## Indicators { #indicators } + +Indicators are based on the data elements included in the WHO malaria burden reduction package for HMIS, which includes a monthly aggregate dataset. These indicators are used to develop dashboard items and all indicators are assigned to the indicator group "Malaria data quality". + +| name | Descripción | Numerator Description | Denominator Description | Indicator Type | Purpose | +| --- | --- | --- | --- | --- | --- | +| MAL - Reporting Completeness (%) | Number of actual reports received divided by total number of health facilities expected to report | Number of health facilities reported | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Reporting timeliness (%) | Number of actual reports received on time divided by total number of health facilities expected to report | Number of health facilities reported on time | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Confirmed malaria cases >/= Treated with 1st line courses | Confirmed malaria cases minus confirmed malaria cases treated with 1st line treatment courses (incl ACT) | Confirmed malaria cases - cases treated with 1st line tx | 1 | Numerator only | Consistency between variables | +| MAL - All cause deaths > Malaria inpatient deaths | All cause deaths minus malaria inpatient deaths | All cause deaths - Malaria inpatient deaths | 1 | Numerator only | Consistency between variables | +| MAL - All cause inpatients > Malaria inpatients | All cause inpatients minus malaria inpatients | All cause inpatients - Malaria inpatients | 1 | Numerator only | Consistency between variables | +| MAL - All cause outpatients > Total malaria cases | All cause outpatients minus total malaria cases | all cause outpatients - total malaria cases | 1 | Numerator only | Consistency between variables | +| MAL - Microscopy tested >/= Microscopy positive | Cases tested for malaria with Microscopy minus microscopy positive | Microscopy tested - Microscopy positive | 1 | Numerator only | Consistency between variables | +| MAL - RDT tested >/= RDT positive | Cases tested for malaria with RDT minus RDT positive | RDT tested - RDT positive | 1 | Numerator only | Consistency between variables | +| MAL - All malaria cases actual reported (%) | Count of reported total malaria cases (confirmed + presumed) divided by actual number of reports received multiplied by 100 | Total malaria cases (confirmed + presumed) | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause death actual reported (%) | Count of reported all-cause death divided by actual number of reports received multiplied by 100 | All-cause death | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause inpatient actual reported (%) | Count of reported all-cause inpatient divided by actual number of reports received multiplied by 100 | All-cause inpatient | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause outpatient cases actual reported (%) | Count of reported all-cause outpatient cases divided by actual number of reports received multiplied by 100 | All-cause outpatient cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Inpatient malaria cases actual reported (%) | Count of reported inpatient malaria cases divided by actual number of reports received multiplied by 100 | Inpatient malaria cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria confirmed cases actual reported (%) | Count of reported malaria confirmed cases divided by actual number of reports received multiplied by 100 | Malaria confirmed cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria deaths actual reported (%) | Count of reported malaria deaths divided by actual number of reports received multiplied by 100 | Malaria deaths | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy positive actual reported (%) | Count of reported microscopy positive divided by actual number of reports received multiplied by 100 | Microscopy positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy tested actual reported (%) | Count of reported microscopy tested divided by actual number of reports received multiplied by 100 | Microscopy tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT positive actual reported (%) | Count of reported RDT positive divided by actual number of reports received multiplied by 100 | RDT positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT tested actual reported (%) | Count of reported RDT tested divided by actual number of reports received multiplied by 100 | RDT tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Outpatient malaria cases (%) | Number of malaria outpatient divided by number of all outpatients multiplied by 100 | Outpatient malaria cases | All-cause outpatients | Porcentaje | Consistency of variable by trends | +| MAL - RDT positivity rate (%) | Number of malaria RDT positive cases divided by total RDT tests multiplied by 100 | Cases positive with RDT | Tested (RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Slide (microscopy) positivity rate (%) | Number of malaria microscopy positive cases divided by total microcopy tests multiplied by 100 | Cases positive with microscopy | Cases tested with microscopy | Porcentaje | Consistency of variable by trends | +| MAL - Inpatient malaria cases (%) | Number of malaria inpatients divided by number of all inpatients deaths multiplied by 100 | Inpatient malaria cases | All cause inpatients | Porcentaje | Consistency of variable by trends | +| MAL - Malaria inpatient deaths (%) | Number of Inpatient malaria deaths divided by number of all deaths at facility multiplied by 100 | Malaria deaths | death | Porcentaje | Consistency of variable by trends | +| MAL - Malaria test positivity rate (Micr+RDT) (%) | Total number of positive cases (Micr + RDT) divided by total number of tested (Micr + RDT) multiplied by 100 | Total positive cases (Micr + RDT) | Total tested (Micr + RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Suspected malaria cases tested (%) | Number of suspected cases tested with either microscopy or RDT divided by total number of suspected cases multiplied by 100 | Cases tested with microscopy + Cases tested with RDT | Suspected malaria cases | Porcentaje | Consistency of variable by trends | + +## Visualizations { #visualizations } + +For each of the indicators outlined above, visualization items have been created using tables and charts as shown below. This covers data quality analysis on completeness, timeliness and consistency of data and visualization. Color legends have also been used on pivot tables to show thresholds of performance with extremes of "red" and "green" flags to indicate low and high quality data respectively. These legends can be adapted by the country according to their own thresholds. + +### Chart 1: Reporting completeness { #chart-1-reporting-completeness } + +![Chart 1: Reporting completeness](resources/images/MALDQ1.png) + +### Table 1: Reporting completeness in public and private sector { #table-1-reporting-completeness-in-public-and-private-sector } + +![Table 1: Reporting completeness in public and private sector](resources/images/MALDQ2.png) + +### Chart 2: Reporting timeliness { #chart-2-reporting-timeliness } + +![Chart 2: Reporting timeliness](resources/images/MALDQ3.png) + +### Table 2: Reporting timeliness in private and public sector { #table-2-reporting-timeliness-in-private-and-public-sector } + +![Table 2: Reporting timeliness in private and public sector](resources/images/MALDQ4.png) + +### Table 3: Completeness of variable in actual reports { #table-3-completeness-of-variable-in-actual-reports } + +![Table 3: Completeness of variable in actual reports](resources/images/MALDQ5.png) + +### Table 4: Consistency between variables { #table-4-consistency-between-variables } + +![Table 4: Consistency between variables](resources/images/MALDQ6.png) + +### Chart 3: Proportion of outpatient malaria cases { #chart-3-proportion-of-outpatient-malaria-cases } + +![Chart 3: Proportion of outpatient malaria cases](resources/images/MALDQ7.png) + +### Chart 4: Proportion of inpatient malaria cases { #chart-4-proportion-of-inpatient-malaria-cases } + +![Chart 4: Proportion of inpatient malaria cases](resources/images/MALDQ8.png) + +### Chart 5: Proportion of inpatient deaths { #chart-5-proportion-of-inpatient-deaths } + +![Chart 5: Proportion of inpatient deaths](resources/images/MALDQ9.png) + +### Chart 6: Test positivity rate { #chart-6-test-positivity-rate } + +![Chart 6: Test positivity rate](resources/images/MALDQ10.png) + +### Chart 7: Slide positivity rate { #chart-7-slide-positivity-rate } + +![Chart 7: Slide positivity rate](resources/images/MALDQ11.png) + +### Chart 8: RDT positivity rate { #chart-8-rdt-positivity-rate } + +![Chart 8: RDT positivity rate](resources/images/MALDQ12.png) + +### Chart 9: Proportion of suspected individuals tested { #chart-9-proportion-of-suspected-individuals-tested } + +![Chart 9: Proportion of suspected individuals tested](resources/images/MALDQ13.png) + +## Dashboard { #dashboard } + +All data visualization items created have been configured on a single dashboard named 'Malaria Data Quality' and below is a snapshot of the dashboard with some of the items as displayed. By default, the Malaria Data Quality dashboard within the package is configured to be shared with the User Group 'Malaria access', which is the same user group used to provide access to dashboards in the Burden Reduction package. + +![Malaria Data Quality Dashboard](resources/images/MALDQ14.png) diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-AGGREGATE__VERSION-200__data-quality-dashboard-design-md b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-AGGREGATE__VERSION-200__data-quality-dashboard-design-md new file mode 100644 index 00000000..2625b49a --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-AGGREGATE__VERSION-200__data-quality-dashboard-design-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/MAL_AGG/blob/master/docs/mal_agg_dq-design.md" +revision_date: "2022-06-09" +--- + +# Malaria Data Quality Dashboard { #malaria-data-quality-dashboard } + +## Introducción { #introduction } + +The WHO Malaria Data Quality (DQ) dashboard is an addendum to the [malaria burden reduction aggregate package](https://dhis2.org/who-package-downloads/#malaria). Like all the aggregate packages, this has been developed as an installable solution for countries to update their DHIS2-based HMIS, specifically the malaria aggregate indicators and dashboard. + +This chapter provides an overview of the design principles that have been applied within the core DHIS2 features for monitoring and improvement of data quality through DHIS2 dashboards. This dashboard complements other DHIS2 apps and tools such as the [WHO Data Quality App for DHIS2](https://docs.dhis2.org/en/use/optional-apps/who-data-quality-tool/installation-and-configuration.html). This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localization of the package and this package can be adapted to local needs and national guidelines. + +The objectives of the data quality dashboard are to: + +1. Bring key data quality metrics to the users routinely through use of DHIS2 dashboards to facilitate data quality improvement activities; +2. Monitor completeness and timeliness of reporting malaria data; +3. Monitor completeness of reporting of core malaria data variables in the monthly health facility reporting form; +4. Monitor internal consistency between variables to detect inconsistencies for quality improvements; +5. Compare trends of key malaria indicators at the various reporting levels and rapidly detect anomalies as red flags for poor data quality. + +The system design builds upon existing malaria aggregate guidelines principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. It is important to note that national guidelines and policies may vary and therefore it is recommended to adapt this package to local contexts. + +## Design Summary { #design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://who.dhis2.org/documentation/general_design_principles.html) and a common [naming convention](https://who.dhis2.org/documentation/naming_convention.html). + +The malaria Data Quality dashboard includes: + +1. Indicators: data quality indicators and other relevant indicators borrowed from malaria burden reduction package.. +2. Visualizations/analytic items: charts and pivot tables to visualize indicator performance +3. Dashboard: designed to present the visuals/analytic items (charts and tables) in a logical way to users + +Like all dashboard packages for DHIS2, the data visualizations are configured to display data for the organisation units for which the user has data capture access in the user configuration. In this way, the dashboard can be used at national, district or other sub-national levels to monitor data quality for the geographic area most relevant to the user. This enables actions to improve data quality to be taken as close to the point of data collection and validation as possible. Configuration of users and assignment to user groups to be able to access the dashboard should be considered within country context to ensure access is provided properly to users. + +### Intended users { #intended-users } + +- Health facility users: monitor completeness and consistency of data reported from the facility, which could support onsite data reviews, checking for data quality errors and cleaning for quality improvement (according to national policies & SOPs) +- District health managers: monitor data quality and detect facilities where data quality improvement may be needed; use the dashboard to provide feedback loops to facilities and plan data quality improvement follow-ups or other technical assistance activities +- National malaria program managers: monitor data quality and develop national data quality improvement plans; understand the potential biases in the routine data set to improve their ability to analyze routine malaria data and consider data quality limitations + +## Indicators { #indicators } + +Indicators are based on the data elements included in the WHO malaria burden reduction package for HMIS, which includes a monthly aggregate dataset. These indicators are used to develop dashboard items and all indicators are assigned to the indicator group "Malaria data quality". + +| name | Descripción | Numerator Description | Denominator Description | Indicator Type | Purpose | +| --- | --- | --- | --- | --- | --- | +| MAL - Reporting Completeness (%) | Number of actual reports received divided by total number of health facilities expected to report | Number of health facilities reported | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Reporting timeliness (%) | Number of actual reports received on time divided by total number of health facilities expected to report | Number of health facilities reported on time | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Confirmed malaria cases >/= Treated with 1st line courses | Confirmed malaria cases minus confirmed malaria cases treated with 1st line treatment courses (incl ACT) | Confirmed malaria cases - cases treated with 1st line tx | 1 | Numerator only | Consistency between variables | +| MAL - All cause deaths > Malaria inpatient deaths | All cause deaths minus malaria inpatient deaths | All cause deaths - Malaria inpatient deaths | 1 | Numerator only | Consistency between variables | +| MAL - All cause inpatients > Malaria inpatients | All cause inpatients minus malaria inpatients | All cause inpatients - Malaria inpatients | 1 | Numerator only | Consistency between variables | +| MAL - All cause outpatients > Total malaria cases | All cause outpatients minus total malaria cases | all cause outpatients - total malaria cases | 1 | Numerator only | Consistency between variables | +| MAL - Microscopy tested >/= Microscopy positive | Cases tested for malaria with Microscopy minus microscopy positive | Microscopy tested - Microscopy positive | 1 | Numerator only | Consistency between variables | +| MAL - RDT tested >/= RDT positive | Cases tested for malaria with RDT minus RDT positive | RDT tested - RDT positive | 1 | Numerator only | Consistency between variables | +| MAL - All malaria cases actual reported (%) | Count of reported total malaria cases (confirmed + presumed) divided by actual number of reports received multiplied by 100 | Total malaria cases (confirmed + presumed) | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause death actual reported (%) | Count of reported all-cause death divided by actual number of reports received multiplied by 100 | All-cause death | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause inpatient actual reported (%) | Count of reported all-cause inpatient divided by actual number of reports received multiplied by 100 | All-cause inpatient | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause outpatient cases actual reported (%) | Count of reported all-cause outpatient cases divided by actual number of reports received multiplied by 100 | All-cause outpatient cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Inpatient malaria cases actual reported (%) | Count of reported inpatient malaria cases divided by actual number of reports received multiplied by 100 | Inpatient malaria cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria confirmed cases actual reported (%) | Count of reported malaria confirmed cases divided by actual number of reports received multiplied by 100 | Malaria confirmed cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria deaths actual reported (%) | Count of reported malaria deaths divided by actual number of reports received multiplied by 100 | Malaria deaths | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy positive actual reported (%) | Count of reported microscopy positive divided by actual number of reports received multiplied by 100 | Microscopy positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy tested actual reported (%) | Count of reported microscopy tested divided by actual number of reports received multiplied by 100 | Microscopy tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT positive actual reported (%) | Count of reported RDT positive divided by actual number of reports received multiplied by 100 | RDT positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT tested actual reported (%) | Count of reported RDT tested divided by actual number of reports received multiplied by 100 | RDT tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Outpatient malaria cases (%) | Number of malaria outpatient divided by number of all outpatients multiplied by 100 | Outpatient malaria cases | All-cause outpatients | Porcentaje | Consistency of variable by trends | +| MAL - RDT positivity rate (%) | Number of malaria RDT positive cases divided by total RDT tests multiplied by 100 | Cases positive with RDT | Tested (RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Slide (microscopy) positivity rate (%) | Number of malaria microscopy positive cases divided by total microcopy tests multiplied by 100 | Cases positive with microscopy | Cases tested with microscopy | Porcentaje | Consistency of variable by trends | +| MAL - Inpatient malaria cases (%) | Number of malaria inpatients divided by number of all inpatients deaths multiplied by 100 | Inpatient malaria cases | All cause inpatients | Porcentaje | Consistency of variable by trends | +| MAL - Malaria inpatient deaths (%) | Number of Inpatient malaria deaths divided by number of all deaths at facility multiplied by 100 | Malaria deaths | death | Porcentaje | Consistency of variable by trends | +| MAL - Malaria test positivity rate (Micr+RDT) (%) | Total number of positive cases (Micr + RDT) divided by total number of tested (Micr + RDT) multiplied by 100 | Total positive cases (Micr + RDT) | Total tested (Micr + RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Suspected malaria cases tested (%) | Number of suspected cases tested with either microscopy or RDT divided by total number of suspected cases multiplied by 100 | Cases tested with microscopy + Cases tested with RDT | Suspected malaria cases | Porcentaje | Consistency of variable by trends | + +## Visualizations { #visualizations } + +For each of the indicators outlined above, visualization items have been created using tables and charts as shown below. This covers data quality analysis on completeness, timeliness and consistency of data and visualization. Color legends have also been used on pivot tables to show thresholds of performance with extremes of "red" and "green" flags to indicate low and high quality data respectively. These legends can be adapted by the country according to their own thresholds. + +### Chart 1: Reporting completeness { #chart-1-reporting-completeness } + +![Chart 1: Reporting completeness](resources/images/MALDQ1.png) + +### Table 1: Reporting completeness in public and private sector { #table-1-reporting-completeness-in-public-and-private-sector } + +![Table 1: Reporting completeness in public and private sector](resources/images/MALDQ2.png) + +### Chart 2: Reporting timeliness { #chart-2-reporting-timeliness } + +![Chart 2: Reporting timeliness](resources/images/MALDQ3.png) + +### Table 2: Reporting timeliness in private and public sector { #table-2-reporting-timeliness-in-private-and-public-sector } + +![Table 2: Reporting timeliness in private and public sector](resources/images/MALDQ4.png) + +### Table 3: Completeness of variable in actual reports { #table-3-completeness-of-variable-in-actual-reports } + +![Table 3: Completeness of variable in actual reports](resources/images/MALDQ5.png) + +### Table 4: Consistency between variables { #table-4-consistency-between-variables } + +![Table 4: Consistency between variables](resources/images/MALDQ6.png) + +### Chart 3: Proportion of outpatient malaria cases { #chart-3-proportion-of-outpatient-malaria-cases } + +![Chart 3: Proportion of outpatient malaria cases](resources/images/MALDQ7.png) + +### Chart 4: Proportion of inpatient malaria cases { #chart-4-proportion-of-inpatient-malaria-cases } + +![Chart 4: Proportion of inpatient malaria cases](resources/images/MALDQ8.png) + +### Chart 5: Proportion of inpatient deaths { #chart-5-proportion-of-inpatient-deaths } + +![Chart 5: Proportion of inpatient deaths](resources/images/MALDQ9.png) + +### Chart 6: Test positivity rate { #chart-6-test-positivity-rate } + +![Chart 6: Test positivity rate](resources/images/MALDQ10.png) + +### Chart 7: Slide positivity rate { #chart-7-slide-positivity-rate } + +![Chart 7: Slide positivity rate](resources/images/MALDQ11.png) + +### Chart 8: RDT positivity rate { #chart-8-rdt-positivity-rate } + +![Chart 8: RDT positivity rate](resources/images/MALDQ12.png) + +### Chart 9: Proportion of suspected individuals tested { #chart-9-proportion-of-suspected-individuals-tested } + +![Chart 9: Proportion of suspected individuals tested](resources/images/MALDQ13.png) + +## Dashboard { #dashboard } + +All data visualization items created have been configured on a single dashboard named 'Malaria Data Quality' and below is a snapshot of the dashboard with some of the items as displayed. By default, the Malaria Data Quality dashboard within the package is configured to be shared with the User Group 'Malaria access', which is the same user group used to provide access to dashboards in the Burden Reduction package. + +![Malaria Data Quality Dashboard](resources/images/MALDQ14.png) diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-HMIS__VERSION-121__data-quality-dashboard-design-md b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-HMIS__VERSION-121__data-quality-dashboard-design-md new file mode 100644 index 00000000..2625b49a --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-HMIS__VERSION-121__data-quality-dashboard-design-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/MAL_AGG/blob/master/docs/mal_agg_dq-design.md" +revision_date: "2022-06-09" +--- + +# Malaria Data Quality Dashboard { #malaria-data-quality-dashboard } + +## Introducción { #introduction } + +The WHO Malaria Data Quality (DQ) dashboard is an addendum to the [malaria burden reduction aggregate package](https://dhis2.org/who-package-downloads/#malaria). Like all the aggregate packages, this has been developed as an installable solution for countries to update their DHIS2-based HMIS, specifically the malaria aggregate indicators and dashboard. + +This chapter provides an overview of the design principles that have been applied within the core DHIS2 features for monitoring and improvement of data quality through DHIS2 dashboards. This dashboard complements other DHIS2 apps and tools such as the [WHO Data Quality App for DHIS2](https://docs.dhis2.org/en/use/optional-apps/who-data-quality-tool/installation-and-configuration.html). This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localization of the package and this package can be adapted to local needs and national guidelines. + +The objectives of the data quality dashboard are to: + +1. Bring key data quality metrics to the users routinely through use of DHIS2 dashboards to facilitate data quality improvement activities; +2. Monitor completeness and timeliness of reporting malaria data; +3. Monitor completeness of reporting of core malaria data variables in the monthly health facility reporting form; +4. Monitor internal consistency between variables to detect inconsistencies for quality improvements; +5. Compare trends of key malaria indicators at the various reporting levels and rapidly detect anomalies as red flags for poor data quality. + +The system design builds upon existing malaria aggregate guidelines principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. It is important to note that national guidelines and policies may vary and therefore it is recommended to adapt this package to local contexts. + +## Design Summary { #design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://who.dhis2.org/documentation/general_design_principles.html) and a common [naming convention](https://who.dhis2.org/documentation/naming_convention.html). + +The malaria Data Quality dashboard includes: + +1. Indicators: data quality indicators and other relevant indicators borrowed from malaria burden reduction package.. +2. Visualizations/analytic items: charts and pivot tables to visualize indicator performance +3. Dashboard: designed to present the visuals/analytic items (charts and tables) in a logical way to users + +Like all dashboard packages for DHIS2, the data visualizations are configured to display data for the organisation units for which the user has data capture access in the user configuration. In this way, the dashboard can be used at national, district or other sub-national levels to monitor data quality for the geographic area most relevant to the user. This enables actions to improve data quality to be taken as close to the point of data collection and validation as possible. Configuration of users and assignment to user groups to be able to access the dashboard should be considered within country context to ensure access is provided properly to users. + +### Intended users { #intended-users } + +- Health facility users: monitor completeness and consistency of data reported from the facility, which could support onsite data reviews, checking for data quality errors and cleaning for quality improvement (according to national policies & SOPs) +- District health managers: monitor data quality and detect facilities where data quality improvement may be needed; use the dashboard to provide feedback loops to facilities and plan data quality improvement follow-ups or other technical assistance activities +- National malaria program managers: monitor data quality and develop national data quality improvement plans; understand the potential biases in the routine data set to improve their ability to analyze routine malaria data and consider data quality limitations + +## Indicators { #indicators } + +Indicators are based on the data elements included in the WHO malaria burden reduction package for HMIS, which includes a monthly aggregate dataset. These indicators are used to develop dashboard items and all indicators are assigned to the indicator group "Malaria data quality". + +| name | Descripción | Numerator Description | Denominator Description | Indicator Type | Purpose | +| --- | --- | --- | --- | --- | --- | +| MAL - Reporting Completeness (%) | Number of actual reports received divided by total number of health facilities expected to report | Number of health facilities reported | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Reporting timeliness (%) | Number of actual reports received on time divided by total number of health facilities expected to report | Number of health facilities reported on time | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Confirmed malaria cases >/= Treated with 1st line courses | Confirmed malaria cases minus confirmed malaria cases treated with 1st line treatment courses (incl ACT) | Confirmed malaria cases - cases treated with 1st line tx | 1 | Numerator only | Consistency between variables | +| MAL - All cause deaths > Malaria inpatient deaths | All cause deaths minus malaria inpatient deaths | All cause deaths - Malaria inpatient deaths | 1 | Numerator only | Consistency between variables | +| MAL - All cause inpatients > Malaria inpatients | All cause inpatients minus malaria inpatients | All cause inpatients - Malaria inpatients | 1 | Numerator only | Consistency between variables | +| MAL - All cause outpatients > Total malaria cases | All cause outpatients minus total malaria cases | all cause outpatients - total malaria cases | 1 | Numerator only | Consistency between variables | +| MAL - Microscopy tested >/= Microscopy positive | Cases tested for malaria with Microscopy minus microscopy positive | Microscopy tested - Microscopy positive | 1 | Numerator only | Consistency between variables | +| MAL - RDT tested >/= RDT positive | Cases tested for malaria with RDT minus RDT positive | RDT tested - RDT positive | 1 | Numerator only | Consistency between variables | +| MAL - All malaria cases actual reported (%) | Count of reported total malaria cases (confirmed + presumed) divided by actual number of reports received multiplied by 100 | Total malaria cases (confirmed + presumed) | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause death actual reported (%) | Count of reported all-cause death divided by actual number of reports received multiplied by 100 | All-cause death | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause inpatient actual reported (%) | Count of reported all-cause inpatient divided by actual number of reports received multiplied by 100 | All-cause inpatient | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause outpatient cases actual reported (%) | Count of reported all-cause outpatient cases divided by actual number of reports received multiplied by 100 | All-cause outpatient cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Inpatient malaria cases actual reported (%) | Count of reported inpatient malaria cases divided by actual number of reports received multiplied by 100 | Inpatient malaria cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria confirmed cases actual reported (%) | Count of reported malaria confirmed cases divided by actual number of reports received multiplied by 100 | Malaria confirmed cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria deaths actual reported (%) | Count of reported malaria deaths divided by actual number of reports received multiplied by 100 | Malaria deaths | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy positive actual reported (%) | Count of reported microscopy positive divided by actual number of reports received multiplied by 100 | Microscopy positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy tested actual reported (%) | Count of reported microscopy tested divided by actual number of reports received multiplied by 100 | Microscopy tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT positive actual reported (%) | Count of reported RDT positive divided by actual number of reports received multiplied by 100 | RDT positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT tested actual reported (%) | Count of reported RDT tested divided by actual number of reports received multiplied by 100 | RDT tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Outpatient malaria cases (%) | Number of malaria outpatient divided by number of all outpatients multiplied by 100 | Outpatient malaria cases | All-cause outpatients | Porcentaje | Consistency of variable by trends | +| MAL - RDT positivity rate (%) | Number of malaria RDT positive cases divided by total RDT tests multiplied by 100 | Cases positive with RDT | Tested (RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Slide (microscopy) positivity rate (%) | Number of malaria microscopy positive cases divided by total microcopy tests multiplied by 100 | Cases positive with microscopy | Cases tested with microscopy | Porcentaje | Consistency of variable by trends | +| MAL - Inpatient malaria cases (%) | Number of malaria inpatients divided by number of all inpatients deaths multiplied by 100 | Inpatient malaria cases | All cause inpatients | Porcentaje | Consistency of variable by trends | +| MAL - Malaria inpatient deaths (%) | Number of Inpatient malaria deaths divided by number of all deaths at facility multiplied by 100 | Malaria deaths | death | Porcentaje | Consistency of variable by trends | +| MAL - Malaria test positivity rate (Micr+RDT) (%) | Total number of positive cases (Micr + RDT) divided by total number of tested (Micr + RDT) multiplied by 100 | Total positive cases (Micr + RDT) | Total tested (Micr + RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Suspected malaria cases tested (%) | Number of suspected cases tested with either microscopy or RDT divided by total number of suspected cases multiplied by 100 | Cases tested with microscopy + Cases tested with RDT | Suspected malaria cases | Porcentaje | Consistency of variable by trends | + +## Visualizations { #visualizations } + +For each of the indicators outlined above, visualization items have been created using tables and charts as shown below. This covers data quality analysis on completeness, timeliness and consistency of data and visualization. Color legends have also been used on pivot tables to show thresholds of performance with extremes of "red" and "green" flags to indicate low and high quality data respectively. These legends can be adapted by the country according to their own thresholds. + +### Chart 1: Reporting completeness { #chart-1-reporting-completeness } + +![Chart 1: Reporting completeness](resources/images/MALDQ1.png) + +### Table 1: Reporting completeness in public and private sector { #table-1-reporting-completeness-in-public-and-private-sector } + +![Table 1: Reporting completeness in public and private sector](resources/images/MALDQ2.png) + +### Chart 2: Reporting timeliness { #chart-2-reporting-timeliness } + +![Chart 2: Reporting timeliness](resources/images/MALDQ3.png) + +### Table 2: Reporting timeliness in private and public sector { #table-2-reporting-timeliness-in-private-and-public-sector } + +![Table 2: Reporting timeliness in private and public sector](resources/images/MALDQ4.png) + +### Table 3: Completeness of variable in actual reports { #table-3-completeness-of-variable-in-actual-reports } + +![Table 3: Completeness of variable in actual reports](resources/images/MALDQ5.png) + +### Table 4: Consistency between variables { #table-4-consistency-between-variables } + +![Table 4: Consistency between variables](resources/images/MALDQ6.png) + +### Chart 3: Proportion of outpatient malaria cases { #chart-3-proportion-of-outpatient-malaria-cases } + +![Chart 3: Proportion of outpatient malaria cases](resources/images/MALDQ7.png) + +### Chart 4: Proportion of inpatient malaria cases { #chart-4-proportion-of-inpatient-malaria-cases } + +![Chart 4: Proportion of inpatient malaria cases](resources/images/MALDQ8.png) + +### Chart 5: Proportion of inpatient deaths { #chart-5-proportion-of-inpatient-deaths } + +![Chart 5: Proportion of inpatient deaths](resources/images/MALDQ9.png) + +### Chart 6: Test positivity rate { #chart-6-test-positivity-rate } + +![Chart 6: Test positivity rate](resources/images/MALDQ10.png) + +### Chart 7: Slide positivity rate { #chart-7-slide-positivity-rate } + +![Chart 7: Slide positivity rate](resources/images/MALDQ11.png) + +### Chart 8: RDT positivity rate { #chart-8-rdt-positivity-rate } + +![Chart 8: RDT positivity rate](resources/images/MALDQ12.png) + +### Chart 9: Proportion of suspected individuals tested { #chart-9-proportion-of-suspected-individuals-tested } + +![Chart 9: Proportion of suspected individuals tested](resources/images/MALDQ13.png) + +## Dashboard { #dashboard } + +All data visualization items created have been configured on a single dashboard named 'Malaria Data Quality' and below is a snapshot of the dashboard with some of the items as displayed. By default, the Malaria Data Quality dashboard within the package is configured to be shared with the User Group 'Malaria access', which is the same user group used to provide access to dashboards in the Burden Reduction package. + +![Malaria Data Quality Dashboard](resources/images/MALDQ14.png) diff --git a/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-HMIS__VERSION-200__data-quality-dashboard-design-md b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-HMIS__VERSION-200__data-quality-dashboard-design-md new file mode 100644 index 00000000..2625b49a --- /dev/null +++ b/projects/docs-full-site/es_419/TOPICS__METADATA__MALARIA__MALARIA-HMIS__VERSION-200__data-quality-dashboard-design-md @@ -0,0 +1,135 @@ +--- +edit_url: "https://github.com/dhis2-metadata/MAL_AGG/blob/master/docs/mal_agg_dq-design.md" +revision_date: "2022-06-09" +--- + +# Malaria Data Quality Dashboard { #malaria-data-quality-dashboard } + +## Introducción { #introduction } + +The WHO Malaria Data Quality (DQ) dashboard is an addendum to the [malaria burden reduction aggregate package](https://dhis2.org/who-package-downloads/#malaria). Like all the aggregate packages, this has been developed as an installable solution for countries to update their DHIS2-based HMIS, specifically the malaria aggregate indicators and dashboard. + +This chapter provides an overview of the design principles that have been applied within the core DHIS2 features for monitoring and improvement of data quality through DHIS2 dashboards. This dashboard complements other DHIS2 apps and tools such as the [WHO Data Quality App for DHIS2](https://docs.dhis2.org/en/use/optional-apps/who-data-quality-tool/installation-and-configuration.html). This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localization of the package and this package can be adapted to local needs and national guidelines. + +The objectives of the data quality dashboard are to: + +1. Bring key data quality metrics to the users routinely through use of DHIS2 dashboards to facilitate data quality improvement activities; +2. Monitor completeness and timeliness of reporting malaria data; +3. Monitor completeness of reporting of core malaria data variables in the monthly health facility reporting form; +4. Monitor internal consistency between variables to detect inconsistencies for quality improvements; +5. Compare trends of key malaria indicators at the various reporting levels and rapidly detect anomalies as red flags for poor data quality. + +The system design builds upon existing malaria aggregate guidelines principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. It is important to note that national guidelines and policies may vary and therefore it is recommended to adapt this package to local contexts. + +## Design Summary { #design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://who.dhis2.org/documentation/general_design_principles.html) and a common [naming convention](https://who.dhis2.org/documentation/naming_convention.html). + +The malaria Data Quality dashboard includes: + +1. Indicators: data quality indicators and other relevant indicators borrowed from malaria burden reduction package.. +2. Visualizations/analytic items: charts and pivot tables to visualize indicator performance +3. Dashboard: designed to present the visuals/analytic items (charts and tables) in a logical way to users + +Like all dashboard packages for DHIS2, the data visualizations are configured to display data for the organisation units for which the user has data capture access in the user configuration. In this way, the dashboard can be used at national, district or other sub-national levels to monitor data quality for the geographic area most relevant to the user. This enables actions to improve data quality to be taken as close to the point of data collection and validation as possible. Configuration of users and assignment to user groups to be able to access the dashboard should be considered within country context to ensure access is provided properly to users. + +### Intended users { #intended-users } + +- Health facility users: monitor completeness and consistency of data reported from the facility, which could support onsite data reviews, checking for data quality errors and cleaning for quality improvement (according to national policies & SOPs) +- District health managers: monitor data quality and detect facilities where data quality improvement may be needed; use the dashboard to provide feedback loops to facilities and plan data quality improvement follow-ups or other technical assistance activities +- National malaria program managers: monitor data quality and develop national data quality improvement plans; understand the potential biases in the routine data set to improve their ability to analyze routine malaria data and consider data quality limitations + +## Indicators { #indicators } + +Indicators are based on the data elements included in the WHO malaria burden reduction package for HMIS, which includes a monthly aggregate dataset. These indicators are used to develop dashboard items and all indicators are assigned to the indicator group "Malaria data quality". + +| name | Descripción | Numerator Description | Denominator Description | Indicator Type | Purpose | +| --- | --- | --- | --- | --- | --- | +| MAL - Reporting Completeness (%) | Number of actual reports received divided by total number of health facilities expected to report | Number of health facilities reported | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Reporting timeliness (%) | Number of actual reports received on time divided by total number of health facilities expected to report | Number of health facilities reported on time | Number of health facilities expected to report | Porcentaje | Reporting completeness | +| MAL - Confirmed malaria cases >/= Treated with 1st line courses | Confirmed malaria cases minus confirmed malaria cases treated with 1st line treatment courses (incl ACT) | Confirmed malaria cases - cases treated with 1st line tx | 1 | Numerator only | Consistency between variables | +| MAL - All cause deaths > Malaria inpatient deaths | All cause deaths minus malaria inpatient deaths | All cause deaths - Malaria inpatient deaths | 1 | Numerator only | Consistency between variables | +| MAL - All cause inpatients > Malaria inpatients | All cause inpatients minus malaria inpatients | All cause inpatients - Malaria inpatients | 1 | Numerator only | Consistency between variables | +| MAL - All cause outpatients > Total malaria cases | All cause outpatients minus total malaria cases | all cause outpatients - total malaria cases | 1 | Numerator only | Consistency between variables | +| MAL - Microscopy tested >/= Microscopy positive | Cases tested for malaria with Microscopy minus microscopy positive | Microscopy tested - Microscopy positive | 1 | Numerator only | Consistency between variables | +| MAL - RDT tested >/= RDT positive | Cases tested for malaria with RDT minus RDT positive | RDT tested - RDT positive | 1 | Numerator only | Consistency between variables | +| MAL - All malaria cases actual reported (%) | Count of reported total malaria cases (confirmed + presumed) divided by actual number of reports received multiplied by 100 | Total malaria cases (confirmed + presumed) | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause death actual reported (%) | Count of reported all-cause death divided by actual number of reports received multiplied by 100 | All-cause death | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause inpatient actual reported (%) | Count of reported all-cause inpatient divided by actual number of reports received multiplied by 100 | All-cause inpatient | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - All-cause outpatient cases actual reported (%) | Count of reported all-cause outpatient cases divided by actual number of reports received multiplied by 100 | All-cause outpatient cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Inpatient malaria cases actual reported (%) | Count of reported inpatient malaria cases divided by actual number of reports received multiplied by 100 | Inpatient malaria cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria confirmed cases actual reported (%) | Count of reported malaria confirmed cases divided by actual number of reports received multiplied by 100 | Malaria confirmed cases | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Malaria deaths actual reported (%) | Count of reported malaria deaths divided by actual number of reports received multiplied by 100 | Malaria deaths | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy positive actual reported (%) | Count of reported microscopy positive divided by actual number of reports received multiplied by 100 | Microscopy positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Microscopy tested actual reported (%) | Count of reported microscopy tested divided by actual number of reports received multiplied by 100 | Microscopy tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT positive actual reported (%) | Count of reported RDT positive divided by actual number of reports received multiplied by 100 | RDT positive | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - RDT tested actual reported (%) | Count of reported RDT tested divided by actual number of reports received multiplied by 100 | RDT tested | Actual report for malaria burden reduction | Porcentaje | Completeness of data variables | +| MAL - Outpatient malaria cases (%) | Number of malaria outpatient divided by number of all outpatients multiplied by 100 | Outpatient malaria cases | All-cause outpatients | Porcentaje | Consistency of variable by trends | +| MAL - RDT positivity rate (%) | Number of malaria RDT positive cases divided by total RDT tests multiplied by 100 | Cases positive with RDT | Tested (RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Slide (microscopy) positivity rate (%) | Number of malaria microscopy positive cases divided by total microcopy tests multiplied by 100 | Cases positive with microscopy | Cases tested with microscopy | Porcentaje | Consistency of variable by trends | +| MAL - Inpatient malaria cases (%) | Number of malaria inpatients divided by number of all inpatients deaths multiplied by 100 | Inpatient malaria cases | All cause inpatients | Porcentaje | Consistency of variable by trends | +| MAL - Malaria inpatient deaths (%) | Number of Inpatient malaria deaths divided by number of all deaths at facility multiplied by 100 | Malaria deaths | death | Porcentaje | Consistency of variable by trends | +| MAL - Malaria test positivity rate (Micr+RDT) (%) | Total number of positive cases (Micr + RDT) divided by total number of tested (Micr + RDT) multiplied by 100 | Total positive cases (Micr + RDT) | Total tested (Micr + RDT) | Porcentaje | Consistency of variable by trends | +| MAL - Suspected malaria cases tested (%) | Number of suspected cases tested with either microscopy or RDT divided by total number of suspected cases multiplied by 100 | Cases tested with microscopy + Cases tested with RDT | Suspected malaria cases | Porcentaje | Consistency of variable by trends | + +## Visualizations { #visualizations } + +For each of the indicators outlined above, visualization items have been created using tables and charts as shown below. This covers data quality analysis on completeness, timeliness and consistency of data and visualization. Color legends have also been used on pivot tables to show thresholds of performance with extremes of "red" and "green" flags to indicate low and high quality data respectively. These legends can be adapted by the country according to their own thresholds. + +### Chart 1: Reporting completeness { #chart-1-reporting-completeness } + +![Chart 1: Reporting completeness](resources/images/MALDQ1.png) + +### Table 1: Reporting completeness in public and private sector { #table-1-reporting-completeness-in-public-and-private-sector } + +![Table 1: Reporting completeness in public and private sector](resources/images/MALDQ2.png) + +### Chart 2: Reporting timeliness { #chart-2-reporting-timeliness } + +![Chart 2: Reporting timeliness](resources/images/MALDQ3.png) + +### Table 2: Reporting timeliness in private and public sector { #table-2-reporting-timeliness-in-private-and-public-sector } + +![Table 2: Reporting timeliness in private and public sector](resources/images/MALDQ4.png) + +### Table 3: Completeness of variable in actual reports { #table-3-completeness-of-variable-in-actual-reports } + +![Table 3: Completeness of variable in actual reports](resources/images/MALDQ5.png) + +### Table 4: Consistency between variables { #table-4-consistency-between-variables } + +![Table 4: Consistency between variables](resources/images/MALDQ6.png) + +### Chart 3: Proportion of outpatient malaria cases { #chart-3-proportion-of-outpatient-malaria-cases } + +![Chart 3: Proportion of outpatient malaria cases](resources/images/MALDQ7.png) + +### Chart 4: Proportion of inpatient malaria cases { #chart-4-proportion-of-inpatient-malaria-cases } + +![Chart 4: Proportion of inpatient malaria cases](resources/images/MALDQ8.png) + +### Chart 5: Proportion of inpatient deaths { #chart-5-proportion-of-inpatient-deaths } + +![Chart 5: Proportion of inpatient deaths](resources/images/MALDQ9.png) + +### Chart 6: Test positivity rate { #chart-6-test-positivity-rate } + +![Chart 6: Test positivity rate](resources/images/MALDQ10.png) + +### Chart 7: Slide positivity rate { #chart-7-slide-positivity-rate } + +![Chart 7: Slide positivity rate](resources/images/MALDQ11.png) + +### Chart 8: RDT positivity rate { #chart-8-rdt-positivity-rate } + +![Chart 8: RDT positivity rate](resources/images/MALDQ12.png) + +### Chart 9: Proportion of suspected individuals tested { #chart-9-proportion-of-suspected-individuals-tested } + +![Chart 9: Proportion of suspected individuals tested](resources/images/MALDQ13.png) + +## Dashboard { #dashboard } + +All data visualization items created have been configured on a single dashboard named 'Malaria Data Quality' and below is a snapshot of the dashboard with some of the items as displayed. By default, the Malaria Data Quality dashboard within the package is configured to be shared with the User Group 'Malaria access', which is the same user group used to provide access to dashboards in the Burden Reduction package. + +![Malaria Data Quality Dashboard](resources/images/MALDQ14.png) diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index 288c855a..aaf64970 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.0 - Uso +- App version 1.0 --- ## Browsing the Action Tracker { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index 5767e283..6a3dbcce 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.0 - Uso +- App version 1.0 --- # Linked Action Tracker Dashboard and Demo server { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index d7a6943c..c1115827 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.0 - Uso +- App version 1.0 --- # Action Tracker App Maintenance { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index f46963db..c1fee687 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.0 - Uso +- App version 1.0 --- # Action Planning in Action Tracker { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index 65e8037d..ac22d047 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.0 - Uso +- App version 1.0 --- # Action Tracking in Action Tracker { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index 852880fc..c72f194f 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Installing the BNA App { #installing-the-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index 5457f42d..5b13ef6c 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # BNA App Maintenance { #bna-app-maintenance } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index 2a13dfb8..fd7dedb8 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # BNA Analysis and Interpretation { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index 5b20e594..411526af 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # BNA App architecture { #bna-app-architecture } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index 91c8ce9d..055b7857 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Bottleneck Analysis Dashboard and Demo server { #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index 88987fbf..fe71c7e0 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # BNA App interventions configurations { #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index 66a5c573..b1bb1034 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Visualization operations { #visualization-operations } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index 098a7b47..db10fe15 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Adopting the use of the BNA App { #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index 2c738a2f..22c72183 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Capacity building { #capacity-building } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index b8a0ee6e..2e66e349 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # End User training { #end-user-training } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index 5c658567..b428ae6c 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Guide to BNA App Implementation { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index 691cc554..60d417db 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Integration Concepts for the BNA App. { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index ce4325cd..ea862ee6 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Opportunities and Challenges { #opportunities-and-challenges } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index 37336fed..09125988 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Planning and organising { #planning-and-organising } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index e011cd0e..39a45f0e 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Setting-up a new BNA App { #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index 0f35818b..eb9d45c2 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/es_419/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: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # BNA App Support and Scale-up { #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index 64d7269a..b15469d7 100644 --- a/projects/docs-full-site/es_419/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/es_419/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: '2021-09-09' tags: -- App version 1.2.2 - Uso +- App version 1.2.2 --- # Scale-up and sustainability { #scale-up-and-sustainability } diff --git a/projects/docs-full-site/fr/.cache_timestamp b/projects/docs-full-site/fr/.cache_timestamp index e19788da..f7abd606 100644 --- a/projects/docs-full-site/fr/.cache_timestamp +++ b/projects/docs-full-site/fr/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:22:11Z \ No newline at end of file +2024-10-19T21:21:48Z \ No newline at end of file diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md index 027bc075..e179a32f 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__analytics-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Analyse { #analytics } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md index 492e64a8..ae6414bf 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__apps-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Applications { #apps } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md index d3ccdb03..1494a0cb 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__audit-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md index 6b000170..2b82a1fb 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-approval-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Approbation des données { #data-approval } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md index c43af6b3..fd56e135 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-store-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Magasin de données { #data-store } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md index d0d3839d..90ca6936 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__data-validation-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Validation des données { #data-validation } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md index c1f9e827..7af774e4 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__email-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Adresses électronique { #email } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md index c2870dd7..35e18982 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__i18n-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # I18n { #i18n } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md index 4d7f1021..2a282219 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__introduction-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Aperçu { #webapi } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md index 1d9dff7d..0a4fe6ba 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__maintenance-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md index a547e8a6..d88dce40 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__messaging-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Messagerie { #messaging } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md index 1c425454..23e57827 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-gist-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Métadonnées Gist API { #gist_api } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md index 54e2ef2c..79a2c7f4 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__metadata-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Métadonnées { #metadata } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md index 7da6612d..88cff37d 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__new-tracker-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # New Tracker { #new-tracker } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md index 97b5d52b..a43a3f6f 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__org-unit-profile-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Profil d'unité d'organisation { #org_unit_profile } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md index 2e7d07f4..9f95600e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__scheduling-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Programmation { #webapi_scheduling } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md index a8d5dc4a..e430c692 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__settings-and-configuration-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Paramètres et configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md index 104e8569..8606cdee 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sharing-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Partage { #sharing } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md index 9dccb59c..ff8a974d 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__sms-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # SMS { #sms } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md index e366b779..21eda502 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__synchronization-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Synchronization { #webapi_synchronization } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md index 89e67081..907e2c8c 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__tracker-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Tracker { #tracker } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md index af54f804..9ae040d8 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__users-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Utilisateurs { #users } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md index 2d6083e2..c10471a0 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-238__visualizations-md +++ b/projects/docs-full-site/fr/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: -- Version principale de DHIS 2.38 - Développement +- Version principale de DHIS 2.38 --- # Visualisations { #visualizations } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md index ce123da9..fe9f498d 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Analyse { #analytics } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md index 9760d7cf..9bc69d15 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md index 311ba087..0fbc56d8 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Approbation des données { #data-approval } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md index c95ab6da..ccf94db0 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Données { #data } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md index 4d329a8c..4afe69e1 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-validation.md" revision_date: '2022-06-21' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Validation des données { #data-validation } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md index e4a269eb..c7c1abb1 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # I18n { #i18n } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md index b959e1cf..5b2c1894 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/overview.md" revision_date: '2023-05-03' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Aperçu { #webapi } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md index d1438af3..86a39ebe 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Messagerie { #messaging } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md index 04d10347..3f88a76d 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Métadonnées Gist API { #gist_api } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md index b0f5932a..d0fe6323 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata.md" revision_date: '2023-08-03' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Métadonnées { #metadata } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md index ba1d78c3..c96f81ad 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/scheduling.md" revision_date: '2022-09-13' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Programmation { #webapi_scheduling } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md index 2b90f145..3886d8e1 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Partage { #sharing } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md index 0c20c985..1aba7ec0 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # SMS { #sms } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md index c47d080f..7447cb47 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/synchronization.md" revision_date: '05/05/2022' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Synchronization { #webapi_synchronization } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md index 133d3f6a..850e05ae 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS version 2.39 - Développement +- DHIS version 2.39 --- # Visualisations { #visualizations } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md index 900d4e45..f83969bd 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md index b8a717e8..347d6b99 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Données { #data } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md index bb596ce7..62c02eba 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-validation-md +++ b/projects/docs-full-site/fr/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 Version 2.40 - Développement +- DHIS Version 2.40 --- # Validation des données { #data-validation } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md index a16371b8..e9c3c800 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__email-md +++ b/projects/docs-full-site/fr/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 Version 2.40 - Développement +- DHIS Version 2.40 --- # Adresses électronique { #email } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index a50632f0..393a6703 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md index a8bbf9c9..4809e8ac 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # I18n { #i18n } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md index c0c0c804..be8dce4a 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Messagerie { #messaging } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index 86c8a862..b2dfe18c 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Métadonnées Gist API { #gist_api } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index a7e1f69d..fa19eb0e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Métadonnées { #metadata } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 702e7d31..e696b159 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/fr/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 Version 2.40 - Développement +- DHIS Version 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index d0b04a7e..403267d9 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/fr/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 Version 2.40 - Développement +- DHIS Version 2.40 --- # Paramètres et configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md index 3096477c..2aa8866e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/synchronization.md" revision_date: '05/05/2022' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Synchronization { #webapi_synchronization } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md index 05eee58f..b3b04436 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md +++ b/projects/docs-full-site/fr/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 Version 2.40 - Développement +- DHIS Version 2.40 --- # Tracker (API obsolètes) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md index 7b90655d..6f5488aa 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS Version 2.40 - Développement +- DHIS Version 2.40 --- # Tracker { #tracker } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md index b792458f..ab4087e4 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-exchange.md" revision_date: '2024-06-26' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Échange de données { #data-exchange } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md index 6366dd23..503d8028 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Données { #data } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md index 3a4fb17f..ddcd4be0 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Validation des données { #data-validation } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md index 2d54fbdc..407a4040 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md index 4fc8c7eb..25eaa114 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Aperçu { #webapi } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md index 2f08705b..27ac6e6b 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Métadonnées Gist API { #gist_api } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md index d52516ac..28f24dde 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Métadonnées { #metadata } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md index 8b98331f..e6bf1de8 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md index e56a0f27..e2daf446 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/route.md" revision_date: '2024-09-24' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Route { #route } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md index 4b466425..ab7765ec 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Programmation { #webapi_scheduling } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md index ab8a47a5..c6861553 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Paramètres et configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md index db4cd11d..24f7347c 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # SMS { #sms } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md index cb9a3034..ef0342c7 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Synchronization { #webapi_synchronization } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md index 79363a3e..5d7278a7 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-deprecated-md +++ b/projects/docs-full-site/fr/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: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Tracker (API obsolètes) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md index 3b6813cd..5db23642 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS Version 2.41 - Développement +- DHIS Version 2.41 --- # Tracker { #tracker } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index 84258dce..063acc6c 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/fr/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-07-26' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Analyse { #analytics } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index 98358579..15510c97 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Applications { #apps } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index a746bea1..fc785098 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 0f15bcb4..62a77944 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Approbation des données { #data-approval } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index 8c6fae67..6df19482 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Saisie de données { #data-entry } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index 38d3a21b..9608b097 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/fr/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-09-18' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Échange de données { #data-exchange } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index dec923c8..6b070ac3 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Données { #data } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index 7676f179..6f68ef8e 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Magasin de données { #data-store } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index f3a43928..71f55468 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Validation des données { #data-validation } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md index 2c9c657c..8473e6bb 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__email-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Adresses électronique { #email } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index 84311cff..f029b8e5 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 129fb9b5..a13bd30f 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # I18n { #i18n } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index 6d1ad989..ea430596 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Aperçu { #webapi } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index 7f4e929f..63058078 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Maintenance { #maintenance } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md index 8534741c..652a680b 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__messaging-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Messagerie { #messaging } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index ed288aca..9781a5eb 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Métadonnées Gist API { #gist_api } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index 1b8ff185..4d4b2903 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-07-29' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Metadata { #webapi_metadata } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index 6b5037d6..30e7759f 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index 00f71f43..8e1f0eed 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Route { #route } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index 3d30f83e..5eec27ff 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Programmation { #webapi_scheduling } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index a4157afc..130ddae4 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Paramètres et configuration { #settings-and-configuration } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index e0a55cd9..302da677 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Partage { #sharing } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 7c733fac..635f3d21 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # SMS { #sms } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index 2d782911..c2360438 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Synchronization { #webapi_synchronization } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index d2f484a4..a5bdc2e6 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/fr/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-09-13' tags: -- Développement - Version Master de DHIS2 Central +- Développement --- # Utilisateurs { #users } diff --git a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index 96883366..af3a227a 100644 --- a/projects/docs-full-site/fr/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/fr/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: -- Développement - Version Master de DHIS2 Central +- Développement --- # Visualisations { #visualizations } diff --git a/projects/docs-full-site/fr/IMPLEMENT__DATA-USE__data-visualization-md b/projects/docs-full-site/fr/IMPLEMENT__DATA-USE__data-visualization-md index 6c4677f6..07ae1081 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__DATA-USE__data-visualization-md +++ b/projects/docs-full-site/fr/IMPLEMENT__DATA-USE__data-visualization-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/data-use/data-visualization.md" -revision_date: '2024-10-17' +revision_date: '2024-10-18' tags: - Implémentation --- @@ -27,9 +27,9 @@ Understanding these categories is essential to selecting the correct chart type - **Ordinal** - Categories with a meaningful order (e.g., disease status). These categories have a logical sequence. - For example, disease severity might be classified as mild, moderate, and severe, which has an inherent order. -> **Note**: +> **Note** > ->**Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. +> **Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. ![Variable categories](resources/images/dataviz_001.png) @@ -46,7 +46,7 @@ What’s the best way to choose the right visualization for the data at hand? [F Another Chart Chooser is mapped in the [Extreme Presentation Method](https://extremepresentation.com/). -![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.png) +![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.jpg) The summary below is based on the visualizations available in the core DHIS2 Data Visualizer App. @@ -93,9 +93,9 @@ The summary below is based on the visualizations available in the core DHIS2 Dat ### Specific Visualization Styles { #specific-visualization-styles } ->**Note** +> **Note** > ->**Data speaks louder than words!** +> **Data speaks louder than words!** In data visualization, choosing the right type of chart or graph is crucial for effectively communicating your data. Each visualization style has its strengths and is best suited for specific types of data and analytical purposes. This chapter explores a variety of visualization styles, detailing their applications and best practices. Whether you're looking to show trends over time, compare quantities, highlight correlations, or illustrate parts of a whole, selecting the appropriate visualization method will enhance clarity and insight. By understanding the nuances of each style, you can ensure that your data tells a compelling and accurate story. @@ -103,9 +103,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Correlation { #correlation } ->**Note** +> **Caution** > ->Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. +> Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. - **Scatterplot**: Shows the relationship between two continuous variables, each having its axis. Each point represents an observation's values on the two variables. It's useful for identifying trends, clusters, and outliers. For example, a scatterplot can display the relationship between the number of immunization campaigns conducted in various districts and the resulting immunization coverage rate. @@ -118,9 +118,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Ranking { #ranking } ->**Note** +> **Note** > ->Emphasizes the item's position in an ordered list rather than the absolute value. +> Emphasizes the item's position in an ordered list rather than the absolute value. - **Ordered bars/columns**: Shows ranks of values more easily when sorted. This visualization helps to quickly see the highest and lowest values. An ordered bar column chart can be used to display the number of TB cases in each district, sorted in descending order to highlight the districts with the highest burden. @@ -132,9 +132,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Change Over Time { #change-over-time } ->**Note** +> **Note** > ->Keep gaps between columns small to highlight data shape. +> Keep gaps between columns small to highlight data shape. Use markers for irregular data points. - **Column**: Emphasizes changing trends. Columns are used to show discrete data points over time. For example, monthly case figures can be shown as a column chart. @@ -152,9 +152,9 @@ Use markers for irregular data points. #### Magnitude { #magnitude } ->**Note** +> **Note** > ->Small gaps highlight data shape. Best for a single series of data. +> Small gaps highlight data shape. Best for a single series of data. - **Column/Paired column/bar**: Compare sizes, usually numbers rather than rates or percentages. For instance, HIV case figures for different regions can be compared using a bar chart. In this case, it is appropriate to keep the distance between the columns as they represent separate entities rather than variables through time. @@ -168,9 +168,9 @@ Use markers for irregular data points. #### Part-to-Whole { #part-to-whole } ->**Note** +> **Tip** > ->Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** +> Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** ![Imrpove the visualization choosing the most suitable colour set](resources/images/dataviz_022.png) @@ -206,9 +206,9 @@ Stacked columns or bar charts **should be avoided when** a detailed comparison o - **Choropleth**: Standard for rates on maps. Uses varying shades of a colour to represent data values for different regions. For example, population density by region can be shown using a choropleth map. ->**Note** +> **Note** > ->**Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. +> **Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. ![Map showing the percentage of PTB-BC cases in a region](resources/images/dataviz_013.png) @@ -287,9 +287,9 @@ A visualization should always have: ![Contextualized graph](resources/images/dataviz_024.png) ->**Note**: +> **Caution** > ->Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. +> Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. #### Pie Chart { #pie-chart } diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md index b2fc1a31..dd480744 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__ANIMAL-HEALTH__EVENT-BASED-SURVEILLANCE__design-md @@ -290,73 +290,73 @@ Pour le cas d'utilisation relatif à la surveillance de la santé publique, veui **Cas d'utilisation B** : DHIS2 est utilisé comme *système d'alerte précoce pour la santé animale* (comme dans le guide de conception de la santé animale). Les alertes et les notifications peuvent être déclenchées du secteur de la santé animale vers le secteur de la santé publique. Exemple : une épidémie de brucellose a été détecté dans une population bovine voisine ; les agents de santé des établissements de santé voisins reçoivent une notification afin d'être plus vigilants dans le dépistage des symptômes chez les patients. -**Cas d'utilisation C** : DHIS2 est utilisé comme une *surveillance intégrée basée sur les événements (EBS)* ou une plate-forme de gestion des événements. Les alertes et les notifications peuvent être analysées sur la base des données saisies et redirigées pour le tri et la vérification des signaux. Exemple : un ASC signale un groupe inhabituel de vaches mortes près de son village à l'aide de l'application mobile DHIS2, ce qui déclenche une alerte auprès du vétérinaire ; un ASC signale des morsures de chien provenant d'un animal présumé rapide et une alerte est envoyée à la fois aux établissements de santé voisins et au vétérinaire du district. +**Cas d'utilisation C** : DHIS2 est utilisé comme une *surveillance intégrée basée sur les événements (EBS)* ou une plate-forme de gestion des événements. Les alertes et les notifications peuvent être analysées sur la base des données saisies et redirigées pour le tri et la vérification des signaux. Exemple : un ASC signale un groupe inhabituel de vaches mortes près de son village à l'aide de l'application mobile DHIS2, ce qui déclenche une alerte auprès du vétérinaire ; un ASC signale des morsures de chien provenant d'un animal présumé enragé et une alerte est envoyée à la fois aux établissements de santé voisins et au vétérinaire du district. -### Configuration workflow { #configuration-workflow } +### Flux de travail de la configuration { #configuration-workflow } -In this section, we provide practical examples and a workflow for customizing notifications in DHIS2 for the use case of sharing data from DHIS2 with actors in animal and public health sectors. These features allow you to define what information to share with which types of actors, under which conditions, and how the information should be disseminated. +Dans cette section, nous fournissons des exemples pratiques et un flux de travail pour personnaliser les notifications dans DHIS2 pour le cas d'utilisation du partage des données de DHIS2 avec les acteurs des secteurs de la santé animale et de la santé publique. Ces fonctionnalités vous permettent de définir quelles informations partager avec quels types d'acteurs, dans quelles conditions et comment les informations doivent être diffusées. -For tracker data, the [program notifications](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create-a-program-stage-notification) feature is used. For aggregate data, [validation rule notifications](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/metadata.html?h=notifications+use#about_validation_rule) are used. +Pour les données de suivi, la fonction [notifications de programme](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create-a-program-stage-notification) est utilisée. Pour les données agrégées, les [notifications de règles de validation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/metadata.html?h=notifications+use#about_validation_rule) sont utilisées. -We recommend that implementers consider and map out the following before follow these steps to define and configure notifications in DHIS2 according to local context: +Nous recommandons aux chargés de la mise en œuvre de tenir compte des éléments ci-après avant de suivre les étapes qui suivent pour définir et configurer les notifications dans DHIS2 en fonction du contexte local : -1. Define the notification protocol: when, what, where, who? -2. Set up user group -3. Configure the validation rule or program stage notification -4. Create the notification message content -5. Schedule automated jobs -6. Set up the method of delivery -7. Maintenance: users, user groups, scheduled jobs +1. Définir le protocole de notification : quand, quoi, où, qui ? +2. Créer un groupe d'utilisateurs +3. Configurer la règle de validation ou la notification d'étape de programme +4. Créer le contenu du message de notification +5. Planifier des tâches automatisées +6. Définir la méthode de distribution +7. Maintenance : utilisateurs, groupes d'utilisateurs, travaux programmés -#### **Step 1: Define notification protocol: when, what, where, who** { #step-1-define-notification-protocol-when-what-where-who } +#### **Étape 1 : Définir le protocole de notification : quand, quoi, où, qui** { #step-1-define-notification-protocol-when-what-where-who } -Under what condition(s) should the system trigger a notification? To whom? Relevant protocols should be consulted and verified with the actors in both public health and animal health & livestock sectors to define and map the conditions for sending notifications based on data collected in DHIS2 by one sector to contacts in another sector. +Dans quelle(s) condition(s) le système doit-il déclencher une notification ? À qui ? Les protocoles pertinents doivent être consultés et vérifiés avec les acteurs des secteurs de la santé publique et de la santé animale et du bétail afin de définir et de mapper les conditions d'envoi de notifications basées sur des données collectées dans DHIS2 par un secteur à des contacts d'un autre secteur. -- When: Notification is shared when a specific condition is met, which may be based on: - - Number of cases: 1 or more - - Period: weekly, monthly, etc - - Place: health facility, district, etc -- What: Content of the notification, what variables? -- Where: which levels (facility, district?) should receive a notification -- within or outside their unit/level? -- Who: recipients of the notification - DHIS2 users and non-DHIS2 users +- Quand : La notification est partagée lorsqu'une condition spécifique est remplie, qui peut être basée sur : + - Nombre de cas : 1 ou plus + - Période : hebdomadaire, mensuelle, etc. + - Lieu : établissement de santé, district, etc +- Quoi : Contenu de la notification, quelles variables ? +- Où : quels niveaux (établissement, district ?) doivent recevoir une notification - à l'intérieur ou à l'extérieur de leur unité/niveau ? +- Qui : les destinataires de la notification - les utilisateurs de DHIS2 et les non-utilisateurs de DHIS2 -**Example use case example (A)**: DHIS2 is used by health facilities for weekly aggregate IDSR reporting of priority infectious diseases and for immediate case-based reporting of notifiable diseases. These include reporting of several suspected zoonotic conditions like rabies and anthrax which should also be notified to the district veterinary health officer for further investigation. The District Veterinary Officer (DVO) is not a typical DHIS2 user; however, when 1 or more human rabies cases is reported into the weekly IDSR in DHIS2 by any health center, the DVO should receive an email notification. +**Exemple de cas d'utilisation (A)** : DHIS2 est utilisé par les établissements de santé pour la déclaration hebdomadaire globale SIMR des maladies infectieuses prioritaires et pour la déclaration immédiate des cas de maladies à déclaration obligatoire. Il s'agit notamment de la déclaration de plusieurs zoonoses présumées, comme la rage et le charbon bactéridien, qui doivent également être notifiées au responsable de la santé vétérinaire du district en vue d'une enquête plus approfondie. Le vétérinaire de district (DVO) n'est pas un utilisateur habituel de DHIS2 ; cependant, lorsque 1 ou plusieurs cas de rage humaine sont signalés dans la SIMR hebdomadaire de DHIS2 par un centre de santé, le DVO doit recevoir une notification par courrier électronique. -#### **Step 2: Set up users and user groups** { #step-2-set-up-users-and-user-groups } +#### **Étape 2 : Configurer les utilisateurs et les groupes d'utilisateurs** { #step-2-set-up-users-and-user-groups } -Depending on the notification protocol defined in Step 1, new user groups may be needed. When the target recipients of the notification are already DHIS2 users, simply adding these users to an appropriate user group may be sufficient. If the target recipients are not DHIS2 users, they can be set up users or a user can be set up in DHIS2 to represent listservs that are managed in other platforms. Lastly, if an integration solution is being applied, a dedicated user may be required and should be discussed on a case-by-case basis. To receive e-mail notifications from DHIS2, the user does not need access to other parts of the DHIS2 system. +En fonction du protocole de notification défini à l'étape 1, de nouveaux groupes d'utilisateurs peuvent être nécessaires. Lorsque les destinataires de la notification sont déjà des utilisateurs de DHIS2, il peut suffire de les ajouter à un groupe d'utilisateurs approprié. Si les destinataires cibles ne sont pas des utilisateurs de DHIS2, ils peuvent être configurés en tant qu'utilisateurs ou un utilisateur peut être configuré dans DHIS2 pour représenter des listes de diffusion gérées dans d'autres plates-formes. Enfin, si une solution d'intégration est appliquée, un utilisateur dédié peut être nécessaire et doit être discuté au cas par cas. Pour recevoir des notifications par courrier électronique de DHIS2, l'utilisateur n'a pas besoin d'accéder à d'autres parties du système DHIS2. -**Use case example (A):** District Veterinary Officers (DVOs) are *not* typical DHIS2 users. They only receive notifications from DHIS2, but they are not expected to log in to capture data or to analyze data. A District Veterinary Officer user group is configured in DHIS2 in order to configure and send notifications. A DHIS2 user account for each district is set up with the appropriate access to org units to facilitate notifications to the designated DVO email address, but the user does not have access to capture, view or analyze data in DHIS2. +**Exemple de cas d'utilisation (A):** Les Agents Vétérinaires de District (DVO) *ne sont pas* des utilisateurs typiques de DHIS2. Ils reçoivent uniquement des notifications de DHIS2, mais ne sont pas censés se connecter pour saisir ou analyser des données. Un groupe d'utilisateurs d'agents vétérinaires de district est configuré dans DHIS2 afin de configurer et d'envoyer des notifications. Un compte d'utilisateur DHIS2 pour chaque district est configuré avec l'accès approprié aux unités d'organisation pour faciliter les notifications à l'adresse électronique désignée du DVO, mais l'utilisateur n'a pas accès à la saisie, à la visualisation ou à l'analyse des données dans DHIS2. -#### **Step 3: configure your program notification or your validation notification** { #step-3-configure-your-program-notification-or-your-validation-notification } +#### **Étape 3 : configurez votre notification de programme ou votre notification de validation** { #step-3-configure-your-program-notification-or-your-validation-notification } -Based on the conditions defined in Step 1, configure a program notification (for tracker data) or validation notification (for aggregate data and outbreak thresholds). These conditions will depend on the existing configuration and what data is being captured in DHIS2. +Based on the conditions defined in Step 1, configure a program notification (for tracker data) or validation notification (for aggregate data and outbreak thresholds). These conditions will depend on the existing configuration and what data is being captured in DHIS2. -In the *aggregate domain*, validation rule notifications can be configured to trigger an alert when a given disease threshold for a given geographic area and time frame is reached. For more information, **see the [validation rule notifications](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/metadata.html?h=notifications+use#about_validation_rule) documentation.** Remember that you may first need to create your validation rule to establish the condition for a threshold. +Dans le *domaine agrégé*, les notifications de règles de validation peuvent être configurées pour déclencher une alerte lorsqu'un seuil de maladie donné est atteint pour une zone géographique et une période données. Pour plus d'informations, **consultez la documentation [notifications des règles de validation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/metadata.html?h=notifications+use#about_validation_rule). ** Rappelez-vous que vous devrez peut-être d'abord créer votre règle de validation afin d'établir la condition d'un seuil. -In the *tracker domain*, program notifications and program stage notifications can trigger a notification based on a flexible range of variables captured in the DHIS2 tracker program. For more information, **see the [program notifications](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create-a-program-stage-notification) documentation.** Remember that you may need to first create a program rule to establish the condition. +Dans le *domaine du tracker*, les notifications de programme et les notifications d'étape de programme peuvent déclencher une notification sur la base d'une gamme flexible de variables saisies dans le programme tracker de DHIS2. Pour plus d'informations, **consultez la documentation sur les [notifications de programme] (https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create-a-program-stage-notification).** Rappelez-vous que vous devrez peut-être d'abord créer une règle de programme pour établir la condition. -**Example use case (A): Validation Notification** +**Exemple de cas d'utilisation (A) : Notification de validation** -We want to configure an alert to the District Veterinary Officer when 1 or more human rabies cases is reported in the weekly aggregate IDSR dataset. +Nous voulons configurer une alerte pour le vétérinaire de district lorsque 1 ou plusieurs cas de rage humaine sont signalés dans l'ensemble de données de la SIMR hebdomadaire. -1. Create a validation rule to represent the condition for your threshold. In this case, assign the data element on the left hand side operator as 'Rabies cases', the operator as less than, the right hand side as 1. When the time period is set to one week and the org unit is set to Facility Level, the rule will allow a notification to be triggered any time a facility that reports more than one rabies case in a given weekly period. +1. Créez une règle de validation pour représenter la condition de votre seuil. Dans ce cas, attribuez à l'élément de données de l'opérateur de gauche la valeur "Cas de rage", à l'opérateur la valeur "inférieur à" et à l'opérateur de droite la valeur "1". Lorsque la période de temps est fixée à une semaine et que l'unité d'organisation est fixée au niveau de l'établissement, la règle permet de déclencher une notification chaque fois qu'un établissement signale plus d'un cas de rage au cours d'une période hebdomadaire donnée. -![validation rule](resources/images/AH_02_validation_rule_rabies.png) +![règle de validation](resources/images/AH_02_validation_rule_rabies.png) -*Tip: Remember to tick the box 'Skip this rule during form validation' if you do not want this rule evaluated during data entry!* +*Conseil : N'oubliez pas de cocher la case « Ignorer cette règle lors de la validation du formulaire » si vous ne souhaitez pas que cette règle soit évaluée lors de la saisie des données !* -![validation rule skip](resources/images/AH_02_validation_rule_skip.png) +![ignorer la règle de validation](resources/images/AH_02_validation_rule_skip.png) -2. Create a validation rule notification. +2. Créer une notification de règle de validation. -Select your desired validation rule ("under what condition will I send a notification?") +Sélectionnez la règle de validation souhaitée ("sous quelle condition vais-je envoyer une notification ?") -Select the desired recipient user group ("who will receive this notification?") +Sélectionnez le groupe d'utilisateurs destinataires souhaité ("qui recevra cette notification ?") -![validation rule](resources/images/AH_02_validation_notification.png) +![règle de validation](resources/images/AH_02_validation_notification.png) -**Example use case (A): Program Notification** +**Exemple de cas d'utilisation (A) : Notification de programme** We want to configure an alert to the District Veterinary Officer when a suspected rabies case reported in a case-based tracker program receives a lab confirmation. @@ -379,23 +379,23 @@ We want to configure an alert to the District Veterinary Officer when a suspecte #### Step 4: Create notification message content { #step-4-create-notification-message-content } -When configuring the validation notification or a program notification, you will set your notification message template. +Lors de la configuration d'une notification de validation ou d'une notification de programme, vous définirez votre modèle de message de notification. -*Tip: ensure your message notification template includes action points and reminders to the target user based on local protocols.* +*Conseil : veillez à ce que le modèle de notification de votre message comprenne des points d'action et des rappels à l'intention de l'utilisateur cible en fonction des protocoles locaux.* -![message template](resources/images/AH_04_message_template_rabies.png) +![modèle de message](resources/images/AH_04_message_template_rabies.png) -Template variables can be used to generate dynamic messages based on parameters such as organisation unit, current date, and period. +Les variables de modèle peuvent être utilisées pour générer des messages dynamiques basés sur des paramètres tels que l'unité d'organisation, la date du jour et la période. -*Figure: Template variables for validation rules* +*Figure : Modèles de variables pour les règles de validation* -![template variable](resources/images/AH_04_message_template_variables.gif) +![modèle de variables](resources/images/AH_04_message_template_variables.gif) -Template variables render dynamically in the message to the target user. In this example, we can see that the rabies cases were reported from Mahosot Hospital (reporting org unit) in epi Week 28 2024 (based on weekly data set). +Les variables du modèle s'affichent dynamiquement dans le message destiné à l'utilisateur cible. Dans cet exemple, nous pouvons voir que les cas de rage ont été signalés par l'hôpital Mahosot (unité d'organisation déclarante) au cours de la semaine du 28 2024 (basé sur un ensemble de données hebdomadaire). -![rabies message](resources/images/AH_04_message_rabies.png) +![message relatif à la rage](resources/images/AH_04_message_rabies.png) -#### Step 5: Schedule automated jobs { #step-5-schedule-automated-jobs } +#### Étape 5: Programmer des tâches automatisés { #step-5-schedule-automated-jobs } Several jobs need to run in sequence in order to automate validation notifications (these can also be run manually). See the [documentation for scheduling](https://docs.dhis2.org/en/implement/health/disease-surveillance/ids-aggregate/installation.html#idsr-scheduling) and sequencing jobs to automate this process. @@ -414,7 +414,7 @@ More robust and complex notifications workflows or support for other types of co - Chatbots and social media platforms (see [video](https://www.youtube.com/watch?v=L35svQE42Qo)) - Other innovations leveraging the DHIS2 API and other extensibility features like web hooks -#### Step 7: Maintenance { #step-7-maintenance } +#### Étape 7 : Maintenance { #step-7-maintenance } A system administrator should be designated to maintain the solution over time. This can typically be managed by the core DHIS2 team at the Ministry or similar: diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md new file mode 100644 index 00000000..76456544 --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -0,0 +1,206 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-design.md" +revision_date: '2023-03-31' +tags: +- Implémentation +--- + +# COVID-19 Surveillance - Aggregate System Design Guide { #c19-agg-design } + +## Objectif { #purpose } + +The COVID-19 Surveillance Aggregate System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Contexte { #background } + +This aggregate design has been updated to reflect new aggregate reporting requirements from the [Global surveillance of COVID-19: WHO process for reporting aggregated data](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form), last updated on August 7, 2020. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| **Type de Package de surveillance** | **Surveillance basée sur les cas (Tracker)** | **Case surveillance line-listing (Event)** | **Surveillance des cas (Agrégat )** | +| --- | --- | --- | --- | +| **Description** | Enrolls a case and tracks over time through laboratory confirmation & case outcome | Permet de saisir les détails relatifs à un cas critique sous forme de liste de lignes | Enables weekly reporting of key aggregate data points | +| **Avantages** | La grande granularité des données et les multiples dimensions temporelles de l'analyse peuvent permettre de décentraliser le flux de travail c'est-à-dire tous les événements liés au cas. | Caractéristique plus granulaire qu'agrégée et pouvant saisir les principales dimensions temporelles (c'est-à-dire la date du rapport par rapport à l'apparition des symptômes) ; réduction de la charge de saisie des données par rapport au tracker et niveau de complexité peu élevé | Peu complexe, facile à mettre en œuvre, plus facile à gérer lorsque le nombre de cas est élevé | +| **Inconvénients** | Le volume de données à saisir peut être écrasant lorsque le nombre de cas atteint le seuil ; ceci peut rendre la mise en œuvre complexe | Ne prend pas en charge le suivi des cas ou d'autres flux de travail décentralisés | Une granularité plus faible pour l'analyse détaillée (c'est-à-dire une analyse basée exclusivement sur la date de notification du cas, une désagrégation limitée)| + +**This document covers only the design of the aggregate package**; separate system design documents are available for DHIS2 Tracker and Line-listing (event-based) packages. As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The aggregate package is designed to meet the most critical reporting requirements and analytical capacities for surveillance and response. + +Les objectifs du progiciel de surveillance du COVID-19 sont les suivants : + +1. surveiller les tendances de la maladie là où il y a transmission interhumaine ; +2. détecter rapidement les nouveaux cas dans les pays où il n'y a pas de circulation du virus ; +3. fournir des informations épidémiologiques pour effectuer des évaluations des risques aux niveaux national, régional et mondial ; et +4. fournir des informations épidémiologiques pour orienter les mesures de préparation et d'intervention. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated August 7, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## Résumé de la conception du système { #system-design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +The aggregate COVID-19 surveillance package includes + +1. Weekly aggregate data set and data elements for key COVID-19 surveillance reporting +2. Categories for data disaggregation +3. Core indicators +4. Tableau de bord et ses items + +The dataset captures a minimum number of data points that meet the current WHO weekly reporting requirements; and generate a core set of indicators and dashboards for national and sub-national decision-makers to rapidly analyze and respond to disease trends. + +| **Nom**. | **Périodicité** | **Objectif** | +| --- | --- | --- | +| Aggregate Weekly Surveillance | Hebdomadaire| Reporting of key COVID-19 surveillance data including cases, tests and deaths. | + +It is recommended that the weekly dataset is assigned to Organisation Units at the lowest level of the health system feasible for reporting data, such as health facilities. + +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). + +### Utilisateurs cibles { #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. +- Autorités sanitaires nationales et locales : suivi et analyse des données de surveillance des maladies au moyen de tableaux de bord et d'outils d'analyse permettant de réaliser des évaluations des risques et de planifier les interventions ; production de rapports en vue des rapports régionaux et global + +## Ensembles de données { #datasets } + +This dataset is intended to capture weekly data needed for rapid response to disease transmission. If the burden of reporting becomes too great or when it is no longer considered an emergency situation in the country, the data set may be changed to monthly according to MOH policies. + +### Daily Surveillance Data Elements { #daily-surveillance-data-elements } + +The following lists the data elements and disaggregation (category combinations) included in the data set: + +| **Éléments de données** | **Category Combinations** | +| --- | --- | +| New Confirmed Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Confirmed Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Hospitalized Cases | Aucun | +| New Discharged Cases | Aucun | +| New Cases Among Health Workers (Confirmed + Probable) | Aucun | +| New Deaths Among Health Workers (Confirmed + Probable) | Aucun | +| Number of Persons Tested for COVID-19 | Aucun | +| Number of persons Tested with PCR Assay | Aucun | +| Transmission Classification | Aucun | + +### Weekly Surveillance Data Entry Form { #weekly-surveillance-data-entry-form } + +- **Section 1: New confirmed and probable Cases** + +Data should be entered for all new confirmed and probable cases reported during the reporting period. Confirmed cases refer to laboratory confirmed cases per WHO guidance; probable cases are defined by WHO as cases where laboratory test result is inconclusive; however countries may apply their own case definitions. The total column is automatically summed during data entry. +![Picture1](resources/images/AGG_Picture1.png) + +- **Section 2: New confirmed and probable deaths** + +Data should be entered for new confirmed and probable deaths reported during the reporting period. The total column is automatically summed during data entry. + +![Picture2](resources/images/AGG_Picture2.png) + +- **Section 3: Health worker infection and death** + +This section captures data for health workers' new confirmed and probable cases including deaths reported during the reporting period. + +![Picture3](resources/images/AGG_Picture3.png) + +- **Section 4: Hospitalisation and discharges** + +This section captures data for new hospitalisation and discharges during the reporting period. + +![Picture4](resources/images/AGG_Picture4.png) + +- **Section 5: Tests conducted** + +This section captures data for tests conducted with additional requirement to report tests conducted using PCR during the reporting period + +![Picture5](resources/images/AGG_Picture5.png) + +- **Section 6: Transmission Classification** + +This section summarizes the major form of transmission classification experienced by the reporting unit. + +![Picture7](resources/images/AGG_Picture6.png) + +### Personnalisation des formulaires de saisie de données { #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) + +## Data Validation { #data-validation } + +The following data validation rules have been configured. These validation rules do not run in the data entry form itself as it is anticipated that the urgent reporting of data where events occur in different time frames (e.g. one week can see only 3 new cases but 5 deaths). + +| **Nom**. | **Opérateur** | **Instruction** | **Left side description** | **Right side description** | +| --- | --- | --- | --- | --- | +| COVID19 - PCR tests \<= tested | less\_than\_or\_equal\_to | Tested with PCR should be less than or equal to total tests conducted | Tested with PCR | Tested conducted | +| COVID19 - New Cases hospitalised \<= All New Cases | less\_than\_or\_equal\_to | New Cases hospitalised should be less than or equal to all new cases | New Cases hospitalised | All New Cases | +| COVID19 - New confirmed deaths \<= New confirmed cases | less\_than\_or\_equal\_to | New confirmed deaths should be less than or equal to New confirmed cases | New confirmed deaths | New confirmed cases | +| COVID19 - Probable deaths \<= New probable cases | less\_than\_or\_equal\_to | Probable deaths should be less than or equal to New probable cases | Probable deaths | New probable cases | +| COVID19 - New deaths among HW (confirmed + probable) \<= All deaths reported | less\_than\_or\_equal\_to | New deaths among HW (confirmed + probable) should be less than or equal to All deaths reported | New deaths among HW (confirmed + probable) | All deaths reported | +| 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) | + +## Groupes d'utilisateurs { #user-groups } + +Le package de métadonnées englobe les groupes d’utilisateurs ci-après : + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Please refer to the [installation guidance](covid-19-aggregate-installation.html) for more information. + +## Indicateurs { #indicators } + +From the data captured, we can calculate at least the following indicators, many of which are recommended by the WHO for [weekly reporting](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) and present them in a dashboard. All COVID-19 program indicators are assigned to the Indicator Group 'COVID19'. + +| **name** | **description** | +| --- | --- | +| COVID19 - New Confirmed Deaths | Number of new confirmed deaths | +| COVID19 - New Cases Among HW (Confirmed + Probable) | Number of New Cases Among HW (Confirmed + Probable) | +| COVID19 - Proportion of HW amongst reported cases (%) | Proportion of HW amongst reported cases (%) | +| COVID19 - Active cases | Number of of active cases | +| COVID19 - Closed cases | Number of closed cases | +| COVID19 - New Confirmed cases | Number of new Confirmed cases | +| COVID19 - Recovery rate (%) | Recovery rate of confirmed cases | +| COVID19 - Case fatality rate among HW (%) | Case fatality rate among HW | +| COVID19 - New Hospitalized Cases | New Hospitalized Cases | +| COVID19 - Tested | Total number of tests conducted | +| COVID19 - Tested with PCR Assay | Tested with PCR assay | +| COVID19 - Positivity rate (%) | Positivity rate | +| COVID19 - New Probable Cases | Number of new probable cases | +| COVID19 - New Discharged Cases | Number of new discharged cases | +| COVID19 - New Deaths Among HW (Confirmed + Probable) | Number of new deaths among HW (Confirmed + Probable) | +| COVID19 - Proportion of PCR tests (%) | Proportion of PCR tests conducted | +| COVID19 - All cases (Confirmed + Probable) | Number of all cases (Confirmed + Probable) | +| COVID19 - New Probable Deaths | Number of new probable deaths | +| COVID19 - Case fatality rate (%) | Case fatality rate among confirmed cases | + +## Tableaux de bord { #dashboards } + +Key analytic items have been configured and added onto the dashboard “COVID19 - Aggregate Weekly Surveillance”. These items include; pivot tables, charts and a map designed to provide data visualization for some of the data captured based on the indicators. In the process of adopting this package, users can modify or create additional items as suits their analytical needs and equally make the necessary adjustments to the dashboard. + +| **name**|**type**| +| --- | --- | +|COVID19 - Tested, tests with PCR and positivity rate by subnational level this year |Tableau croisé dynamique| +|COVID19 - HW amongst reported cases this year |Chart| +|COVID19 - Fatality rate amongst HW.|Chart| +|COVID19 - New confirmed cases and deaths in the last 12 weeks|Chart| +|COVID19 - Cumulative tests conducted, cases reported, hospitalised, discharged and deaths|Chart| +|COVID19 - Cumulative confirmed cases by subnational|Carte| +|COVID19 - Deaths by age groups last weeks|Chart| +|COVID19 - Confirmed cases by sex in the last 14 weeks|Chart| +|COVID19 - Closed and active cases at subnational last months|Chart| +|COVID19 - Case recovery and fatality rates last 12 weeks|Chart| +|COVID19 - Active and Closed Cases last 12 weeks|Chart| + +## Références { #references } + +- Installation guidance: [https://www.dhis2.org/covid-19](covid-19-aggregate-installation.html) +- WHO Interim guidelines on nCoV-19 surveillance & case definitions (last updated March 20, 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions>]() +- WHO COVID-19 surveillance data dictionary (v6) +[https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98\_2](https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2) +- WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) + [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +- Rapports de l'OMS sur la situation du coronavirus + [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports>]() +- Global surveillance of COVID-19: WHO process for reporting aggregated data +[https://www.who.int/publications/i/item/aggregated-weekly-reporting-form](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md new file mode 100644 index 00000000..5a234c3c --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-installation.md" +revision_date: '2022-11-07' +tags: +- Implémentation +--- + +# Aggregate Package Installation Guide { #c19-agg-installation } + +## Présentation { #overview } + +Ce document est destiné à guider les administrateurs dans le processus d'installation du package de configuration standard COVID-19 pour DHIS2 pour la déclaration des données agrégées. Il est donc nécessaire d'avoir une bonne compréhension de DHIS2. + +Les packages de configuration pour DHIS2 consistent en un fichier de métadonnées au format [JSON](https://en.wikipedia.org/wiki/JSON) qui peut être importé dans une instance de DHIS2, ainsi que la documentation associée. Le package fournit un contenu prédéfini et standard selon les recommandations de l'OMS. Ce document couvre des packages complets qui comprennent des configurations de collecte de données (ensembles de données, éléments de données, règles de validation) ainsi que des analyses et des tableaux de bord (graphiques, cartes et tableaux croisés dynamiques favoris). Il est destiné à être utilisé lorsqu'aucune collecte de données n'est configurée dans DHIS2, ou en cas de remplacement ou de révision du contenu existant pour l'aligner sur les recommandations de l'OMS. + +Les packages de configuration se composent de 4 éléments principaux : + +* des ensembles de données avec des éléments de données ; +* un ensemble d'indicateurs ; +* des résultats analytiques (tableau croisé dynamique, visualiseur de données et favoris SIG) ; et +* un ensemble de tableaux de bord. + +Ces composantes sont toutes liées, c'est-à-dire que les indicateurs sont basés sur les éléments de données inclus, les résultats analytiques sont basés sur les indicateurs inclus, et les tableaux de bord sont constitués des résultats analytiques inclus. + +## Installation { #installation } + +L'installation du module se fait en deux étapes : + +1. [Préparation](#preparing-the-metadata-file) du fichier de métadonnées avec les métadonnées de DHIS2. +2. [Importation](#importing-metadata-file) du fichier de métadonnées dans DHIS2. +3. [Configuration](#configuration-additionnelle) des métadonnées importées. +4. [Exécution](#exemples-d'autres-modifications) des modifications spécifiques au package. + +Cette section traite des deux premières étapes que sont la préparation et l’importation du fichier de métadonnées dans DHIS2, tandis que la procédure de configuration est abordée dans la section suivante. Il est recommandé de lire les deux sections avant de commencer le processus d’installation et de configuration dans DHIS2. Outre les étapes générales décrites ici, certains des packages de configuration comportent des annexes au guide d’installation, qui décrivent des points particuliers. Ces annexes sont énumérées dans la section appropriée [ici] (https://dhis2.org/who-package-downloads). + +La procédure décrite dans ce document doit être testée dans un environnement de test et de simulation avant d'être répétée ou transférée à une instance de production du DHIS2. + +Packages à configuration multiple + +Certains packages de configuration ont des métadonnées qui se chevauchent, par exemple les indicateurs. Cela signifie que dans certaines situations, les modifications apportées aux métadonnées des packages de configuration importés précédemment peuvent être écrasées lors de l’importation d’un package différent. Cela peut être évité en important des métadonnées « nouvelles seulement » plutôt que « nouvelles et mises à jour », mais notez que dans les deux cas, des modifications manuelles seront nécessaires. Vous devez au moins vous assurer que les métadonnées utilisées par plusieurs programmes sont [partagées] (https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/users-roles-and-groups.html#mgt_usergroup) avec les groupes d’utilisateurs appropriés pour les deux programmes. + +## Conditions requises { #requirements } + +Pour installer le package de configuration, il est nécessaire d'avoir un compte d'utilisateur administrateur dans DHIS2, avec les autorisations permettant d'ajouter/de modifier les objets de métadonnées (publiques), y compris (mais sans s'y limiter) : + +* des éléments de données (y compris les catégories) +* des ensembles de données +* indicateurs +* des types d'indicateurs +* des tableaux de bord +* le visualiseur de données, le tableau croisé dynamique et les favoris du SIG + +La liste complète des objets inclus dans le package (pour lesquels l'administrateur a besoin d'autorisation avant de les gérer) se trouve dans le Document de référence des métadonnées pour le package de configuration en question. + +Si des modifications du fichier de métadonnées .json du package de configuration doivent être apportées [(voir ci-dessous)](https://who.dhis2.org/documentation/installation_guide_complete.html#preparing-the_metadata-file), il convient d'utiliser un [éditeur de texte](https://en.wikipedia.org/wiki/Text_editor). Ces modifications ne doivent pas être effectuées avec un logiciel de traitement de textes tel que Microsoft Word. + +Le package de configuration peut être installé dans le système DHIS2 par l’intermédiaire de l’application DHIS2 Health, ou manuellement par le biais d’un fichier .json contenant les métadonnées du DHIS2 en utilisant l’application [Importer/Exporter](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) du DHIS2. La procédure décrite dans le reste de cette section s’applique au processus d’importation manuelle des métadonnées. + +La section [Configuration] (https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) s'applique aux deux méthodes. + +## Préparation du fichier de métadonnées { #preparing-the-metadata-file } + +**N.B.** : Si vous installez le package sur une nouvelle instance de DHIS2, vous pouvez alors ignorer la section "Préparation du fichier de métadonnées" et passer immédiatement à la section "[Importer un fichier de métadonnées dans DHIS2](#importing-a-metadata-file-into-dhis2)". + +Bien que ce ne soit pas toujours nécessaire, il peut souvent être avantageux d'apporter certaines modifications au fichier de métadonnées avant son importation dans DHIS2. + +## Dimension de données par défaut { #default-data-dimension } + +Dans les premières versions de DHIS2, l'UID de la dimension des données par défaut était généré automatiquement. Ainsi, alors que toutes les instances du DHIS2 ont une option de catégorie par défaut, une catégorie d'élément de données, une combinaison de catégories et une combinaison d'options de catégories, les UID de ces valeurs par défaut peuvent être différents. Les versions plus récentes de DHIS2 ont des UID codés en dur pour la dimension par défaut, et ce sont ces UID qui sont utilisés dans les packages de configuration. + +Pour éviter les conflits lors de l'importation des métadonnées, il est conseillé de rechercher et de remplacer l'ensemble du fichier .json pour toutes les occurrences de ces objets par défaut, en remplaçant les UID du fichier .json par les UID de la base de données dans laquelle le fichier sera importé. Le tableau 1 indique les UID qui doivent être remplacés, ainsi que les point d'extrémité de l'API pour l'identification des UID existants. + +|Objet|UID|Chemin vers l'API| +|--|--|--| +|Catégorie|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Option de catégorie|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Combinaison de catégories|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Combinaison d’options catégorie|HllvX50cXC0|../api/categoryOptionCombos.json?filter=name:eq:default| + +Par exemple, si vous importez un package de configuration dans [https://play.dhis2.org/demo](https://play.dhis2.org/demo), l'UID de la combinaison d'options de catégorie par défaut peut être identifié via [https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default](https://play.dhis2.org/demo/api/categoryOptionCombos.json?filter=name:eq:default) comme `bRowv6yZOF2`. Vous pouvez alors rechercher et remplacer toutes les occurrences de `HllvX50cXC0` par `bRowv6yZOF2` dans le fichier .json. Notez que cette opération de recherche et de remplacement doit être effectuée avec un éditeur de texte brut, et non avec un logiciel de traitement de textes comme Microsoft Word. + +## Types d'indicateurs { #indicator-types } + +Le type d'indicateur est un autre type d'objet pouvant créer un conflit d'importation puisque certains noms sont utilisés dans différentes bases de données de DHIS2 ("Pourcentage", par exemple). Étant donné que les types d'indicateurs sont définis simplement par leur facteur et par le fait qu'il s'agisse ou non de simples nombres sans dénominateur, ils sont sans aucune ambiguïté et peuvent être remplacés par une recherche et un remplacement des UID. Cela permet d'éviter d'éventuels conflits d'importation et de ne pas créer de types d'indicateurs dupliqués. Le tableau 2 montre les UID qui pourraient être remplacés, ainsi que les points d'extrémité de l'API pour identifier les UID existants + +|Objet|UID|Chemin vers l'API| +|--|--|--| +|Numérateur seulement (nombre)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Pourcentage|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| + +**N.B. 1** : en remplaçant les UID comme décrit et en important le fichier .json, le nom (y compris les traductions éventuelles) des types d'indicateurs en question sera mis à jour pour correspondre à ceux inclus dans les packages de configuration. + +**N.B. 2** : Une alternative à la réutilisation des types d'indicateurs existants consiste à importer les types qui sont inclus dans le package de configuration, puis à supprimer ceux qui se chevauchent. Pour ce faire, il faut mettre à jour tous les indicateurs utilisant les types déjà présents avec ceux nouvellement importés, et ensuite supprimer les types d'indicateurs qui existaient. + +## Importation de métadonnées dans DHIS2 { #importing-a-metadata-file-into-dhis2 } + +Le fichier de métadonnées .json est importé via l’application [Importer/Exporter](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) de DHIS2. Nous vous recommandons d’utiliser la fonction « test » pour identifier les problèmes avant de tenter d’effectuer une importation réelle des métadonnées. Si le « test » signale des problèmes ou des conflits, consultez la section [conflits lors de l’importation](https://who.dhis2.org/documentation/installation_guide_complete.html#handling-import-conflicts) ci-dessous. + +Si l'importation "d'essai"/"de validation fonctionne sans erreur, essayez d'importer les métadonnées. Si l'importation réussit sans aucune erreur, vous pouvez alors passer à la [configuration](https://who.dhis2.org/documentation/installation_guide_complete.html#configuration) du module. Dans certains cas, les conflits ou les problèmes d'importation ne sont pas affichés pendant le "test", mais apparaissent lorsque l'on tente l'importation proprement dite. Dans ce cas, le résumé de l'importation énumère les erreurs à résoudre. + +### Gestion des conflits d'importation { #handling-import-conflicts } + +**N.B.** : Si vous importez dans une nouvelle instance DHIS2, vous n'aurez pas à vous soucier des conflits d'importation, car il n'y a rien dans la base de données que vous importez qui puisse entrer en conflit avec celle-ci. Suivez les instructions pour importer les métadonnées, puis passez à la section "[Configuration supplémentaire](#configuration-supplémentaire)". + +Plusieurs de conflits peuvent survenir, mais le plus courant est le fait qu'il y ait des objets de métadonnées dans le package de configuration avec un nom, un nom abrégé et/ou un code existant déjà dans la base de données cible. Il existe plusieurs solutions alternatives à ces problèmes, avec de différents avantages et inconvénients. La solution la plus appropriée dépendra, par exemple, du type d'objet pour lequel un conflit survient. + +#### Option 1 { #alternative-1 } + +Renommez l'objet de votre base de données DHIS2 pour lequel il y a un conflit. L'avantage de cette approche est que vous n'avez pas besoin de modifier le fichier .json, puisque les modifications sont effectuées par l'interface utilisateur de DHIS2. Cette méthode est probablement moins susceptible d'entraîner des erreurs. Cela signifie également que le package de configuration est laissé tel quel, ce qui peut être un avantage, par exemple, lorsque du matériel de formation et de la documentation basés sur le package de configuration seront utilisés. + +#### Option 2 { #alternative-2 } + +Renommez l'objet pour lequel il y a un conflit dans le fichier .json. L'avantage de cette approche est que les métadonnées DHIS2 existantes sont laissées telles quelles. Cela peut être un facteur lorsqu'il y a du matériel de formation ou de la documentation, comme les procédures normales d'exploitation des dictionnaires de données liés à l'objet en question, et cela n'implique aucun risque de confusion pour les utilisateurs lors de la modification des métadonnées qui leur sont familières. Au même moment, la modification de l'objet du fichier .json signifie que l'utilisation de la documentation et du matériel de formation associés pourrait devenir plus compliquée. + +Notez que pour les deux options 1 et 2, la modification peut être aussi simple que l'ajout d'un petit pré/post-fixe au nom, pour minimiser le risque de confusion. + +#### Option 3 { #alternative-3 } + +Une troisième approche, plus complexe, consiste à modifier le fichier .json pour réutiliser les métadonnées existantes. Par exemple, dans les cas où un indicateur existe déjà pour un certain concept (par exemple "Couverture de CPN 1"), cet indicateur pourrait être supprimé du fichier .json et toutes les références à son UID remplacées par l'indicateur correspondant existant déjà dans la base de données. Le grand avantage de cette méthode (qui n'est pas limitée aux seuls cas où il y a un conflit d'importation direct) est d'éviter de créer des métadonnées en double dans la base de données. Cependant, elle n'est généralement pas recommandée pour plusieurs raisons : + +* il nécessite une connaissance approfondie de la structure détaillée des métadonnées du DHIS2 +* Cette approche ne fonctionne pas pour tous les types d'objets. En particulier, certains types d'objets ont des dépendances compliquées à résoudre de cette manière, par exemple en ce qui concerne les désagrégations. +* comme pour l'option 2, cela signifie que le résultat de l'installation n'est pas entièrement conforme à la configuration standard, et que le matériel de formation et la documentation élaborés pour cette configuration pourraient ne pas être utilisables sans modifications. +* il sera compliqué de procéder aux futures mises à jour du package de configuration. + +## Configuration supplémentaire { #additional-configuration } + +Une fois que toutes les métadonnées ont été importées avec succès, le module devrait être utilisable avec seulement quelques ajustements mineurs supplémentaires. En outre, en fonction de l'instance DHIS2 dans laquelle le module a été importé, une configuration et des modifications supplémentaires peuvent être nécessaires ou avantageuses. Cette section passera d'abord en revue les étapes de configuration nécessaires, puis fera part de certains des autres types de modifications ou de configuration qui pourraient être utiles. + +## Configuration requise { #required-configuration } + +Avant que les packages de configuration puissent être utilisés pour la collecte de données, deux étapes sont nécessaires. + +* Affecter le ou les ensemble(s) de données aux unités d'organisation appropriées +* Partager le ou les ensemble(s) de données avec les groupes d'utilisateurs appropriés +* Ajouter votre/vos utilisateur(s) aux groupes d'utilisateurs appropriés + +Les ensembles de données doivent être affectés aux unités d'organisation (établissements) censées faire rapport sur cet ensemble de données particulier. + +Les ensembles de données et les options de catégories doivent également être partagés avec le ou les groupe(s) d'utilisateurs concernés du personnel chargé de la saisie des données pour ces ensembles de données. + +### Partage { #sharing } + +Tout d'abord, vous devrez utiliser la fonctionnalité *Partage* de DHIS2 pour configurer quels utilisateurs (groupes d'utilisateurs) doivent voir les métadonnées et les données associées au programme ainsi que qui peut enregistrer/saisir des données dans le programme. La fonctionnalité Partage doit être configurée pour ce qui suit : + +* Éléments de données/Groupes d'éléments de données +* Indicateurs/Groupes d'indicateurs +* Ensembles de données +* Tableaux de bord + +Trois groupes d'utilisateurs sont inclus dans le package : + +* COVID19 Accès +* COVID19 Administrateur +* COVID 19 Saisie de données + +Nous recommandons l'accès suivant + +|Objet|Groupe d'utilisateurs||| +|--|--|--|--| +||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| +|_Éléments de données/groupe d’éléments de données_.|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : peuvent être visualisées
Données : peuvent être visualisées| +|_Indicateurs/groupes d’indicateurs_.|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : peuvent être visualisées
Données : peuvent être visualisées| +|_Ensembles de données_|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : affichage autorisé
Données : saisie et affichage autorisés | +|_Tableaux de bord_|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : peuvent être visualisées
Données : peuvent être visualisées| + +### Métadonnées dupliquées { #duplicated-metadata } + +Même lorsque les métadonnées sont importées avec succès sans aucun conflit d'importation, il peut y avoir des doublons dans les métadonnées - qu'il s'agisse d'un graphique, d'un indicateur, d'un élément de données ou d'une catégorie d'éléments de données qui existe déjà. Comme indiqué dans la section ci-dessus sur la résolution des conflits, il est important de garder à l'esprit que les décisions relatives à la modification des métadonnées dans DHIS2 doivent également tenir compte d'autres documents et ressources associés de différentes manières aux métadonnées existantes et aux métadonnées importées par le biais du package de configuration. La résolution des doublons ne consiste donc pas seulement à "nettoyer la base de données", mais aussi à s'assurer que cela est fait sans, par exemple, briser le potentiel d'intégration avec d'autres systèmes, la possibilité d'utiliser du matériel de formation, la violation des procédures, etc. Cela dépend beaucoup du contexte. + +Une chose importante à garder à l'esprit est que le DHIS2 dispose d'outils pouvant dissimuler certaines des complexités des duplications potentielles dans les métadonnées. Par exemple, lorsqu'il existe des catégories d'éléments de données en double, ces doublons peuvent être masqués aux utilisateurs finaux grâce à des ensembles de groupes d'options de catégories, ou certains objets de métadonnées peuvent être masqués pour des groupes d'utilisateurs à travers l'option de partage. + +Il est recommandé de ne pas supprimer ou remplacer les indicateurs inclus dans les packages de configuration même si le même indicateur existe déjà, afin de pouvoir conserver les résultats analytiques (qui, eux, reposent exclusivement sur des indicateurs). Cela permettra de réutiliser le matériel de formation basé sur les packages de configuration. + +## Exemples d'autres modifications { #examples-of-other-modifications } + +Outre la configuration requise, il existe plusieurs autres modifications et configurations qui peuvent s'avérer utiles, en fonction de la situation spécifique. Il ne sera pas possible de fournir des orientations et des recommandations couvrant tous les différents scénarios, mais nous présentons ici une brève discussion de certains problèmes courants. + +### Les traductions { #translations } + +Des traductions supplémentaires pourraient être ajoutées, si d'autres langues que celles incluses sont nécessaires. + +### Ajout de variables supplémentaires { #adding-additional-variables } + +Les packages de configuration comprennent les principaux éléments de données et indicateurs recommandés. Toutefois, il peut être nécessaire dans certains cas d'ajouter des variables supplémentaires pour répondre aux besoins d'information spécifiques à chaque pays. Ces variables peuvent être ajoutées aux ensembles de données inclus. + +### Mise à jour de la présentation des formulaires de déclaration { #updating-layout-of-reporting-forms } + +Pour faciliter le travail du personnel chargé de la saisie des données dans DHIS2, il est parfois souhaitable d'ajouter un formulaire de saisie personnalisé qui correspond au format des formulaires papier utilisés au premier niveau. + +## Maintenance { #maintenance } + +Aucune maintenance particulière n'est requise pour les packages de configuration, puisqu'ils sont constitués de métadonnées standard de DHIS2. Toutefois, avant de passer aux nouvelles versions de DHIS2, il est important de tester toutes les fonctionnalités du système en général sur un serveur de test ou de préproduction avant la mise à niveau des instances de production du système. + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md new file mode 100644 index 00000000..c60b8ef3 --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/overview.md" +revision_date: '2023-03-07' +tags: +- Implémentation +--- + +# COVID-19 Aggregate Surveillance { #covid-19-aggregate-surveillance } + +## Note de mise à jour { #release-note } + +- [Release Note](#c19-agg-release-note) + +## Conception { #design } + +- [Version 2.0.0](#c19-agg-design) + +## Installation { #installation } + +- [Installation Guide](#c19-agg-installation) + +## Référence des métadonnées { #metadata-reference } + +- [Version 2.0.0](https://packages.dhis2.org/en/C19_AGG/2.0.0/DHIS2.39/C19_AGG_COMPLETE_2.0.0_DHIS2.39.xlsx) + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md new file mode 100644 index 00000000..2c4893b1 --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md @@ -0,0 +1,26 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implémentation +--- + +# Release Note { #c19-agg-release-note } + +To see additional details of the metadata objects mentioned below, refer to the metadata reference documentation of the relevant version. + +## 2.0.0 { #200 } + +* The changes leading to this version were based on the revised [WHO Global surveillance of COVID-19 Weekly Aggregate Report ](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) +* The major were made on the age disaggregations with 5 year age bands used for <20 years and 60+ years spanning upto 80+years. +* Unknown age and Unknown sex were also introduced in the disaggregations to cater data that cannot be categorized with the options provided. +* Data elements for cases and deaths among health workers (Confirmed + Probable), tests with PCR assay, deaths amongst probable cases and health workers were introduced in this version. +* Data elements for logistics and cases by transmission classifications were removed. +* Considering these changes, all the core metadata objects; data elements, indicators, dashboard and its items, dataSets, indicator groups and data elements groups were newly created. +* This version now has only one dataSet designed for weekly reporting unlike in the previous version that had 2 dataSets reported weekly and daily basis. +* All the core metadata objects have been coded in support for international standard for aggregate data exchange (ADX). + +## 1.0.0 { #100 } + +Initial release of COVID-19 Aggregate Surveillance package + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md new file mode 100644 index 00000000..18fa64cb --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -0,0 +1,291 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-design.md" +revision_date: '2022-09-13' +tags: +- Implémentation +--- + +# COVID-19 Case Surveillance & Contact Tracing Design { #c19-cs-design } + +Demo: [https://demos.dhis2.org/covid-19](https://demos.dhis2.org/covid-19) + +## Objectif { #purpose } + +Le document "Conception du système de surveillance du COVID-19" donne un aperçu du design conceptuel utilisé dans la configuration d'un ensemble de données numériques du COVID-19 dans le DHIS2. Le paquet COVID-19 a été développé en réponse à un besoin exprimé par les pays d'adapter rapidement une solution de gestion des données du COVID-19. Ce document est destiné aux responsables de la mise en œuvre du DHIS2 au niveau national et régional pour soutenir la mise en œuvre et la localisation du progiciel. Le progiciel de métadonnées de COVID-19 peut être adapté aux besoins locaux et aux directives nationales. Les flux de travail locaux et les lignes directrices nationales doivent être en particulier pris en compte lors de la localisation et de l'adoption des programmes inclus dans ce progiciel. + +## Contexte { #background } + +**This design has been updated to reflect new aggregate reporting requirements from the [WHO interim surveillance guidelines updated March 20, 2020][1]**. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| Type de Package de surveillance | Case Surveillance (Tracker) | Surveillance (Événement) | Surveillance (Agrégat ) | +|---|---|---|---| +| ***Description*** | Permet d'enregistrer un cas et de le suivre dans le temps grâce à la confirmation en laboratoire et au résultat relatif au cas | Permet de saisir les détails relatifs à un cas critique sous forme de liste de lignes | Permet la déclaration quotidienne ou hebdomadaire des principaux points de données agrégées | +| ***Avantages*** | La grande granularité des données et les multiples dimensions temporelles de l'analyse peuvent permettre de décentraliser le flux de travail c'est-à-dire tous les événements liés au cas. | Caractéristique plus granulaire qu'agrégée et pouvant saisir les principales dimensions temporelles (c'est-à-dire la date du rapport par rapport à l'apparition des symptômes) ; réduction de la charge de saisie des données par rapport au tracker et niveau de complexité peu élevé | Peu complexe, facile à mettre en œuvre, plus facile à gérer lorsque le nombre de cas est élevé | +| ***Inconvénients*** | Le volume de données à saisir peut être écrasant lorsque le nombre de cas atteint le seuil ; ceci peut rendre la mise en œuvre complexe | Ne prend pas en charge le suivi des cas ou d'autres flux de travail décentralisés | Une granularité plus faible pour l'analyse détaillée (c'est-à-dire une analyse basée exclusivement sur la date de notification du cas, une désagrégation limitée) | + +**Ce document ne couvre que la conception de l'ensemble du programme de suivi de la surveillance** ; des documents de conception de système distincts sont disponibles pour les ensembles d'événements et d'agrégats de DHIS2. + +L'OMS "exhorte tous les pays à se préparer à l'arrivée éventuelle de COVID-19 en préparant des systèmes d'intervention d'urgence, en augmentant la capacité à détecter et à soigner les patients, en veillant à ce que les hôpitaux disposent de l'espace, du matériel et du personnel nécessaires et en mettant au point des interventions médicales visant à sauver des vies". + +Les objectifs du progiciel de surveillance du COVID-19 sont les suivants : + +1. surveiller les tendances de la maladie là où il y a transmission interhumaine ; +2. détecter rapidement les nouveaux cas dans les pays où il n'y a pas de circulation du virus ; +3. fournir des informations épidémiologiques pour effectuer des évaluations des risques aux niveaux national, régional et mondial ; et +4. fournir des informations épidémiologiques pour orienter les mesures de préparation et d'intervention. + +The system design builds upon existing case disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 surveillance package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions][2], updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## Résumé de la conception du système { #system-design-summary } + +The DHIS2 case surveillance tracker metadata was based on the **[WHO COVID-19 case reporting template][3]** and the mapping of data dictionaries can be accessed at: [DHIS2 CBS tracker metadata WHO line-list data dictionary][4]. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles][5] and a common [naming convention][6]. + +Le package de données numériques de la COVID-19 prend en charge les flux de travail de surveillance et l'analyse automatisée des éléments clés de la surveillance de routine et active. Ce paquet comprend un système de suivi de la surveillance des cas ainsi qu'un système d'enregistrement et de suivi des contacts, installés ensemble dans le même progiciel de métadonnées. Les programmes de suivi sont optimisés pour être installés avec d'autres progiciels de surveillance de COVID-19, notamment le programme de suivi du contrôle aux points d'entrée et l'ensemble de données de surveillance quotidiennes agrégées. + +1. **[Use Case 1: COVID-19 Case surveillance tracker][7]**: enrols & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. Metadata for the case surveillance tracker is aligned with the WHO [COVID-19 surveillance data dictionary][8] + + > n.b. The COVID-19 case tracker can be implemented either as a ‘standalone’ program for COVID-19 specific disease surveillance as described here; or, COVID-19 concepts can be integrated into an existing case surveillance tracker program if one already exists in-country. Please refer to installation and implementation guidance for more details. + +1. **[Use Case 2: Contact registration & follow-up][9]**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. + +Digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [Google Play store][10]. + +## Use Case 1: COVID-19 Case surveillance tracker { #use-case-1-covid-19-case-surveillance-tracker } + +The COVID-19 case surveillance tracker can be adapted and used by countries to supplement existing national disease surveillance programs. The basic case surveillance program is designed to: + +1. Enroll suspected\* COVID-19 cases (*generally appearing at a health facility, but may be enrolled at other places*) +2. Saisir les informations clés sur le cas suspect, y compris les données démographiques et les expositions, telles que les symptômes, les contacts avec un cas précédemment confirmé et les antécédents de voyage +3. Générer des demandes d'analyse de laboratoire +4. Enregistrer le diagnostic du laboratoire +5. Enregistrer les contacts d'un cas confirmé\*\* ou probable\*\*\* pour suivi +6. Enregistrer les résultats d'analyse de cas +7. Faciliter la notification des cas et le signalement des cas au niveau national/régional/global +8. Générer des tableaux de bord et des outils d'analyse pour suivre les tendances des maladies et planifier les interventions + +The design of the case tracker program assumes that [WHO case definitions][1] are followed in the use case; its use can be adapted to local case definitions as needed. The WHO case definitions were updated on March 20, 2020 and noted below. + +> \* Suspected case: A) a patient with acute respiratory illness (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness of breath), AND with no other aetiology that fully explains the clinical presentation AND a history of travel to or residence in a country/area or territory reporting local transmission of COVID-19 disease during the 14 days prior to symptom onset; **OR**, B) A patient with any acute respiratory illness AND having been in contact with a confirmed or probable COVID-19 case (see definition of contact) in the last 14 days prior to onset of symptoms; **OR,** C) A patient with severe acute respiratory infection (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness breath) AND requiring hospitalization AND with no other aetiology that fully explains the clinical presentation. +> +>\*\* Probable case: A) a suspect case for whom testing for COVID-19 is inconclusive (inconclusive being the result of the test reported by the laboratory) **OR,** B) a suspect case for whom testing could not be performed for any reason. +> +>\*\*\* Confirmed case: A person with laboratory confirmation of COVID-19 infection, irrespective of clinical signs and symptoms. + +### Utilisateurs cibles { #intended-users } + +* Utilisateurs des établissements de santé : saisie et enregistrement des détails relatifs à un cas suspect, y compris les symptômes cliniques et les expositions ; suivi des résultats de laboratoire ; enregistrement des résultats d'analyse du cas +* Utilisateurs de laboratoire : reçoivent les demandes d'analyses de laboratoire et enregistrent résultat d'analyses de laboratoire pour un cas suspect particulier +* Autorités sanitaires nationales et locales : suivi et analyse des données de surveillance des maladies au moyen de tableaux de bord et d'outils d'analyse permettant de réaliser des évaluations des risques et de planifier les interventions ; production de rapports en vue des rapports régionaux et global + +### Workflow: COVID-19 Case Surveillance Tracker { #workflow-covid-19-case-surveillance-tracker } + +![Workflow of the DHIS2 COVID-19 Case Surveillance Tracker](resources/images/sdd-tracker-v3-case1-workflow.png) + +### Structure : Programme de suivi de la surveillance des cas du COVID-19 { #structure-covid-19-case-surveillance-tracker-program } + +![Structure of the COVID-19 Case Surveillance Tracker Program](resources/images/sdd-tracker-v3-case1-structure-v2.png) + +#### Description du programme : COVID-19 : test de cas, diagnostic et résultats { #program-description-covid-19-case-testing-diagnosis-outcome } + +| Étape | Description | +|---|---| +| **Détails de l'inscription et Attributs** | The Tracked Entity is the case, which is represented by a Tracked Entity Type of ‘person.’ The *Enrollment date* is the date of registration of the case. The Related programs is *COVID-19 Contact registration & follow-up*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *Age*, *First Name*, *Surname*, *Sex*, *Case phone number*, *First Name (parent or care)*, *Surname (parent or carer)*, *Home Address*, *Workplace/school physical address*, *Country of Residence*, *Facility contact number*| +| **Étape 1 : Examen clinique et expositions** | This stage records a suspected case’s clinical symptoms and exposures including: *Symptoms*, *Pregnancy and underlying conditions*, *Hospitalisation and Isolation*, *Exposures in 14 days prior to symptoms*, *Travel history*, *Contact with confirmed case*. After examination, you can record if the case has been hospitalised or isolated, and information surrounding this. | +| **Étape 2 : Demande d'analyse [reproductible]** | La demande d'analyse indique la raison des tests ainsi que toute autre information dont un laboratoire a besoin pour traiter un échantillon et le tester pour la COVID19. Les informations fournies ici peuvent aider le personnel du laboratoire à établir un ordre de priorité pour les tests de laboratoire lorsque les ressources sont limitées. L'agent chargé de saisir ces données peut être la même que celui ayant enregistré le cas suspect et consigné l'examen clinique et les expositions du patient ; il peut également s'agir d'un autre membre du personnel chargé de traiter les demandes d'analyse. | +| **Étape 3 : Résultats d'analyses de laboratoire [reproductibles]** | L'étape consacrée aux résultats de laboratoire permet d'enregistrer le type et les résultats des tests de laboratoire. Elle peut être réalisée directement au laboratoire ou comme deuxième saisie de données. Cette étape est répétable puisque les échantillons pour un cas donné peuvent être testés plusieurs fois (c'est-à-dire que dans le cas de résultats de laboratoire non concluants, un nouveau test de laboratoire peut être effectué et les résultats enregistrés). | +| **Étape 4 : Résultats cliniques** | Le résultat clinique indique le résultat médical final du cas : (guéri, non guéri, mort ou inconnu), y compris la date de sortie ou de décès, selon le cas. | + +#### Enrollment Stage { #enrollment-stage } + +![Enrollment](resources/images/sdd-tracker-v3-case1-enrollment.png) + +#### Étape 1 du programme - Examen clinique et diagnostic { #program-stage-1-clinical-examination-diagnosis } + +##### Section 1 - Signes et symptômes cliniques { #section-1-clinical-signs-and-symptoms } + +En sélectionnant "oui" à l'élément de donnée 'Signes ou symptômes ?', vous découvrirez les autres options. + +![Section 1](resources/images/sdd-tracker-v3-case1-stage1-section1.png) + +##### Section 2 - Détails sur la grossesse { #section-2-pregnancy-details } + +Cette section est masqée si le sexe sélectionné est "Femme". + +![Section 2](resources/images/sdd-tracker-v3-case1-stage1-section2.png) + +##### Section 3 - Conditions sous-jacentes/comorbidité { #section-3-underlying-conditionscomorbidity } + +The details of this section are hidden unless “Any underlying conditions” is marked as “Yes”. + +![Section 3](resources/images/sdd-tracker-v3-case1-stage1-section3.png) + +##### Section 4 - Hospitalisation { #section-4-hospitalisation } + +The details of this section is hidden unless “Hospitalised” is marked as “Yes”. + +![Section 4](resources/images/sdd-tracker-v3-case1-stage1-section4.png) + +##### Section 5 - Risque d'exposition { #section-5-exposure-risk } + +This section is used to record exposures + + 1. The fields ***country, city and facility*** are hidden by program rules if the case is not a health care worker; + 2. The fields for contact IDs are hidden by program rules if the case has not had contact with a confirmed case in 14 days. + +A suspected case’s exposure to a *previously confirmed* case is distinct from prospective contact tracing in Program Stage 5. + +![Section 5](resources/images/sdd-tracker-v3-case1-stage1-section5.png) + +##### Section 6 - Antécédents de voyage { #section-6-travel-history } + +![Section 6](resources/images/sdd-tracker-v3-case1-stage1-section6.png) + +#### Étape 2 du programme : Demande d'analyses de laboratoire { #program-stage-2-lab-request } + +![Stage 2](resources/images/sdd-tracker-v3-case1-stage2.png) + +#### Étape 3 : Résultats d'analyses de laboratoire { #stage-3-lab-results } + +![Stage 3](resources/images/sdd-tracker-v3-case1-stage3.png) + +#### Étape 4 : Résultats cliniques { #stage-4-health-outcomes } + +![Stage 4](resources/images/sdd-tracker-v3-case1-stage4.png) + +### Règles du programme : Suivi de la surveillance des cas de COVID19 { #program-rules-covid19-case-surveillance-tracker } + +The following program rules have been configured. If a country has an existing case surveillance program and wishes to incorporate elements of the COVID-19 case tracker into their existing program, special attention must be paid to the configuration of program rules. + +| Nom de la règle du programme | Description de la règle du programme | +|---|---| +| Assign Enrollment Date | This assigns the enrollment date if there is no onset date available to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators. | +| Assign Onset Date| This assigns the onset date to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators.| +| Calculer et attribuer l'âge du patient en années | Calculer et attribuer l'âge du patient en années selon la DDN | +| Afficher l'âge du patient en années + jours | Afficher l'âge du patient en années + jours | +| Hide Date of Death | Hide the Date of Death unless Death is the health outcome | +| Hide Date of Discharge | Hide Date of Discharge if no outcome or if the outcome is death | +| Hide Measured Temperature field | Hide Measured Temperature field until Fever is selected | +| Hide confirmed case ID's if no contact with other confirmed cases| Hides any contact ID's if the case has not been in any contact with other confirmed cases | +| Masquer les détails relatifs au personnel de santé s'il ne s'agit pas d'un professionnel des soins de santé | Masquer les détails relatifs au personnel de santé s'il ne s'agit pas d'un professionnel des soins de santé | +| Masquer l'explication relative au résultat clinique si le résultat clinique n'est pas différent | Masquer l'explication relative au résultat clinique si le résultat clinique n'est pas différent | +| Masquer les détails relatifs à l'hospitalisation si celle-ci est inexistante ou inconnue | Masquer les détails relatifs à l'hospitalisation si celle-ci est inexistante ou inconnue | +| Masquer la date d'isolement si le cas n'est pas en isolement | Masquer la date d'isolement si le cas n'est pas en isolement | +| Masquer les détails relatifs à la grossesse si la femme concernée n'est pas enceinte | Masquer les détails relatifs à la grossesse si la femme concernée n'est pas enceinte | +| Masquer la section réservée aux détails sur la grossesse si le sexe est masculin | Masquer la section réservée aux détails sur la grossesse si le sexe est masculin | +| Masquer les explications relatives aux tests effectués dans le cas où une option est sélectionnée | Masquer les explications relatives aux tests effectués dans le cas où une option est sélectionnée | +| Masquer les détails relatifs aux antécédents de voyage si aucun voyage n'a été effectué 14 jours avant l'apparition des symptômes | Masquer les détails relatifs aux antécédents de voyage si aucun voyage n'a été effectué 14 jours avant l'apparition des symptômes | +| Masquer les affections sous-jacentes si le cas n'en présente pas | Masquer les affections sous-jacentes si le cas n'en présente pas | +| Afficher un message d'avertissement si la date de l'événement est postérieure à la date de l'enregistrement | Afficher un message d'avertissement à la fin d'un événement si la date de l'événement est antérieure à la date de l'enregistrement | + +You can read more about program rules here: [https://docs.dhis2.org/master/en/user/html/configure\_program\_rule.html][11] + +### Indicateurs de programme { #program-indicators } + +À partir des données saisies dans le Programme de surveillance des cas de COVID-19, nous pouvons calculer au moins les indicateurs suivants, y compris ceux recommandés par l'OMS pour la déclaration globale quotidienne et hebdomadaire, et les présenter dans un tableau de bord : + +| Nom de l'indicateur | Description | +|---|---| +| COVID-19 - Cas traités par ventilation mécanique ou par ECMO ou admis en unité de soins intensifs (USI) | *Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU)* | +| Contacts avec des cas de COVID-19 | *Counts the number of relationships (‘has been in contact with’) created that are linked to the case TEI* | +| COVID-19 - Décès (tous les cas suspects) | *COVID-19 related deaths (deaths recorded among all suspected cases)* | +| COVID-19 - Décès (cas confirmés) | *COVID-19 related deaths (deaths recorded among confirmed cases)* | +| COVID-19 - Décès (cas probables) | *COVID-19 related deaths (deaths recorded among all probable cases)* | +| COVID-19 - Cas confirmés et hospitalisés | *Number of confirmed cases that were admitted into hospital* | +| COVID-19 - Cas importés | *Cases where likely source of infection is recorded as another country or imported from another country.* | +| COVID-19 - Cas confirmés en laboratoire | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by report date* | +| COVID-19 - Cas confirmés en laboratoire - en fonction de l'apparition des symptômes | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by date of onset of symptoms* | +| COVID-19 - Cas testés en laboratoires | *Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)* | +| COVID-19 - Cas de transmission locale | *Number of suspected cases where transmission is local (no travel in last 14 days* | +| COVID-19 - Cas probables | *Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date* | +| COVID-19 - Cas probables - en fonction de l'apparition des symptômes | *Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms* | +| COVID-19 - Cas confirmés guéris | *Number of laboratory confirmed cases with outcome recovered*| +| COVID-19 - Cas suspects | *Total number of cases suspected with COVID-19, by report date* | +| COVID-19 - Cas suspects - en fonction de l'apparition des symptômes | *Total number of cases suspected with COVID-19, by date of onset of symptoms* | +| COVID-19 - Cas suspects dont le résultat du test n'est pas positif | *Total number of suspected cases without a positive lab result* | +| COVID-19 : Nombre total de tests de laboratoire effectués | *Total number of lab tests conducted (count of tests, not cases)* | +| COVID-19 : Nombre total de tests positifs | *Total number of lab tests returned with positive results (count of tests, not cases* | +| COVID-19 : Décès par sexe et par tranche d'âge | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 : Cas confirmés par sexe et par tranche d'âge | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 : Cas suspects par sexe et groupe d'âge | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | + +## Cas d'utilisation 2 : COVID-19 Enregistrement et suivi des contacts { #use-case-2-covid-19-contact-registration-follow-up } + +This program can be used in addition to the case surveillance tracker to facilitate the registration and follow-up of contacts of a confirmed case. In this scenario, it is assumed that if any contacts of a confirmed case meet criteria for suspected case and are referred for testing, the case will be enrolled into the COVID-19 Case Surveillance tracker program. + +Le programme d'enregistrement et de suivi des contacts permet d'enregistrer chaque contact d'un cas (tel que décrit dans le cas d'utilisation de la surveillance de cas COVID-19) en tant que nouvelle instance (personne) d'entité surveillée et les relie au cas dans le programme de surveillance de cas COVID-19 via une ‘relation’. Il comporte une étape de suivi simple et reproductible où les symptômes et tout suivi entrepris peuvent être enregistrés. + +### Flux de travail : Enregistrement des contacts et suivi { #workflow-contact-registration-follow-up } + +![Worflow of the Contact registration & follow-up](resources/images/sdd-tracker-v3-case2-workflow.png) + +### Description du programme : Enregistrement des contacts et suivi { #program-description-contact-registration-follow-up } + +| Étape | Description | +|---|---| +| **Détails de l'inscription et Attributs** | The Tracked Entity is represented by a Tracked Entity Type of ‘person.’ The Related program is *COVID-19 Case based surveillance*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *First Name*, *Surname*, *Date of birth*, *Age*, *Sex*, *Phone number (local)*, *Home Address*, *Country of Residence* | +| **Étape 1 : Suivi [non reproductible]** | This stage is meant to record information related to contact tracing follow up, given that a contact has already been identified. It is divided into two sections: *1. Relation with case*, *2. Exposure Assessment* | +| **Étape 2: Symptômes[reproductibles]** | This stage is intended to record symptoms of the case. Follow-up to check on the symptoms of a contact can be repeated until the follow-up period is complete (for example, after 14 days or according to national guidelines). When follow-up period is complete, the enrollment can be ‘completed.’ *1. Symptoms*| + +Les contacts sont ajoutés au cas index en utilisant le menu des relations du programme de surveillance des cas : + +![Profile](resources/images/sdd-tracker-v3-case2-profile.png) + +Once you select “Add” from the relationships box, you are able to select the relationship and program and either select an existing person or enroll a new contact using the enrollment stage that appears. This will enroll the contact into the contact registration and follow-up +program. + +![Add a relationship](resources/images/sdd-tracker-v3-case2-add-relationship.png) + +Contacts that are added will then be listed on the case’s tracker dashboard in the relationship +widget + +![Relationships widget](resources/images/sdd-tracker-v3-case2-relationships-widget.png) + +Vous pouvez également les inscrire séparément au programme. Une fois inscrits, vous pourrez les retrouver pour le suivi nécessaire. + +#### Inscription { #enrollment } + +![iEnrollment in the use case 2](resources/images/sdd-tracker-v3-case2-enrollment-case2.png) + +#### Étape 1 du programme : Suivi { #program-stage-1-follow-up } + +![Case 2 Stage 1](resources/images/sdd-tracker-v3-case2-stage1.png) + +#### Étape 2 du programme : Symptômes { #program-stage-2-symptoms } + +![Case 2 Stage 2](resources/images/sdd-tracker-v3-case2-stage2.png) + +### Indicateurs de programme : Enregistrement des contacts { #program-indicators-contact-registration } + +| Nom de l'indicateur de programme | Description | +|---|---| +| COVID-19 : voyageurs dépistés | Nombre total de voyageurs dépistés et enregistrés au programme de dépistage au PDE | +| COVID-19 : autorisation des voyageurs au PDE | Nombre de voyageurs autorisés après le contrôle au PDE (aucun suivi requis) | +| COVID-19 : voyageurs présentant des symptômes au PDE | Nombre de voyageurs présentant des symptômes lors du contrôle au PDE | +| COVID-19 : voyageurs autorisés après 14 jours de suivi | Nombre de voyageurs autorisés après 14 jours de suivi (aucun symptôme n'est apparu pendant cette période) | +| COVID-19 : voyageurs référés à un établissement de santé | Nombre de voyageurs référés à un établissement de santé durant les 14 jours de surveillance | +| COVID-19 : voyageurs enregistrés pour un suivi de 14 jours | Nombre de voyageurs ne présentant pas de symptômes lors du dépistage au PDE et n'ayant pas été autorisés lors du dépistage au PDE | +| COVID-19 : voyageurs actuellement sous surveillance | Nombre de voyageurs non autorisés ou non référés à un établissement de santé | +| COVID-19 : les voyageurs ayant développé des symptômes lors du suivi | Nombre de voyageurs ayant développé des symptômes lors du suivi (exclure les voyageurs présentant des symptômes lors du dépistage au PDE) | + +## Références { #references } + +* Directives techniques de l'OMS sur la surveillance de la COVID-19 et les définitions de cas (dernière mise à jour le 20 mars 2020) [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* Dictionnaire de données de l'OMS en ce qui concerne le formulaire de déclaration de cas COVID-19 [https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* Dépistage en laboratoire des cas suspects d'infection humaine par le nouveau coronavirus 2019 (2019-nCoV) (dernière mise à jour le 2 mars 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* Considérations de l'OMS dans l'investigation des cas et groupes de COVID-19 (dernière mise à jour le 13 mars 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* Rapports de l'OMS sur la situation du coronavirus [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + +[1]: https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf +[2]: https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions +[3]: https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx +[4]: https://drive.google.com/open?id=1vigXHkP7L2hJ2lrZpdf9u4csQtppMH16 +[5]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html +[6]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html +[7]: #use-case-1-covid-19-case-surveillance-tracker +[8]: https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2 +[9]: #use-case-2-covid-19-Contact-registration-follow-up +[10]: https://play.google.com/store/apps/details?id=com.dhis2&hl=en +[11]: https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md new file mode 100644 index 00000000..c49bb3f4 --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-installation.md" +revision_date: '2022-09-13' +tags: +- Implémentation +--- + +# COVID-19 Surveillance - Installation Guide { #c19-cs-installation } + +## Présentation { #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: + +1. COVID-19 Programme Tracker de surveillance basée sur les cas & COVID-19 Programme d'enregistrement et de suivi des contacts +2. Programme Tracker de dépistage aux points d'entrée + +Vous devrez suivre les instructions dans leur intégralité pour chaque package que vous installez. + +## Installation { #installation } + +L'installation du module se fait en plusieurs étapes : + +1. [Préparation](#preparing-the-metadata-file) du fichier de métadonnées avec les métadonnées de DHIS2. +2. [Importation](#importing-metadata) du fichier de métadonnées dans DHIS2. +3. [Configuration](#configuration-additionnelle) des métadonnées importées. +4. [Adaptation](#adapting-the-tracker-program) du programme après son importation + +Il est recommandé de lire d'abord chaque section avant de commencer le processus d'installation et de configuration dans le DHIS2. Les sections non applicables ont été identifiées, selon que vous importiez dans une nouvelle instance de DHIS2 ou dans une instance de DHIS2 ayant déjà des métadonnées. La procédure décrite dans le présent document doit être testée dans un environnement de test et de simulation avant d'être répétée ou transférée dans une instance de production du DHIS2. + +## Conditions requises { #requirements } + +Pour installer le module, il faut nécessairement un compte d'utilisateur administrateur sur DHIS2. La procédure décrite dans le présent document doit être testée dans un environnement de test et de simulation avant d'être exécutée sur une instance de production du 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/). + +## Préparation du fichier de métadonnées { #preparing-the-metadata-file } + +**N.B.** : Si vous installez le package sur une nouvelle instance de DHIS2, vous pouvez alors ignorer la section "Préparation du fichier de métadonnées" et passer immédiatement à la section "[Importer un fichier de métadonnées dans DHIS2](#importing-metadata)". + +Bien que ce ne soit pas toujours nécessaire, il peut souvent être avantageux d'apporter certaines modifications au fichier de métadonnées avant son importation dans DHIS2. + +### Dimension de données par défaut { #default-data-dimension } + +Dans les premières versions de DHIS2, l'UID de la dimension des données par défaut était généré automatiquement. Ainsi, alors que toutes les instances du DHIS2 ont une option de catégorie par défaut, une catégorie d'élément de données, une combinaison de catégories et une combinaison d'options de catégories, les UID de ces valeurs par défaut peuvent être différents. Les versions plus récentes de DHIS2 ont des UID codés en dur pour la dimension par défaut, et ce sont ces UID qui sont utilisés dans les packages de configuration. + +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 + +|Objet|UID|Chemin vers l'API| +|--|--|--| +|Catégorie|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Option de catégorie|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Combinaison de catégories|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Combinaison d’options catégorie|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. + +Vous pourriez alors rechercher et remplacer toutes les occurrences de `HllvX50cXC0` par `bRowv6yZOF2` dans le fichier .json, puisque c'est l'ID par défaut du système dans lequel vous importez. ***Notez que cette opération de recherche et de remplacement doit être effectuée avec un éditeur de texte brut***, et non avec un logiciel de traitement de textes comme Microsoft Word. + +### Types d'indicateurs { #indicator-types } + +Le type d'indicateur est un autre type d'objet pouvant créer un conflit d'importation puisque certains noms sont utilisés dans différentes bases de données de DHIS2 ("Pourcentage", par exemple). Étant donné que les types d'indicateurs sont définis simplement par leur facteur et par le fait qu'il s'agisse ou non de simples nombres sans dénominateur, ils sont sans aucune ambiguïté et peuvent être remplacés par une recherche et un remplacement des UID. Cela permet d'éviter d'éventuels conflits d'importation et de ne pas créer de types d'indicateurs dupliqués. Le tableau 2 montre les UID qui pourraient être remplacés, ainsi que les points d'extrémité de l'API pour identifier les UID existants. + +|Objet|UID|Chemin vers l'API| +|--|--|--| +|Numérateur seulement (nombre)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Pourcentage|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| + +#### Type d'entité suivie { #tracked-entity-type } + +Comme pour les types d'indicateurs, il se peut que vous ayez déjà des types d'entités suivies dans votre base de données DHIS2. Les références au type d'entité suivie doivent être modifiées pour refléter ce qui se trouve dans votre système afin d'éviter la création de doublons. Le tableau 3 indique les UID qui pourraient être remplacés, ainsi que les points point d'extrémité de l'API permettant d'identifier les UID existants. + +|Objet|UID|Chemin vers l'API| +|--|--|--| +|Personne|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| + +## Importation de métadonnées { #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. + +### Gestion des conflits d'importation { #handling-import-conflicts } + +***N.B.*** : Si vous importez dans une nouvelle instance DHIS2, vous n'aurez pas à vous soucier des conflits d'importation, car il n'y a rien dans la base de données que vous importez qui puisse entrer en conflit avec celle-ci. Suivez les instructions pour importer les métadonnées, puis passez à la section "[Configuration supplémentaire](#configuration-supplémentaire)". + +Plusieurs de conflits peuvent survenir, mais le plus courant est le fait qu'il y ait des objets de métadonnées dans le package de configuration avec un nom, un nom abrégé et/ou un code existant déjà dans la base de données cible. Il existe plusieurs solutions alternatives à ces problèmes, avec de différents avantages et inconvénients. La solution la plus appropriée dépendra, par exemple, du type d'objet pour lequel un conflit survient. + +#### Option 1 { #alternative-1 } + +Renommez l'objet de votre base de données de DHIS2 pour lequel il y a un conflit. L'avantage de cette approche est que vous n'avez pas besoin de modifier le fichier .json, puisque les modifications sont effectuées par l'interface utilisateur de DHIS2. Cette méthode est probablement moins sujette aux erreurs. Cela signifie également que le package de configuration est laissé tel quel, ce qui peut être un avantage, par exemple, lorsque du matériel de formation et de la documentation basés sur le package de configuration seront utilisés. + +#### Option 2 { #alternative-2 } + +Renommez l'objet pour lequel il y a un conflit dans le fichier .json. L'avantage de cette approche est que les métadonnées DHIS2 existantes sont laissées telles quelles. Cela peut être un facteur lorsqu'il y a du matériel de formation ou de la documentation, comme les procédure normale d'exploitation des dictionnaires de données liés à l'objet en question, et cela n'implique aucun risque de confusion pour les utilisateurs lors de la modification des métadonnées qui leur sont familières. + +Notez que pour les deux options 1 et 2, la modification peut être aussi simple que l'ajout d'un petit pré/post-fixe au nom, pour minimiser le risque de confusion. + +#### Option 3 { #alternative-3 } + +Une troisième approche, plus complexe, consiste à modifier le fichier .json pour réutiliser les métadonnées existantes. Par exemple, dans les cas où un ensemble d'options existe déjà pour un certain concept (par exemple "sexe"), cet ensemble d'options pourrait être supprimé du fichier .json et toutes les références à son UID remplacées par l'ensemble d'options correspondant existant déjà dans la base de données. Le grand avantage de cette méthode (qui n'est pas limitée aux seuls cas où il y a un conflit d'importation directe) est d'éviter de créer des métadonnées dupliquées dans la base de données. Il y a des aspects essentiels à prendre en compte lors de ce type de modification : + +* il nécessite une connaissance approfondie de la structure détaillée des métadonnées du DHIS2 +* Cette approche ne fonctionne pas pour tous les types d'objets. En particulier, certains types d'objets ont des dépendances compliquées à résoudre de cette manière, par exemple en ce qui concerne les désagrégations. +* il sera compliqué de procéder aux futures mises à jour du package de configuration. + +## Configuration supplémentaire { #additional-configuration } + +Une fois que toutes les métadonnées sont importées avec succès, des étapes doivent être mises en oeuvre avant que le module ne soit fonctionnel. + +### Partage { #sharing } + +Tout d'abord, vous devrez utiliser la fonctionnalité *Partage* de DHIS2 pour configurer quels utilisateurs (groupes d'utilisateurs) doivent voir les métadonnées et les données associées au programme ainsi que qui peut enregistrer/saisir des données dans le programme. Par défaut, le partage a été configuré pour ce qui suit : + +* Type d'entité suivie +* Programme +* Étapes du programme +* Tableaux de bord + +Trois groupes d'utilisateurs sont inclus dans le package : + +* COVID19 Accès +* COVID19 Administrateur +* COVID 19 Saisie de données + +Les éléments suivants sont attribués par défaut à ces groupes d'utilisateurs + +|Objet|Groupe d'utilisateurs||| +|--|--|--|--| +||_COVID19 access_|_COVID19 admin_|_COVID19 data capture_| +|_*Type d’entité suivie*_.|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : peuvent être visualisées
Données : peuvent être capturées et visualisées| +|_*Programme*_|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : peuvent être visualisées
Données : peuvent être capturées et visualisées| +|_*Étapes du programme*_|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : peuvent être visualisées
Données : peuvent être capturées et visualisées| +|_*Tableaux de bord*_.|Métadonnées : peuvent être visualisées
Données : peuvent être visualisées|Métadonnées : peuvent être modifiées et visualisées
Données : peuvent être visualisées |Métadonnées : peuvent être visualisées
Données : peuvent être visualisées| + +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. + +### Rôles des utilisateurs { #user-roles } + +Les utilisateurs auront besoin de rôles utilisateur pour pouvoir utiliser les différentes applications du DHIS2. Les rôles minimums suivants sont recommandés : + +1. Analyse des données Tracker : Il peut visualiser des analyses d'événements et accéder à des tableaux de bord, des rapports d'événements, un visualiseur d'événements, un visualiseur de données, des tableaux croisés dynamiques, des rapports et des cartes. +2. Saisie de données Tracker : possibilité d'ajouter des valeurs de données, de mettre à jour les entités suivies, de rechercher des entités suivies dans les unités d'organisation et d'accéder à l'application Saisie Tracker + +Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. + +### Unités d’organisation { #organisation-units } + +Vous devez assigner le programme à des unités d'organisation au sein de votre propre hiérarchie afin de pouvoir le visualiser dans Saisie Tracker. + +### Métadonnées dupliquées { #duplicated-metadata } + +**N.B.** : Cette section ne s'applique que si vous importez dans une base de données DHIS2 ayant déjà des méta-données. Si vous travaillez avec une nouvelle instance de DHIS2, veuillez ignorer cette section et aller à [Adapter le programme tracker] (#adapter-le-programme-de-suivi)". + +Même lorsque les métadonnées sont importées avec succès sans aucun conflit d'importation, il peut y avoir des doublons dans les métadonnées - éléments de données, attributs d'entités suivies ou ensembles d'options qui existent déjà. Comme indiqué dans la section ci-dessus sur la résolution des conflits, il est important de garder à l'esprit que les décisions relatives à la modification des métadonnées dans le DHIS2 doivent également tenir compte d'autres documents et ressources associés de différentes manières aux métadonnées existantes et aux métadonnées importées par le biais du package de configuration. La résolution des doublons ne consiste donc pas seulement à "nettoyer la base de données", mais aussi à s'assurer que cela est fait sans, par exemple, briser le potentiel d'intégration avec d'autres systèmes, la possibilité d'utiliser du matériel de formation, la rupture des SOP, etc. Cela dépend beaucoup du contexte. + +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). + +## Adaptation du programme tracker { #adapting-the-tracker-program } + +Une fois le programme importé, il est possible que vous souhaitiez y apporter certaines modifications. Voici quelques exemples d'adaptations locales que vous *pourrez* effectuer : + +* Ajout de variables supplémentaires au formulaire. +* Adaptation des noms des éléments de données/options en fonction des usages au niveau national. +* Ajout des traductions aux variables et/ou au formulaire de saisie des données. +* Modification des indicateurs du programme en fonction des définitions de cas locales + +Toutefois, il est fortement recommandé de faire preuve d'une grande prudence si vous décidez de modifier ou de supprimer l'un des formulaires/métadonnées inclus. Il y a donc un risque que des modifications brisent des fonctionnalités, par exemple les règles du programme et les indicateurs du programme. + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md new file mode 100644 index 00000000..224e318c --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md @@ -0,0 +1,29 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/overview.md" +revision_date: '2022-11-22' +tags: +- Implémentation +--- + +# COVID-19 Case Surveillance { #covid-19-case-surveillance } + +## Note de mise à jour { #release-note } + +- [Release Note](#c19-cs-release-note) + +## Conception { #design } + +- [Version 1.0.2](#c19-cs-design) + +## Installation { #installation } + +- [Installation Guide](#c19-cs-installation) + +## Référence des métadonnées { #metadata-reference } + +- [Version 1.0.2](https://packages.dhis2.org/en/C19_CS/1.0.2/C19_CS_COMPLETE_1.0.2_DHIS2.37.xlsx) + +## Training Material { #training-material } + +- [COVID-19 Training Material](https://dhis2.org/covid-training-material) + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..06434954 --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implémentation +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Présentation { #overview } + +Nous avons procédé à plusieurs mises à jour du paquet existant pour l'aligner sur les nouvelles directives de surveillance COVID-19 [publiées par l'OMS le 20 mars 2020] (https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) et avons introduit de nouveaux éléments dans le paquet de soutien. Pour toute question, veuillez consulter les notes ici et nous contacter sur le forum de discussion COVID-19 dans la [communauté de pratique] (https://community.dhis2.org/c/implementation/covid-19/). + +**Tous les paquets de métadonnées et la documentation peuvent être téléchargés à partir de [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. + +La nouvelle version comprend : + +1. COVID-19 Case-based Surveillance Tracker program +2. COVID-19 Contact Registration & Follow-Up program +3. COVID-19 Rapport de surveillance globale +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Codes de métadonnées mis à jour afin de s'accorder avec [dictionnaire des données de déclaration basée sur des cas de l'OMS] (https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Les indicateurs de programme ont été mis à jour pour refléter les nouvelles définitions de cas de l'OMS pour les cas probables (référence aux définitions de cas mises à jour dans les directives de surveillance provisoires mises à jour le 20 mars 2020 [Directives de surveillance provisoires de l'OMS mises à jour le 20 mars 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Les légendes d'âge ont été mises à jour pour répondre aux nouvelles directives de l'OMS relatives à la déclaration hebdomadaire +4. Type de relation ajouté au progiciel de métadonnées +5. Modifications mineures apportées aux métadonnées pour faciliter l'installation du paquet (c'est-à-dire que l'indicateur de type UID correspond au type d'indicateur inclus dans l'ensemble d'agrégation) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. Une nouvelle étape du programme a été ajoutée pour permettre un "suivi" reproductible d'un cas de contact. Elle a été ajoutée pour refléter les flux de travail mis en œuvre en Ouganda et au Togo, où les contacts peuvent être régulièrement suivis pendant 14 jours pour déterminer s'il existe des symptômes. Le ***programme*** est basé sur les directives de l'OMS que pouvez consulter [ici](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), ainsi que sur les informations obtenues via le site web [OpenWHO](https://openwho.org/courses/introduction-to-ncov) +2. Les légendes d'âge ont été mises à jour pour répondre aux nouvelles directives de l'OMS relatives à la déclaration hebdomadaire +3. Type de relation ajouté au progiciel de métadonnées +4. Modifications mineures apportées aux métadonnées pour faciliter l'installation du paquet + +### COVID-19 Rapport de surveillance globale { #covid-19-aggregate-surveillance-reporting } + +Les mises à jour suivantes ont été effectuées pour tenir compte des nouvelles orientations contenues dans les [lignes directrices de l'OMS mises à jour le 20 mars 2020] (https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), y compris la mise à jour des rapports globaux à l'OMS (hebdomadaires et quotidiens) + +1. Les catégories d'âge sont mises à jour en fonction des nouvelles tranches d'âge +2. De nouveaux indicateurs ont été ajoutés en ce qui concerne la proportion d'hommes parmi les cas confirmés et la proportion d'hommes parmi les décès confirmés +3. Le nouvel ensemble de données hebdomadaires pour saisir la classification de la transmission au premier niveau infranational (c'est-à-dire provincial -- peut être attribué à n'importe quel niveau infranational selon le cas dans le pays) selon les directives actualisées de l'OMS en matière de déclaration hebdomadaire +4. Modifications mineures apportées aux métadonnées pour faciliter l'installation du paquet + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +Le cas d'utilisation du Programme Tracker des points d'entrée a été conçu dans le but de soutenir l'enregistrement des voyageurs entrant dans un pays ayant des antécédents de voyage ou de résidence dans un pays/une région/un territoire qui signalent une transmission locale de COVID-19 et qui peuvent avoir besoin d'être suivis pour s'assurer qu'aucun symptôme ne se développe. Il est basé sur la conception mise en œuvre par HISP Sri Lanka pour soutenir le ministère de la Santé du Sri Lanka avec des changements mineurs visant à rendre le programme plus générique en vue d'une utilisation mondiale et pour s'aligner sur les autres programmes Tracker du paquet COVID-19. Le programme vient en appui aux interventions aux points d'entrée détaillées dans les [directives techniques de l'OMS pour la gestion des personnes malades aux points d'entrée] (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/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md new file mode 100644 index 00000000..1810bc5f --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -0,0 +1,136 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/c19_poe-design.md" +revision_date: '2022-07-05' +tags: +- Implémentation +--- + +# COVID-19 Points of Entry Tracker Design { #c19-poe-design } + +Demo: [https://covid19.dhis2.org/](https://covid19.dhis2.org/demo) + +## Objectif { #purpose } + +The COVID-19 Points of Entry (POE) Screening System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Contexte { #background } + +The Points of Entry Screening Tracker is inspired by the pioneering design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health. In January 2020, the Sri Lanka MOH implemented screening measures at ports of entry like airports to identify travelers who may have been exposed to nCoV-19. DHIS2 tracker was to enroll travelers entering Sri Lanka who had visited countries impacted by COVID-19. DHIS2 tracker enabled follow-up with travelers at field level for 14 days to ensure no symptoms developed. If symptoms developed, travelers would be referred to a health facility for clinical examination and testing. The POE tracker can be used in combination with other COVID-19 digital data packages that include case surveillance and contact tracing. + +The World Health Organisation (WHO) has published [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). Points of entry (POE) include international airports, seaports and land crossings. POE measures include 1) detection of ill travellers; 2) interview of ill travellers for COVID-19; 3) reporting of alerts of ill travellers with suspected COVID-19 infection and 4) isolation, initial case management and referral of ill travellers with suspected COVID-19 infection. These guidelines should be consulted, in addition to national protocols for points of entry. + +## Résumé de la conception du système { #system-design-summary } + +### Cas d'utilisation { #use-case } + +The POE tracker program use case was designed to support the registration of travelers 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. For this use case, it is assumed that a traveler may be 1) screened and cleared immediately with no follow-up needed; 2) screened and followed up for 14 days [with or without isolation measures] to ensure no symptoms develop; or 3) screened and referred for testing and/or initial case management. The current design proposes that a traveler meeting the country’s definition of a suspected case would be enrolled into the complementary DHIS2 COVID-19 Case-Based Surveillance (CBS) Tracker. For example, a traveler enrolled in this program who later meets the definition of a suspected case during follow-up (i.e. an asymptomatic traveler from a country with known transmission is registered at the POE and later develops symptoms) is enrolled as a suspected case into the COVID-19 CBS program to capture all clinical details, exposures and follow the case through laboratory diagnosis and case outcome. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +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). + +### Utilisateurs cibles { #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. +* National and local health authorities: monitor and analyse data through dashboards and analytics tools to conduct risk assessments and plan response measures. + +### Déroulement { #workflow } + +The Points of Entry program workflow is based on the following scenario + +![Scenario](resources/images/POE_image01.png "Scenario") + +In this design, it is assumed a traveler would complete their enrollment in the POE under the following scenarios: + +1. Traveler is marked as ‘cleared’ during initial screening or after 14 day follow-up +2. Traveler is referred to health facility at any point during follow-up + +**A traveler that is referred to a health facility is expected to be enrolled in the COVID-19 Case-based Surveillance Tracker as a suspected case** (according to national guidelines). Details about a suspected case including clinical exam, exposures, laboratory results and case outcome would be recorded in the CBS program. + +### Structure: Points of Entry Screening Tracker Program { #structure-points-of-entry-screening-tracker-program } + +![Structure](resources/images/POE_image02.png "Structure") + +#### Consideration for Organisation Units & Geography { #consideration-for-organisation-units-geography } + +This program design assumes that Points of Entry such as airports, seaports or land crossings will be created as organisation units included in the OU hierarchy. The program would be assigned to the POE org units. Primary analysis is based on the enrolling Org Unit (the port of entry). + +Additional geographical components are also captured as other dimensions: + +1. TEI coordinates: It is possible to capture TEI coordinates when registering the traveler as TEI. These can be displayed in the maps app. Local protocols may choose what coordinates to enter, for example the TEI’s local residence where he/she may be self-quarantined for 14 days. +2. Event coordinates: for screening and follow-up stages, coordinates can be captured on the event and displayed in a map. For example, the user may capture a traveler’s location each time they are followed up (i.e. in the case of tourists or others not in home quarantine). + +#### Program Description { #program-description } + +|Étape|Description| +|--|--| +|**Registration**|The Tracked Entity is the traveler, which is represented by the Tracked Entity Type of ‘person.’ The TEI is configured to collect a geographic ‘point’ during registration. These can be analyzed in a map.| +|**Enrollment details**|Enrollment date
The first Program Stage is configured to appear on the Registration page so that a user does not need to click through to add the first event.| +|**Attributs**|Attributes include basic personal information and unique case identifiers
- Passport number
- Local Case ID
- Age
- First Name
- Surname
- Country of residence
- Sex
- Date of birth
- Local address
- Home address
- Telephone (local)
- Telephone (foreign)
- Emergency contact
- Emergency contact phone
- Email| +|**Stage 1**
**Screening at POE**
**(non-repeatable)**|This stage records:
- Traveler details (countries visited, flight number, date of departure, etc)
- Examination: recorded temperature
- Symptoms: this list includes symptoms typically checked for both COVID-19 symptoms and symptoms of other potential notifiable diseases
- Case clearance

If the traveler is marked as ‘cleared’, no further follow up is required; the enrollment may be closed. If the traveler requires follow-up, an event can be scheduled for follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 2:**
**Follow-up (within 14 days)**
**(repeatable)**|Data is entered at this stage if any interim follow-up is performed before the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment may be closed if no further monitoring & follow-up is planned in this program.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 3:**
**Follow-up (after 14 days)**
**(non-repeatable)**|Data is entered at this stage at the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)
- Case clearance

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment should be closed at the completion of 14 day follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization. + +![Enrollment](resources/images/POE_image03.png "Enrollment") + +![Program Stage 1 - Screening at POE](resources/images/POE_image04.png "Program Stage 1 - Screening at POE") + +![Program Stage 1 - Screening at POE](resources/images/POE_image05.png "Program Stage 1 - Screening at POE") + +![Program Stage 2: Follow-up (within 14 days)](resources/images/POE_image06.png "Program Stage 2: Follow-up (within 14 days)") + +![Program Stage 3: Follow up (after 14 days)](resources/images/POE_image07.png "Program Stage 3: Follow up (after 14 days)") + +#### How to refer the TEI to another Organisation Unit { #how-to-refer-the-tei-to-another-organisation-unit } + +Primary analysis is completed on the enrolling organisation unit (the port of entry). Referral facility is captured as a Data Element (type: Organisation Unit) in order to display travelers by referral to health facility in the analytics apps (i.e. Event Report). In some use cases, it may be desirable to refer the TEI (the traveler) to another Org Unit for follow-up. + +A TEI can be ‘referred’ to another org unit such as a health facility for one event or permanently. In this case, health facility user must be able to search TEIs enrolled in the relevant Points of Entry org units. For example, if after screening a traveler at the POE, the traveler may be “referred” to a district health office near the traveler’s local address for follow-up by district health staff. After completing the data entry for Stage 1 (screening), the user would refer the TEI to a District Health Center. Read more about referrals in tracker in [DHIS2 User Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/tracking-individual-level-data/tracker-capture.html). + +![alt_text](resources/images/POE_image08.png "image_tooltip") + +### Program Relationships { #program-relationships } + +This program has the relationshipType ‘Has been in contact with’. Users can create a relationship between TEIs enrolled in the POE program and TEIs in other COVID-19 tracker programs (Case-based Surveillance, Contact Registration & Follow-up). The relationship can be added at any point in the program stages during data entry. + +### Règles de programme { #program-rules } + +The following program rules have been configured. + +|Nom de la règle du programme|Description de la règle du programme| +|--|--| +|Calculer et attribuer l'âge du patient en années|Calculer et attribuer l'âge du patient en années| +|Hide countries if not visited|Hide countries if not visited| +|Hide Follow-Up Stages|Hide Follow-Up Stages if the case is cleared at the port of entry| +|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)| +|Hide symptoms if no symptoms present (Follow Up within 14 days)|Hide symptoms if no symptoms present (Follow Up within 14 days)| +|Hide symptoms if no symptoms present (PoE)|Hide symptoms if no symptoms present (PoE)| + +You can read more about program rules here: +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create_program_rule) + +### Indicateurs et indicateurs de programme { #indicators-and-program-indicators } + +||| +|--|--| +|COVID-19 : voyageurs dépistés|Nombre total de voyageurs dépistés et enregistrés au programme de dépistage au PDE| +|COVID-19 : autorisation des voyageurs au PDE|Nombre de voyageurs autorisés après le contrôle au PDE (aucun suivi requis)| +|COVID-19 : voyageurs présentant des symptômes au PDE|Nombre de voyageurs présentant des symptômes lors du contrôle au PDE| +|COVID-19 : voyageurs autorisés après 14 jours de suivi|Nombre de voyageurs autorisés après 14 jours de suivi (aucun symptôme n'est apparu pendant cette période)| +|COVID-19 : voyageurs référés à un établissement de santé|Nombre de voyageurs référés à un établissement de santé durant les 14 jours de surveillance| +|COVID-19 : voyageurs enregistrés pour un suivi de 14 jours|Nombre de voyageurs ne présentant pas de symptômes lors du dépistage au PDE et n'ayant pas été autorisés lors du dépistage au PDE| +|COVID-19 : voyageurs actuellement sous surveillance|Nombre de voyageurs non autorisés ou non référés à un établissement de santé| +|COVID-19 : les voyageurs ayant développé des symptômes lors du suivi|Nombre de voyageurs ayant développé des symptômes lors du suivi (exclure les voyageurs présentant des symptômes lors du dépistage au PDE)| +|COVID-19 % travelers developed symptoms during 14-day follow-up|Numerator: Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)
Denominator: Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| + +Users can also generate an Event Report to see: + +1. Travelers by nationality and/or originating country +2. Referrals to health facility + +## Références { #references } + +* DHIS2 COVID-19 [Tracker Package Installation Guide](covid-19-tracker-installation.html) +* World Health Organisation (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) (interim guidance, published 19 March 2020) + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md new file mode 100644 index 00000000..3997028b --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implémentation +--- + +# COVID-19 Points of Entry { #covid-19-points-of-entry } + +## Conception { #design } + +[Version 1.0.2](#c19-poe-design) + +## Installation { #installation } + +[Installation Guide](#c19-poe-installation) + +## Note de mise à jour { #release-note } + +[Release Note](#c19-poe-release-note) + +## Référence des métadonnées { #metadata-reference } + +[Version 1.0.2](https://packages.dhis2.org/en/C19_POE/1.0.2/C19_POE_COMPLETE_1.0.2_DHIS2.37.xlsx) + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md new file mode 100644 index 00000000..ebe0634b --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -0,0 +1,164 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/c19_evt-design.md" +revision_date: '2022-11-08' +tags: +- Implémentation +--- + +# COVID-19 Surveillance Line-list Design { #c19-evt-design } + +Demo: [https://covid.dhis2.org](https://covid.dhis2.org/demo) + +## Objectif { #purpose } + +The COVID-19 Surveillance Event Program System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Contexte { #background } + +The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +|Type de Package de surveillance|Surveillance basée sur les cas (Tracker)|Surveillance (Événement)|Surveillance (Agrégat )| +|--|--|--|--| +|_Description_|Enrolls a case and tracks over time through laboratory confirmation & case outcome|Permet de saisir les détails relatifs à un cas critique sous forme de liste de lignes|Permet la déclaration quotidienne ou hebdomadaire des principaux points de données agrégées| +|_Pros_|La grande granularité des données et les multiples dimensions temporelles de l'analyse peuvent permettre de décentraliser le flux de travail c'est-à-dire tous les événements liés au cas.|Caractéristique plus granulaire qu'agrégée et pouvant saisir les principales dimensions temporelles (c'est-à-dire la date du rapport par rapport à l'apparition des symptômes) ; réduction de la charge de saisie des données par rapport au tracker et niveau de complexité peu élevé|Peu complexe, facile à mettre en œuvre, plus facile à gérer lorsque le nombre de cas est élevé| +|_Cons_|Le volume de données à saisir peut être écrasant lorsque le nombre de cas atteint le seuil ; ceci peut rendre la mise en œuvre complexe|Ne prend pas en charge le suivi des cas ou d'autres flux de travail décentralisés|Une granularité plus faible pour l'analyse détaillée (c'est-à-dire une analyse basée exclusivement sur la date de notification du cas, une désagrégation limitée) + +**This document covers only the design of the surveillance event program package**; separate system design documents are available for DHIS2 Tracker and aggregate packages. + +L'OMS "exhorte tous les pays à se préparer à l'arrivée éventuelle de COVID-19 en préparant des systèmes d'intervention d'urgence, en augmentant la capacité à détecter et à soigner les patients, en veillant à ce que les hôpitaux disposent de l'espace, du matériel et du personnel nécessaires et en mettant au point des interventions médicales visant à sauver des vies". + +Les objectifs du progiciel de surveillance du COVID-19 sont les suivants : + +1. surveiller les tendances de la maladie là où il y a transmission interhumaine ; +2. détecter rapidement les nouveaux cas dans les pays où il n'y a pas de circulation du virus ; +3. fournir des informations épidémiologiques pour effectuer des évaluations des risques aux niveaux national, régional et mondial ; et +4. fournir des informations épidémiologiques pour orienter les mesures de préparation et d'intervention. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## Résumé de la conception du système { #system-design-summary } + +This package is designed as a DHIS2 [Event Program](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#about_event_program). **The Event Program is not designed to capture all data variables contained in the [WHO case reporting template](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx)**. To capture a complete set of WHO case reporting variables, please refer to the DHIS2 COVID-19 Case-based Surveillance Tracker. Rather, the event program is a simplified program that captures a subset of minimum critical data points to facilitate high data quality when the number of caseloads or burden of reporting exceeds capacity for successfully completing the full line-list for suspected COVID-19 cases. For implementers who wish to capture the complete WHO line-listing, please refer to the COVID-19 Case-based Surveillance Tracker Package. + +The COVID-19 Surveillance Event Program data package includes: + +1. Event program and data elements case reporting +2. Core indicators +3. Tableau de bord + +### Use Case: Simplified line-listing of COVID-19 cases { #use-case-simplified-line-listing-of-covid-19-cases } + +As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The event package is designed to capture the most critical data points in a line-list and analytical capacities for surveillance and response. The event package is designed as a standalone program. However, countries may use the event package in combination with other packages (i.e. event reports and daily aggregate reporting); or, they may shift from tracker to event to aggregate as caseloads and reporting burden increases. **_Countries should plan carefully how they intend to implement these packages in combination, including reporting flows, transitioning from one data model to another, and how to maintain historical data for analysis if transitioning between data models. _** + +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. + +#### Utilisateurs cibles { #intended-users } + +* Health facility users: capture and report key data on COVID-19 cases and deaths presenting at the health facility +* Autorités sanitaires nationales et locales : suivi et analyse des données de surveillance des maladies au moyen de tableaux de bord et d'outils d'analyse permettant de réaliser des évaluations des risques et de planifier les interventions ; production de rapports en vue des rapports régionaux et global + +#### Déroulement { #workflow } + +Unlike the tracker program, there are limitations to decentralization of the data reporting workflow in an Event program. The most significant limitation is that the Case Outcome (recovery or death) is often not known until days or weeks after the case is reported. The current program design allows for the following workflow options: + +1. Event is created when a suspected case is reported. All known data is entered, but the event is not completed. A user can select an ‘Active Event’ from a working list based on User filters and criteria. When missing data becomes available (i.e. the case outcome), the user can enter the remaining data fields and complete the event. Cases can be identified in the event list by the Case ID data element. See the image below as an example which can be accessed within the Capture App: +![Capture App](resources/images/EVENT_image1.png "Capture App") + +2. Event is created. All case related data is entered retrospectively, including the Outcome. Event is completed. _The limitation is this approach is timeliness of the data reporting, as new suspected cases might not be captured until their outcome which is often too late for decision making._ + +### Structure du programme { #program-structure } + +The program is called ‘COVID-19 Cases (events)’ + +|Section|Description| +|--|--| +|Date of report|Event Date
_Countries may re-name the event date to apply to their protocols._| +|Section 1
**Basic Information**|Records basic demographic data.
_Countries may add data elements as desired._
- **Patient ID**
Can be used to filter events in working lists, eg. Active events
- **Sex**
- **Age**| +|Section 2
Case Details|Records information about the case including symptoms, severity, testing, etc.
- **Symptoms**
Options: Yes / No
Specifies whether a case has any symptoms at time of notification

- **Date of symptoms onset**
Only appears if symptoms are present;
Date of symptoms onset, if available, will replace “Date of Report” in data analytics and reporting.

- **Case Severity (at time of notification)**
Options: Mild / Moderate / Severe / Critical
- **Laboratory tested?**
Options: Yes / No/ Unknown
Specifies whether a case has been laboratory tested for COVID-19

- **Test Result**
Only appears if the case was laboratory tested
Options: Inconclusive / Positive / Negative / Unknown
The program is designed to capture only the final test result. Results for each individual test (if available) and the total number of tests performed are not captured.
- **Case Classification**
Options: Suspected case / Probable case / Laboratory confirmed case
Automatically assigned values
The values are assigned by Program rules in accordance with WHO case definitions
This feature can be useful in filtering active cases in the working lists.| +|Section 3
**Exposures**|- **Has the case traveled in the 14 days prior to symptoms onset?**
Options: Yes / No / Unknown
Specifies travel history of the case.

- **Likely Infection Source**
Options: Imported case* / Local Transmission / Exposure unknown
* Imported case option appears only if the case traveled in the 14 days prior to symptoms onset

- **Specify local source**
Only appears if Likely Infection Source is Local Transmission
Options: Community (workplace, public transport, etc.) / Household / Healthcare Facility / Close Contact with Other Infected Individual / Exposure Unknown

- **Case Type**
Options: New index case / Linked to existing cluster / Unknown
Specifies whether the case is connected to an existing cluster or is a new index case| +|Section 4
**Treatment**|- **Hospitalised**
Options: Yes / No

- **Did the case receive care in an intensive care unit (ICU)?**
Only appears if the case is hospitalised
Options: Yes / No| +|Section 5
**Contacts**|- **Total number of contacts followed for this case**
Records number of contacts| +|Section 6
**Outcome**|- **Health outcome**
Options: Recovered / Death| +|Section 7
**Assigned Date of onset of symptoms**|- **Calculated onset date (for Indicators)**
This section is used only to calculate indicators based on report date vs. date of onset of symptoms]
This automatically assigned date is used in program indicators. Initially, it is the report date. If the date of onset of symptoms is available, the date is replaced by the date of onset of symptoms.| +|**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.| + +### Groupes d'utilisateurs { #user-groups } + +Le package de métadonnées englobe les groupes d’utilisateurs ci-après : + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Currently, only users assigned to the COVID19 data capture group will have access to capture data in the program. Please refer to the installation guidance for more instructions. + +### Règles de programme { #program-rules } + +The following program rules have been configured for the program: + +|Nom de la règle du programme|Description de la règle du programme| +|--|--| +|Assign Empty Value to Class Classification|Automation: Assign Empty Value to Class Classification| +|Assign Event Date|Automation: Assign Event date if to onset date if no Onset date is available| +|Assign 'Laboratory Confirmed Case' to Case Classification|Automation: Assign 'Laboratory Confirmed Case' to Case Classification| +|Assign Onset Date|Automation: Assign Symptoms Onset Date if available| +|Assign 'Probable Case' to Case Classification|Automation: Assign 'Probable Case' to Case Classification| +|Assign 'Suspected Case' to Case Classification|Automation: Assign Suspected Case' to Case Classification| +|Hide Case Classification Field|Hide Case Classification Field until Lab Test question is answered| +|Hide ICU field|Hide ICU field unless Hospitalised| +|Hide 'Imported Case'|Hide 'Imported Case' if not traveled| +|Hide Onset of Symptoms Date|Hide Onset of Symptoms Date if no symptoms| +|Hide Outcome Options|Hide irrelevant Outcome Options| +|Hide 'Specify Local Infection Source'|Hide 'Specify Local Infection Source' unless Local Transmission is selected| +|Hide Test Result Field|Hide Test Result Field until Lab Test question is answered with yes| +|Hide Test Result Options|Hide Irrelevant Test Result Options| +|Hide Unknown Options|Hide Irrelevant Unknown Options| + +Vous pouvez en savoir plus sur les règles du programme ici : + +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule) + +### Indicateurs et indicateurs de programme { #indicators-and-program-indicators } + +From the data captured in the COVID-19 line-listing program, we can calculate the following indicators, including those recommended by the WHO for daily and weekly reporting, present them in a dashboard. All COVID-19 program indicators based on the event program are assigned to the Program Indicator Group ‘COVID-19 Events.’ + +||| +|--|--| +|COVID-19 - Cases admitted in intensive care unit (ICU)|COVID-19 Cases admitted in intensive care unit (ICU)| +|COVID-19 - Cases exposed through healthcare facility|Cases where infection is suspected to have occurred in a health care setting| +|COVID-19 - Cases infected by community transmission|Cases where infection is suspected to have occurred through community spread| +|COVID-19 - Cases infected by household transmission|Cases where infection is suspected to have occurred within the household| +|COVID-19 - Cases infected by local transmission|Cases where infection is suspected to have occurred locally, not in another country| +|COVID-19 - Cases infected through other contact with other infected individual|Cases where infection is suspected to have occurred through other close contact with an infected individual (excluding those listed: household, known cluster, HCF)| +|COVID-19 - Cases linked to known cluster|Cases where infection is suspected to have occurred by linkage to a known cluster of cases| +|COVID-19 - Cases with unknown exposure|Cases where source of infection or exposure is unknown| +|COVID-19 - Deaths|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 - Cas confirmés et hospitalisés|Number of confirmed cases that were admitted into hospital| +|COVID-19 - Cas importés|Cases where likely source of infection is recorded as another country or imported from another country.| +|COVID-19 - Cas confirmés en laboratoire|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by report date| +|COVID-19 - Cas confirmés en laboratoire - en fonction de l'apparition des symptômes|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by date of onset of symptoms| +|COVID-19 - Cas testés en laboratoires|Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)| +|COVID-19 - Cas probables|Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date| +|COVID-19 - Cas probables - en fonction de l'apparition des symptômes|Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms| +|COVID-19 - Recovered cases|Number of cases that are recovered (By date of onset of symptoms)| +|COVID-19 - Cas suspects|Total number of cases suspected with COVID-19, by report date| +|COVID-19 - Cas suspects - en fonction de l'apparition des symptômes|Total number of cases suspected with COVID-19, by date of onset of symptoms| +|COVID-19 - Suspected cases not tested|Total number of suspected cases without a lab result| +|COVID-19 Event - case fatality rate|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 : Décès par sexe et par tranche d'âge|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 : Cas confirmés par sexe et par tranche d'âge|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 : Cas suspects par sexe et groupe d'âge|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| + +## Références { #references } + +* [COVID-19 Surveillance, Response & Vaccine Delivery Toolkit](https://dhis2.org/covid-19) +* Guide technique de l'OMS sur la surveillance et les définitions de cas de COVID-19 (dernière mise à jour le 20 mars 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* Dictionnaire de données de l'OMS pour le formulaire de déclaration de cas de COVID-19 +[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* Dépistage en laboratoire des cas suspects d'infection humaine par le nouveau coronavirus 2019 (2019-nCoV) (dernière mise à jour le 2 mars 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* Considérations de l'OMS dans l'investigation des cas et groupes de COVID-19 (dernière mise à jour le 13 mars 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* Rapports de l'OMS sur la situation du coronavirus +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md new file mode 100644 index 00000000..97f80ccb --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md @@ -0,0 +1,13 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implémentation +--- + +# COVID-19 Surveillance Events { #covid-19-surveillance-events } + +## Conception { #design } + +[Version 0.3.2](#c19-evt-design) + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md new file mode 100644 index 00000000..87a16730 --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md @@ -0,0 +1,22 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_surveillance-digital_data_package-2022.md" +revision_date: '2023-09-01' +tags: +- Implémentation +--- + +# COVID-19 Surveillance { #covid-19-surveillance } + +DHIS2 released a digital metadata package to accelerate case detection, situation reporting, active surveillance and response for COVID-19. The design is inspired by the Ministry of Health Sri Lanka’s pioneering use of DHIS2 tracker for COVID-19 case detection and draws on years of collaboration with the World Health Organisation (WHO) to develop information system standards for case-based disease surveillance. The COVID-19 digital data package includes standard metadata aligned with the WHO’s [technical guidance on COVID-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and implementation guidance to enable rapid deployment in countries. + +The design of these modules can be adapted, modified and reused for new and emerging infectious disease threats to strengthen health emergency preparedness and response systems in countries. + +## COVID-19 Surveillance Modules { #covid-19-surveillance-modules } + +DHIS2 supports surveillance workflows and automated analysis for key components of routine and active surveillance: + +* **COVID-19 Case Surveillance tracker**: enrolls & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. +* **Contact Registration & Follow-up tracker**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. +* **Ports of Entry Screening & Follow-up tracker**: enrols travellers who have visited high-risk locations at Ports of Entry for 14-day monitoring and follow-up. +* **COVID-19 Aggregate Situation Reports**: an aggregate reporting dataset that captures minimum necessary data points for daily or weekly reporting and includes key information for generating situation reports. + diff --git a/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..06434954 --- /dev/null +++ b/projects/docs-full-site/fr/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implémentation +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Présentation { #overview } + +Nous avons procédé à plusieurs mises à jour du paquet existant pour l'aligner sur les nouvelles directives de surveillance COVID-19 [publiées par l'OMS le 20 mars 2020] (https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) et avons introduit de nouveaux éléments dans le paquet de soutien. Pour toute question, veuillez consulter les notes ici et nous contacter sur le forum de discussion COVID-19 dans la [communauté de pratique] (https://community.dhis2.org/c/implementation/covid-19/). + +**Tous les paquets de métadonnées et la documentation peuvent être téléchargés à partir de [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. + +La nouvelle version comprend : + +1. COVID-19 Case-based Surveillance Tracker program +2. COVID-19 Contact Registration & Follow-Up program +3. COVID-19 Rapport de surveillance globale +4. Points of Entry Screening Tracker program [***DISCONTINUED***] + +### COVID-19 Case Surveillance Tracker { #covid-19-case-surveillance-tracker } + +1. Codes de métadonnées mis à jour afin de s'accorder avec [dictionnaire des données de déclaration basée sur des cas de l'OMS] (https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +2. Les indicateurs de programme ont été mis à jour pour refléter les nouvelles définitions de cas de l'OMS pour les cas probables (référence aux définitions de cas mises à jour dans les directives de surveillance provisoires mises à jour le 20 mars 2020 [Directives de surveillance provisoires de l'OMS mises à jour le 20 mars 2020](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf)) +3. Les légendes d'âge ont été mises à jour pour répondre aux nouvelles directives de l'OMS relatives à la déclaration hebdomadaire +4. Type de relation ajouté au progiciel de métadonnées +5. Modifications mineures apportées aux métadonnées pour faciliter l'installation du paquet (c'est-à-dire que l'indicateur de type UID correspond au type d'indicateur inclus dans l'ensemble d'agrégation) + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. Une nouvelle étape du programme a été ajoutée pour permettre un "suivi" reproductible d'un cas de contact. Elle a été ajoutée pour refléter les flux de travail mis en œuvre en Ouganda et au Togo, où les contacts peuvent être régulièrement suivis pendant 14 jours pour déterminer s'il existe des symptômes. Le ***programme*** est basé sur les directives de l'OMS que pouvez consulter [ici](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19), ainsi que sur les informations obtenues via le site web [OpenWHO](https://openwho.org/courses/introduction-to-ncov) +2. Les légendes d'âge ont été mises à jour pour répondre aux nouvelles directives de l'OMS relatives à la déclaration hebdomadaire +3. Type de relation ajouté au progiciel de métadonnées +4. Modifications mineures apportées aux métadonnées pour faciliter l'installation du paquet + +### COVID-19 Rapport de surveillance globale { #covid-19-aggregate-surveillance-reporting } + +Les mises à jour suivantes ont été effectuées pour tenir compte des nouvelles orientations contenues dans les [lignes directrices de l'OMS mises à jour le 20 mars 2020] (https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf), y compris la mise à jour des rapports globaux à l'OMS (hebdomadaires et quotidiens) + +1. Les catégories d'âge sont mises à jour en fonction des nouvelles tranches d'âge +2. De nouveaux indicateurs ont été ajoutés en ce qui concerne la proportion d'hommes parmi les cas confirmés et la proportion d'hommes parmi les décès confirmés +3. Le nouvel ensemble de données hebdomadaires pour saisir la classification de la transmission au premier niveau infranational (c'est-à-dire provincial -- peut être attribué à n'importe quel niveau infranational selon le cas dans le pays) selon les directives actualisées de l'OMS en matière de déclaration hebdomadaire +4. Modifications mineures apportées aux métadonnées pour faciliter l'installation du paquet + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +Le cas d'utilisation du Programme Tracker des points d'entrée a été conçu dans le but de soutenir l'enregistrement des voyageurs entrant dans un pays ayant des antécédents de voyage ou de résidence dans un pays/une région/un territoire qui signalent une transmission locale de COVID-19 et qui peuvent avoir besoin d'être suivis pour s'assurer qu'aucun symptôme ne se développe. Il est basé sur la conception mise en œuvre par HISP Sri Lanka pour soutenir le ministère de la Santé du Sri Lanka avec des changements mineurs visant à rendre le programme plus générique en vue d'une utilisation mondiale et pour s'aligner sur les autres programmes Tracker du paquet COVID-19. Le programme vient en appui aux interventions aux points d'entrée détaillées dans les [directives techniques de l'OMS pour la gestion des personnes malades aux points d'entrée] (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/fr/IMPLEMENT__LOGISTICS__data-quality-and-data-use-md b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__data-quality-and-data-use-md index 84f7738b..c1b42449 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__data-quality-and-data-use-md +++ b/projects/docs-full-site/fr/IMPLEMENT__LOGISTICS__data-quality-and-data-use-md @@ -28,7 +28,7 @@ Accès aux données Dimensions de la qualité des sorties - Pertinence -- Justesse +- Exactitude - Complétude - Précision - Fiabilité (reproductibilité) @@ -39,7 +39,7 @@ Dimensions de la qualité des sorties - Comparabilité Process quality dimensions -- Charge pour les collecteurs de données +- Charge de travail pour les collecteurs de données - Pertinence des sources de données - Processus de collecte des données - Transparence et documentation des sources de données @@ -47,7 +47,7 @@ Process quality dimensions Qualité institutionnelle - Transparence et crédibilité -Alors que les systèmes traditionnels de gestion des données du LMIS, basés sur le papier, exigent de trouver un équilibre entre différents compromis, tels que la quantité de champs de données ou l'exactitude et la ponctualité des données, l'utilisation de systèmes numériques de collecte et de gestion des données permet d'améliorer simultanément l'exactitude, la ponctualité, l'accessibilité, la cohérence, etc. +Alors que les systèmes traditionnels de gestion des données du LMIS, basés sur le papier, exigent de trouver un équilibre entre différents compromis, tels que la quantité de champs de données ou la précision et la ponctualité des données, l'utilisation de systèmes numériques de collecte et de gestion des données permet d'améliorer simultanément la précision, la ponctualité, l'accessibilité, la cohérence, etc. ### Accessibilité des données { #data-accessibility } @@ -70,10 +70,10 @@ Les différentes parties prenantes du réseau d'approvisionnement et du système En principe, la gestion efficace et efficiente des réseaux d'approvisionnement ne nécessite qu'un petit nombre de points de données. Par exemple, au niveau de l'établissement de santé, seules les quantités des transactions de stock (stock distribué/livré, éliminé et perdu) sont pertinentes ; les autres données (secondaires) peuvent être déduites. En amont, il faut également gérer les données relatives aux commandes, aux expéditions et aux détails des stocks (numéros de lot et dates de péremption). L'utilisation de DHIS2 dans les établissements de santé encourage à limiter les points de données collectés, car il ne fait que compléter les données qui ne sont pas (et ne peuvent pas être) disponibles dans les eLMIS nationaux, et le recours aux bonnes pratiques est encouragé pendant la phase de conception des projets et pendant la formation des membres de projets. -#### Justesse { #correctness } +#### Exactitude { #correctness } -La justesse des données consiste à collecter les éléments de données pour les champs concernés ; par exemple saisir des quantités distribuées dans le bon champ de données (colonne) d'un formulaire papier ou numérique. -L'utilisation de DHIS2 contribue à la justesse des données en réduisant le nombre de champs de données. Par exemple, en utilisant DHIS2-RTS (système en temps réel), seules les quantités des transactions sont enregistrées et il est donc impossible d'entrer par erreur une valeur dans un champ de données (colonne) qui ne convient pas. L'utilisation de lecteurs de codes-barres élimine le risque d'enregistrer par erreur les données d'un produit de santé dans la mauvaise ligne. De plus, des règles de validation peuvent également être configurées pour éviter les erreurs au moment de la saisie des données, par exemple en empêchant la saisie d'une valeur négative pour le "stock disponible". +L'exactitude des données consiste à collecter les éléments de données pour les champs concernés ; par exemple saisir des quantités distribuées dans le bon champ de données (colonne) d'un formulaire papier ou numérique. +L'utilisation de DHIS2 contribue à l'exactitude des données en réduisant le nombre de champs de données. Par exemple, en utilisant DHIS2-RTS (système en temps réel), seules les quantités des transactions sont enregistrées et il est donc impossible d'entrer par erreur une valeur dans un champ de données (colonne) qui ne convient pas. L'utilisation de lecteurs de codes-barres élimine le risque d'enregistrer par erreur les données d'un produit de santé dans la mauvaise ligne. De plus, des règles de validation peuvent également être configurées pour éviter les erreurs au moment de la saisie des données, par exemple en empêchant la saisie d'une valeur négative pour le "stock disponible". #### Complétude { #completeness } @@ -84,8 +84,8 @@ En utilisant DHIS2-RTS (système en temps réel), la question de la complétude #### Exactitude { #accuracy } -L'exactitude fait référence à la concordance de la valeur des points de données collectés avec l'entité physique mesurée et déclarée. Il s'agit, par exemple, de savoir si le stock disponible déclaré correspond réellement à la quantité physiquement disponible dans le magasin. L'exactitude des données exige à la fois de bien compter le stock et de saisir la bonne quantité. -Ni les systèmes manuels ni les systèmes numériques de gestion des données ne pourront jamais garantir l'exactitude de toutes les données et, en principe, les systèmes d'information ne seront pas en mesure de détecter les chiffres erronés ou les transactions qui n'ont pas été corrigées. Toutefois, DHIS2 dispose de plusieurs outils qui permettent d'identifier les incohérences dans les données (voir ci-dessous). Souvent, les contrôles et les bilans mettent en évidence certaines valeurs de données qui sont clairement erronées et indiquent l'intervalle correct dans lequel se trouve une certaine valeur, sans toutefois permettre de déterminer la valeur exacte. +La précision fait référence à la concordance de la valeur des points de données collectés avec l'entité physique mesurée et déclarée. Il s'agit, par exemple, de savoir si le stock disponible déclaré correspond réellement à la quantité physiquement disponible dans le magasin. La précision des données exige à la fois de bien compter le stock et de saisir la bonne quantité. +Ni les systèmes manuels ni les systèmes numériques de gestion des données ne pourront jamais garantir la précision de toutes les données et, en principe, les systèmes d'information ne seront pas en mesure de détecter les chiffres erronés ou les transactions qui n'ont pas été corrigées. Toutefois, DHIS2 dispose de plusieurs outils qui permettent d'identifier les incohérences dans les données (voir ci-dessous). Souvent, les contrôles et les bilans mettent en évidence certaines valeurs de données qui sont clairement erronées et indiquent l'intervalle correct dans lequel se trouve une certaine valeur, sans toutefois permettre de déterminer la valeur exacte. #### Fiabilité (reproductibilité) { #reliability-reproducibility } @@ -137,7 +137,7 @@ L'intégration de DHIS2 au niveau de l'établissement de santé avec le eLMIS na #### Pertinence des sources de données { #appropriateness-of-data-sources } -Tous les systèmes de rapports périodiques utilisent des registres manuels tels que des fiches de lot, des fiches de stock et d'autres enregistrements comme principale source de données, même si les rapports (mensuels), qui constituent une source de données secondaire, sont enregistrés directement sur des appareils numériques. Par conséquent, pour la période de déclaration (mensuelle), l'utilisation de DHIS2 repose entièrement sur l'exactitude et la fiabilité des registres de stock manuels sans que des informations sur ces sources de données ne soient fournies ou documentées. Pour les données du LMIS, la pertinence des sources de données n'est pas un facteur déterminant en ce sens qu'il n'existe pas d'autres sources de données. +Tous les systèmes de rapports périodiques utilisent des registres manuels tels que des fiches de lot, des fiches de stock et d'autres enregistrements comme principale source de données, même si les rapports (mensuels), qui constituent une source de données secondaire, sont enregistrés directement sur des appareils numériques. Par conséquent, pour la période de déclaration (mensuelle), l'utilisation de DHIS2 repose entièrement sur la précision et la fiabilité des registres de stock manuels sans que des informations sur ces sources de données ne soient fournies ou documentées. Pour les données du LMIS, la pertinence des sources de données n'est pas un facteur déterminant en ce sens qu'il n'existe pas d'autres sources de données. Cependant, pour les données enregistrées, stockées et partagées par DHIS2, les fichiers journaux fournissent des détails complets et une visibilité du lieu de collecte des données (à condition que la fonction de géolocalisation soit configurée), l'identité de la personne qui s'est connectée à l'appareil mobile, ainsi que la date et l'heure exactes de chaque point de données enregistré et de toute modification apportée à ces données. DHIS2-RTS (système de gestion des stocks en temps réel) permet de gérer les stocks médicaux sans aucun enregistrement papier. La seule source de données physique ("externe") sur laquelle il s'appuie est le code-barres qui est attaché à chaque produit de santé dans le magasin de fournitures médicales. Comme pour toutes les autres données enregistrées et gérées dans DHIS2, DHIS2-RTS enregistre la géolocalisation, l'identité de l'utilisateur ainsi que l'horodatage (heures, minutes, secondes et fractions de secondes) de chaque transaction enregistrée. @@ -154,72 +154,72 @@ Toutefois, les informations fournies ci-dessus sur la documentation relative à ### Qualité institutionnelle { #institutional-quality } -La qualité des données du LMIS dépend de la confiance que lui accordent les acteurs du système de santé. Malheureusement, les doutes sur la qualité et l'exactitude des données sont assez fréquents et, dans le pire des cas, conduisent à ignorer les données du LMIS déclarées par les établissements de santé et à remettre en question des données essentielles du LMIS telles que les stocks mensuels (agrégés). +La qualité des données du LMIS dépend de la confiance que lui accordent les acteurs du système de santé. Malheureusement, les doutes sur la qualité et la précision des données sont assez fréquents et, dans le pire des cas, conduisent à ignorer les données du LMIS déclarées par les établissements de santé et à remettre en question des données essentielles du LMIS telles que les stocks mensuels (agrégés). DHIS2 améliore considérablement la qualité des données, car les enregistrements y sont transparents, facilement accessibles et partagés instantanément avec toutes les parties prenantes, et peuvent être facilement analysés et audités. ### Résumé de la contribution de DHIS2 à la qualité des données { #summary-of-the-dhis2-contribution-to-data-quality } Le tableau ci-dessous résume la manière dont DHIS2 contribue à améliorer considérablement la qualité des données, pour le cas d'utilisation du LMIS, grâce à sa conception et à divers algorithmes automatiques. -| **Data quality dimension** | **DHIS2 contribution** | +| **Dimension de la qualité des données** | **Contribution de DHIS2** | | :--- | :--- | -| Accès | Global accessibility from a single DHIS2 instance | -| Relevance | Data collection (forms) according to best practices | -| Exactitude | Minimising the number of data fields, Barcode scanners for identifying healthcare products, validation rules | -| Complétude | Intuitive visualisation of data gaps, Data completeness reports, Completeness by design when using DHIS2-RTS | -| Accuracy | Data consistency checks, validation rules | -| Reliability (reproducibility) | - | -| Cohérence | Data consistency checks, Instant stock on hand updates when using DHIS2-RTS | -| Timeliness and punctuality | Report punctuality analysis, Timeliness by design when using DHIS-RTS | -| Fréquence | Flexible use of any reporting frequency, Real-time reporting (best practice) with DHIS2-RTS | -| Interpretability | Use of only essential LMIS data by design | -| Comparability | Standardised and present data reporting forms | -| Burden for data collectors | Minimal LMIS data collection by design, Avoids data redundancy | -| Appropriateness of data sources | Complete visibility of data collection through log files | -| Data collection process | Digitised data collection, Automated data sharing (synchronisation),Eliminates mistakes by data duplication and copying | -| Transparency and documentation | Transparency of data collection through log files | -| Transparency and credibility | Transparency and auditability of all data and log files | - -## LMIS data quality analysis { #lmis-data-quality-analysis } - -DHIS2 natively features a range of tools and applications for preventing the entry of erroneous data, real-time validation of already entered data and (retro-active) analysis of entered data for identifying (potentially) false data values as well as data which was not recorded on time. - -### LMIS data validation { #lmis-data-validation } - -The native DHIS2 data validation features allow validating data values during data entry entry and thereby minimising data handling errors. Data validation means ensuring that entered data values are within predefined ranges. -The DHIS2 "Value type" setting, which is natively available for all "Data elements", allows restricting the entry of data values to certain number sets such as natural numbers ("Positive Integer") or positive integers (which includes zero). This setting also prevents "accidental" data entry such as mistakenly entering text into a numeric data field. -During data entry, DHIS2 will indicate any data values which are outside the defined data range by highlighting the data field with a red background and displaying an additional error message on the screen. For example, DHIS2 will prevent users from entering non-integer or any negative values in a stock on hand field and prevent the user from saving any report until the error is corrected. -Users can open an on-screen pop-up window which will display the entire history of entered data values in a bar chart and line chart which allows to quickly identify inconsistent values and outliers. -The DHIS2-RTS (Real-Time System) goes even further by not only displaying an alert in real-time if negative data values are entered but even preventing the user from saving the data entry and continuing entry of any further data. In addition, a specific minimum and maximum data value can be configured for each data field which will display a real-time alert if the user enters a value which is outside of the configured range. -The DHIS2-RTS system prevents negative stock on hand values, prevents entry of any non-integer values in any data field and prevents entry of negative or zero values for any transaction quantities. -A dedicated DHIS2 "Validation rule" application allows configuring complex validation rules based on data values from different data fields such as entering any data values which would lead to negative stock on hand values. When users execute the validation, DHIS2 will display a list of alerts in a dedicated sidebar. -The DHIS2 "Data Quality" app allows defining a z-score, identifying any data values which lie outside of the set range and are therefore likely to be outliers. - -### Data value completeness { #data-value-completeness } - -Before exporting data (either through the Import/Export app or the Data Visualizer app) it is important to check the following three settings: - -**Storing zero values** -Maintenance > Data element > "Store zero data values" -For logistics data collection this setting must be always selected. Otherwise zero values will appear as blank fields and it will be impossible to distinguish whether the user entered a zero or left the field blank. If "Store zero data values" is not selected, then zero values will neither appear in the Data entry forms nor in the analytics. Apart from making data completeness analyses impossible, it is also not possible to analyse any zero values such as stockouts. - -**Displaying zero values** -System Settings > Analytics > "Include zero data values in analytics tables" -If the setting "Store zero data values" is set, zero values are recorded in the Data entry form. However, those zero values are only shown in the analytics if in the "System Settings" app the setting "Include zero data values in analytics tables" is set in the "Analytics". - -**Completion of all data fields compulsory** -Maintenance > Data set > "All fields for data elements required" - -If the Data set is tagged as "All fields for data elements required" then the user must complete (enter values for) all data fields in the Data entry form. If this setting is selected and has been selected from the onset of data collection, then the system will ensure that all data has been recorded if the respective completeness report indicates 100% completion. In this case, the data completeness analysis can be limited to only two cases: -- Time periods when that setting was not (yet) selected -- Time periods for which the completeness report is not 100% - -The objective of the data value completeness analysis is determining how consistently data is actually being collected. Data value completeness can be determined across the following dimensions: -- All data fields -- By healthcare facility (Organisation Unit) -- By reporting period (month/year) -- By item (healthcare product) -- By LMIS data fields (stock on hand, stock distribution etc.) +| Accès | Accessibilité globale à partir d'une seule instance DHIS2 | +| Pertinence | Collecte de données (formulaires) respectant les bonnes pratiques | +| Exactitude | Réduction du nombre de champs de données, lecteurs de codes-barres pour l'identification des produits de santé, règles de validation | +| Complétude | Visualisation intuitive des lacunes dans les données, rapports sur la complétude des données, complétude disponible par défaut dans DHIS2-RTS | +| Précision | Vérification de la cohérence des données, règles de validation | +| Fiabilité (reproductibilité) | - | +| Cohérence | Vérification de la cohérence des données, mises à jour instantanée du stock disponible avec DHIS2-RTS | +| Rapidité et ponctualité | Analyse de la ponctualité des rapports, rapidité disponible par défaut avec DHIS2-RTS | +| Fréquence | Utilisation flexible de toutes les fréquences de rapport, rapport en temps réel (bonne pratique) avec DHIS2-RTS | +| Interprétabilité | Use of only essential LMIS data by design | +| Comparabilité | Formulaires de déclaration de données normalisés et disponibles | +| Charge de travail pour les collecteurs de données | Collecte minimale des données du LMIS par défaut, évite la redondance des données | +| Pertinence des sources de données | Visibilité complète de la collecte des données grâce aux fichiers journaux | +| Processus de collecte des données | Collecte de données numérisées, partage automatisé des données (synchronisation), élimination des erreurs dues à la duplication et à la copie des données. | +| Transparence et documentation | Transparence de la collecte des données grâce aux fichiers journaux | +| Transparence et crédibilité | Transparence et possibilité d'audit de toutes les données et de tous les fichiers journaux | + +## Analyse de la qualité des données du LMIS { #lmis-data-quality-analysis } + +DHIS2 est doté d'outils et d'applications qui permettent d'éviter la saisie de données erronées, de valider en temps réel les données déjà saisies et d'analyser (rétroactivement) les données saisies afin d'identifier les valeurs (potentiellement) fausses ainsi que les données qui n'ont pas été enregistrées à temps. + +### Validation des données du LMIS { #lmis-data-validation } + +Les fonctionnalités intégrées de DHIS2 concernant la validation des données permettent de valider les données lors de leur saisie et de minimiser ainsi les erreurs liées à la manipulation des données. La validation des données consiste à s'assurer que les valeurs saisies se situent dans des intervalles prédéfinis. +Le paramètre "Type de valeur" de DHIS2, intégré au système et disponible pour tous les "Éléments de données", permet de limiter la saisie des données à certains ensembles de nombres, tels que les nombres naturels ("Entier positif") ou les nombres entiers positifs (y compris zéro). Ce paramètre permet également d'éviter la saisie "accidentelle" de données, par exemple la saisie d'un texte dans un champ de données destiné aux chiffres. +Pendant la saisie des données, DHIS2 signale les valeurs qui se situent en dehors de l'intervalle de données défini en mettant le champ de données en surbrillance avec un fond rouge et en affichant un message d'erreur à l'écran. Par exemple, DHIS2 empêchera les utilisateurs de saisir des valeurs non entières ou négatives dans un champ "stock disponible" et les empêchera d'enregistrer un rapport tant que l'erreur n'aura pas été corrigée. +Les utilisateurs peuvent ouvrir une fenêtre contextuelle à l'écran qui affiche l'historique complet des données saisies sous la forme d'un graphique à barres et d'un graphique linéaire, ce qui permet d'identifier rapidement les valeurs incohérentes et les valeurs atypiques. +DHIS2-RTS (Système en temps réel) va encore plus loin en affichant non seulement une alerte en temps réel si des valeurs négatives sont saisies, mais aussi en empêchant l'utilisateur de sauvegarder les données saisies et de continuer à en saisir d'autres. De plus, il est possible de configurer une valeur minimale et une valeur maximale pour chaque champ de données, ce qui affichera une alerte en temps réel si l'utilisateur saisit une valeur qui se situe en dehors de l'intervalle configuré. +Le système DHIS2-RTS empêche la saisie de valeurs négatives pour le stock disponible, la saisie de valeurs non entières dans tous les champs de données et la saisie de valeurs négatives ou nulles pour tous les volumes de transaction. +Une application DHIS2 dédiée aux "règles de validation" permet de configurer des règles de validation complexes sur la base de valeurs de données provenant de différents champs de données, par exemple la saisie de toute valeur de données qui conduirait à des valeurs négatives pour le stock disponible. Lorsque les utilisateurs exécutent la validation, DHIS2 affiche une liste d'alertes dans une barre latérale dédiée. +L'application "Qualité des données" de DHIS2 permet de définir un z-score, qui identifie toutes les valeurs de données qui se situent en dehors de l'intervalle défini et sont donc susceptibles d'être des valeurs atypiques. + +### Complétude des valeurs de données { #data-value-completeness } + +Avant d'exporter des données (via l'application Importation/Exportation ou l'application Visualiseur de données), il est important de vérifier les trois paramètres suivants : + +**Enregistrement des valeurs nulles** +Maintenance > Élément de données > "Enregistrer les valeurs nulles" +Pour la collecte de données logistiques, cet paramètre doit toujours être sélectionné. Sinon, les valeurs nulles apparaîtront comme des champs vides et il sera impossible de déterminer si l'utilisateur a saisi un zéro ou s'il a laissé le champ vide. Si "Enregistrer les valeurs nulles" n'est pas sélectionnée, les valeurs nulles n'apparaîtront ni dans les formulaires de saisie ni dans les analyses. Outre l'impossibilité d'analyser la complétude des données, il ne sera pas non plus possible d'analyser les valeurs de ruptures de stock nulles. + +**Affichage des valeurs nulles** +Paramètres du système > Analyse > "Inclure les valeurs de données nulles dans les tableaux d'analyse" +Si le paramètre "Enregistrer les valeurs nulles" est activé, les valeurs nulles sont enregistrées dans le formulaire de saisie des données. Toutefois, ces valeurs nulles ne sont affichées dans les analyses que si le paramètre "Inclure les valeurs de données nulles dans les tableaux d'analyse" est activé dans l'application "Paramètres du système" dans "Analyse". + +**Remplissage obligatoire de tous les champs de données** +Maintenance > Ensemble de données > "Tous les champs requis pour les éléments de données" + +Si l'ensemble de données a l'option "Tous les champs requis pour les éléments de données" activé, l'utilisateur doit remplir (saisir des valeurs dans) tous les champs de données dans le formulaire de saisie des données. Si ce paramètre est sélectionné et qu'il l'a été dès le début de la collecte des données, le système s'assurera que toutes les données ont été enregistrées si le rapport de complétude correspondant indique un taux de complétude de 100 %. Dans ce cas, l'analyse de la complétude des données est limitée à seulement deux cas : +- Périodes pendant lesquelles ce paramètre n'a pas (encore) été sélectionné +- Périodes pour lesquelles le taux de complétude du rapport n'est pas à 100 % + +L'objectif de l'analyse de la complétude des données est de déterminer la cohérence de leur collecte. La complétude des données peut être déterminée en fonction des dimensions suivantes : +- Tous les champs de données +- Par établissement de santé (Unité d'organisation) +- Par période de déclaration (mois/année) +- Par article (produit de santé) +- Par champ de données du LMIS (stock disponible, distribution des stocks, etc.) - By time series (OU/item/LMIS data field) Data completeness is determined by simply counting the number of data fields for which values were reported without verifying the correctness of those values and then presenting those counts as percentages as well as histograms. @@ -256,28 +256,25 @@ It is possible, but very unlikely, that data values in a time series will be ide **Correlation** Data values which are highly correlated are also suspicious for being accurate. For example, if, over several time periods, stock receipts and stock distributions are identical this could only be explained by continuous shortages (whatever is received is being distributed immediately) or by "copy/pasting" data without measuring (counting etc.). -**Outlier analysis** -DHIS2 Data Quality app natively features the analysis of time series and the detection of outliers either by defining a treshold either as an absolute number or Z-score. The "Outlier Detection" table will then display a detailed report by Data element indicating the values, their mean and standard deviation together with the minimum and maximum values for the respective Data element. Scatter plots are another native DHIS2 feature which allow displaying and detecting outliers in a chart. -As the determination of whether individual data values should be considered as outliers depends on various factors such as the frequency of use of healthcare products and their variability, it is not possible to define general thresholds for defining outliers and the analysis will have to be carried out item by item. However, a systematic analysis is still possible by analysing data values with the largest deviation from the mean which have the greatest likelihood of being "real" outliers rather than artefacts. For example, any "normal" distribution quantity may (falsely) appear as an outlier after a prolonged period of stockouts during which no distributions were possible. +**Analyse des valeurs atypiques** +L'application Qualité des données de DHIS2 permet d'analyser les séries temporelles et de détecter les valeurs atypiques en définissant un seuil sous la forme d'un chiffre absolu ou d'un Z-score. Le tableau « Détection des valeurs atypiques » affiche alors un rapport détaillé par élément de données, indiquant les valeurs, leur moyenne et leur écart-type, ainsi que les valeurs minimale et maximale pour chaque élément de données. Les diagrammes de dispersion sont une autre fonctionnalité intégrée à DHIS2 qui permet d'afficher et de détecter les valeurs atypiques dans un graphique. +Étant donné que la détermination des valeurs de données individuelles à considérer comme atypiques dépend de divers facteurs tels que la fréquence d'utilisation des produits de santé et leur variabilité, il n'est pas possible de définir des seuils généraux pour définir les valeurs atypiques et l'analyse devra être effectuée élément par élément. Toutefois, une analyse systématique est toujours possible par l'analyse des valeurs de données présentant le plus grand écart par rapport à la moyenne, qui ont la plus grande probabilité d'être de "vraies" valeurs atypiques plutôt que des artefacts. Par exemple, toute quantité de distribution "normale" peut (faussement) apparaître comme une valeur atypique après une période prolongée de rupture de stock au cours de laquelle aucune distribution n'a été possible. -### Data report completeness and timeliness { #data-report-completeness-and-timeliness } +### Complétude et rapidité des rapports de données { #data-report-completeness-and-timeliness } -DHIS2 natively allows to set a "Days after period end to qualify for timely data submission" which allows to then determine whether reports were submitted on time. At the end of the monthly data recording users confirm completion by selecting the "Complete" button on the data entry screen. -This binary native DHIS2 reporting functionality allows users to confirm completeness of an entire Data set. The collected data depends on whether "All fields for data elements required" is configured in the Data set or not. If "All fields for data elements required" is not selected, the user can report the Data set as "Complete" even without entering a single value. If "All fields for data elements required" is collected the user will be prevented from selecting "Complete" unless all data fields are filled. However, if the user is forced to complete all data fields before selecting "Complete" for a Data set, the user may be tempted to record random values which will impair data quality. -This data and time stamp then allows to generate a range of default reports for the completeness of reports in terms of data recordings for each data field as well as the timeliness (on-time) of reported data values. -DHIS2 natively features the following reports for any kind of Data set: +DHIS2 permet de fixer un "Nombre de Jours après la période pour une transmission des données dans les délais", ce qui permet de déterminer si les rapports ont été soumis à temps. À la fin de l'enregistrement mensuel des données, les utilisateurs confirment l'achèvement en cliquant sur le bouton "Terminer" sur l'écran de saisie des données. Cette fonctionnalité binaire intégrée à DHIS2 permet aux utilisateurs de confirmer la complétude d'un ensemble de données. La collecte des données dépend de la configuration ou non de l'option "Tous les champs requis pour les éléments de données" dans l'ensemble de données. Si l'option "Tous les champs requis pour les éléments de données" n'est pas sélectionnée, l'utilisateur peut déclarer l'ensemble de données "Complet", même sans saisir une seule valeur. Si "Tous les champs requis pour les éléments de données" est sélectionné, l'utilisateur ne pourra pas déclarer l'ensemble de données "Complet" à moins que tous les champs de données ne soient renseignés. Toutefois, si l'utilisateur est contraint de renseigner tous les champs avant de sélectionner "Complet" pour un ensemble de données, il peut être tenté d'enregistrer des valeurs aléatoires, ce qui nuira à la qualité des données. Ces données et l'horodatage permettent ensuite de générer une série de rapports par défaut sur la complétude des rapports en termes d'enregistrement de données pour chaque champ, ainsi que sur la ponctualité des valeurs déclarées. DHIS2 propose par défaut les rapports suivants pour tout type d'ensemble de données : - Rapports effectifs - Rapports effectifs dans les délais - Rapports attendus - Taux de déclaration -- Reporting rate on time -For details please refer to the Implementation guidance chapter on [Data Quality Principles](#data-quality-principles) +- Taux de déclaration dans les délais +Pour plus de détails, veuillez vous référer au chapitre des Orientations de l'implémentation consacré aux [Principes de la qualité des données] (#data-quality-principles). -## LMIS data use { #lmis-data-use } +## Utilisation des données du LMIS { #lmis-data-use } -Although logistics and supply chain management is often associated with and perceived as handling (storing and transporting) physical goods and stocks, in reality logistics and main, and difficult, issues in logistics supply chain management is obtaining and processing timely and accurate data. The most difficult tasks in supply chain management of ensuring the availability of stocks in the place they are required and at the time they are required is entirely determined by data. Provided that stocks are available, the material handling (storage and transportation) is by far the easiest task. -Therefore data in general, and data from the last mile (first data mile) in particular, is absolutely essential, critical and indispensable. Only supply networks driven by first mile demand data can be effective as well as efficient and ensure that all goods required for providing high quality healthcare services are available at the service delivery point when they are needed. -Far too often, any logistics data is lumped together as "indicators" or even "Key Performance Indicators" (KPI) while actually logistics data serves different and distinct purposes. +Bien que la logistique et la gestion de la chaîne d'approvisionnement soient souvent associées et perçues comme la manipulation (stockage et transport) de biens physiques et de stocks, leur principal défi est en réalité l'obtention et le traitement de données précises et ponctuelles. La tâche la plus difficile de la gestion de la chaîne d'approvisionnement, qui consiste à garantir la disponibilité des stocks au lieu et au moment requis, est entièrement déterminée par les données. Si les stocks sont disponibles, leur manipulation (stockage et transport) est de loin la tâche la plus facile. +C'est pourquoi les données en général, et les données provenant du dernier kilomètre (premier kilomètre de données) en particulier, sont absolument essentielles et indispensables. Seuls les réseaux d'approvisionnement alimentés par les données relatives à la demande du premier kilomètre peuvent être efficaces et garantir que tous les biens nécessaires à la fourniture de services de santé de haute qualité sont disponibles au point de prestation de services et au moment voulu. +Bien trop souvent, toutes les données logistiques sont regroupées sous forme d'"indicateurs" ou même d'"indicateurs clés de performance" (ICP), alors qu'en réalité, les données logistiques servent des objectifs différents et distincts. ### Data use for inventory control { #data-use-for-inventory-control } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md index 1e0e31f3..109d9979 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.3/ReleaseNote-2.3.0.md" revision_date: '2020-11-03' tags: -- DHIS core version 2.35 - Android app version 2.3.0 - Implémentation +- DHIS core version 2.35 --- # Note de mise à jour de la version 2.3 de l'application Android du DHIS2 { #dhis2-android-app-version-23-release-note } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md index 177c9ae4..f6d64e1a 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.4/ReleaseNote-2.4.0.md" revision_date: '2021-04-27' tags: -- Android app version 2.4.0 -- DHIS core version 2.36 - Implémentation +- DHIS core version 2.36 +- Android app version 2.4.0 --- # DHIS2 Android App version 2.4 Release Notes { #dhis2-android-app-version-24-release-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md index 88a6a403..ca1b5d16 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.5/ReleaseNote-2.5.0.md" revision_date: '2021-11-24' tags: -- Android app version 2.5.0 - DHIS core version 2.37 - Implémentation +- Android app version 2.5.0 --- # DHIS2 Android App version 2.5 Release Notes { #dhis2-android-app-version-25-release-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md index a60a8254..a93e80b1 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.6/ReleaseNote-2.6.0.md" revision_date: '2022-04-18' tags: +- Implémentation - Version principale de DHIS 2.38 - Android app version 2.6.0 -- Implémentation --- # DHIS2 Android App version 2.6 Release Notes { #dhis2-android-app-version-26-release-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md index 270d6078..e8b7a1db 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.7/ReleaseNote-2.7.0.md" revision_date: '2023-05-11' tags: -- DHIS version 2.39 - Android app version 2.7.0 - Implémentation +- DHIS version 2.39 --- # DHIS2 Android App version 2.7 Release Notes { #dhis2-android-app-version-27-release-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md index 38b3c0a3..a793fc00 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.8/ReleaseNote-2.8.0.md" revision_date: '2023-05-08' tags: -- DHIS Version 2.40 - Application Android Version 2.8.0 - Implémentation +- DHIS Version 2.40 --- # DHIS2 Android App version 2.8 Release Notes { #dhis2-android-app-version-28-release-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md index 8bd9bb32..e59117ed 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/ReleaseNote-2.35.0.md" revision_date: '2020-10-22' tags: -- DHIS core version 2.35 - Implémentation +- DHIS core version 2.35 --- # Note de mise à jour de la version 2.35 du DHIS { #dhis-version-235-release-note } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md index adbbdfe9..fc4aa315 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.35 - Implémentation +- DHIS core version 2.35 --- # Notes de mise à jour de la version 2.35 { #235-upgrade-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md index 93b29bfc..c808799e 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/ReleaseNote-2.36.md" revision_date: '2021-10-27' tags: -- DHIS core version 2.36 - Implémentation +- DHIS core version 2.36 --- # DHIS version 2.36 Release Note { #dhis-version-236-release-note } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md index e3bc32f7..a0ac4a1a 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.36 - Implémentation +- DHIS core version 2.36 --- # 2.36 Upgrade Notes { #236-upgrade-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md index 7582045f..1bc881f3 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/ReleaseNote-2.38.md" revision_date: '2022-10-12' tags: -- Version principale de DHIS 2.38 - Implémentation +- Version principale de DHIS 2.38 --- # DHIS version 2.38 Release Note { #dhis-version-238-release-note } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md index 14a354c3..692cd8df 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/README.md" revision_date: '2023-08-30' tags: -- Version principale de DHIS 2.38 - Implémentation +- Version principale de DHIS 2.38 --- # 2.38 Upgrade Notes { #238-upgrade-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md index 695ca09d..505f328a 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/ReleaseNote-2.39.md" revision_date: '2023-01-26' tags: -- DHIS version 2.39 - Implémentation +- DHIS version 2.39 --- # DHIS version 2.39 Release Note { #dhis-version-239-release-note } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md index 95fce612..b1ce4422 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/README.md" revision_date: '2023-08-30' tags: -- DHIS version 2.39 - Implémentation +- DHIS version 2.39 --- # 2.39 Upgrade Notes { #239-upgrade-notes } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md index 3f2f2fc1..6f93d9cf 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/ReleaseNote-2.40.md" revision_date: '2023-05-12' tags: -- DHIS Version 2.40 - Implémentation +- DHIS Version 2.40 --- # DHIS2 version 40 Release Note { #dhis2-version-40-release-note } diff --git a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md index 1f0e17df..9d79fb25 100644 --- a/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md +++ b/projects/docs-full-site/fr/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/README.md" revision_date: '2023-08-30' tags: -- DHIS Version 2.40 - Implémentation +- DHIS Version 2.40 --- # 2.40 Upgrade Notes { #240-upgrade-notes } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md index 0b249aa8..2d2aceb2 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS version 2.39 +- Gestion --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md index b6401f81..fdefe153 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__installation-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS version 2.39 +- Gestion --- # Installation { #installation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md index 0e435b97..4371754e 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__monitoring-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS version 2.39 +- Gestion --- # Surveillance { #monitoring } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md index c17612f2..62d9f22d 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__upgrading-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS version 2.39 +- Gestion --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md index 021c0dd3..f0748ee7 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-239__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS version 2.39 +- Gestion --- # Utilisation de passerelles pour l'établissement de rapports SMS { #sms_report_sending } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md index 838c793f..6447bdc2 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.40 +- Gestion --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md index 1c8a6bf6..4e1b578b 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__debugging-as-another-user-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.40 +- Gestion --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md index 7ddbe47f..0508c1f3 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__installation-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.40 +- Gestion --- # Installation { #installation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md index 710c0b58..95478277 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-240__upgrading-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.40 +- Gestion --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md index 28887349..a62725d7 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__audit-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.41 +- Gestion --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md index 04463605..906a0bce 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__debugging-as-another-user-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.41 +- Gestion --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md index 3a860f0a..71d49444 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__installation-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.41 +- Gestion --- # Installation { #installation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md index 1f5dba5c..8eec7971 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-241__upgrading-md +++ b/projects/docs-full-site/fr/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: -- Gestion - DHIS Version 2.41 +- Gestion --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index c164ad77..1ae6c0f0 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/fr/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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # Audit { #audit } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index f16962fb..1af78c38 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/fr/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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # Using the User Impersonation Feature in DHIS2 { #user_impersonation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index 42db6769..8635217c 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/fr/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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # Installation { #installation } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index 94b24936..7474aaff 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/fr/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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # Surveillance { #monitoring } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index f5a13464..196359e1 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/fr/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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # Upgrading { #upgrading-dhis2 } diff --git a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index 3c3a534d..d0f479a8 100644 --- a/projects/docs-full-site/fr/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/fr/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: -- Gestion - Version Master de DHIS2 Central +- Gestion --- # Utilisation de passerelles pour l'établissement de rapports SMS { #sms_report_sending } diff --git a/projects/docs-full-site/pt/.cache_timestamp b/projects/docs-full-site/pt/.cache_timestamp index d7cf1f52..6a3aded0 100644 --- a/projects/docs-full-site/pt/.cache_timestamp +++ b/projects/docs-full-site/pt/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:22:50Z \ No newline at end of file +2024-10-19T21:22:30Z \ No newline at end of file diff --git a/projects/docs-full-site/ru/.cache_timestamp b/projects/docs-full-site/ru/.cache_timestamp index d5281731..1af5d763 100644 --- a/projects/docs-full-site/ru/.cache_timestamp +++ b/projects/docs-full-site/ru/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:23:00Z \ No newline at end of file +2024-10-19T21:22:43Z \ No newline at end of file diff --git a/projects/docs-full-site/ru/IMPLEMENT__DATA-USE__data-visualization-md b/projects/docs-full-site/ru/IMPLEMENT__DATA-USE__data-visualization-md new file mode 100644 index 00000000..e5f363d3 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__DATA-USE__data-visualization-md @@ -0,0 +1,341 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/data-use/data-visualization.md" +revision_date: '2024-10-18' +tags: +- Осуществлять +--- + +# Data Visualization Best Practices { #data-visualization-best-practices } + +## Introduction { #introduction } +Data visualization is a powerful tool for understanding and communicating data. The choices made in visualization are crucial and should be guided by the type of data and the message that needs to be conveyed. Proper visualization can reveal patterns, trends, and insights that might be missed in raw data. Fortunately, data visualization follows established rules and design principles that align with the type of variables being used, ensuring that it is not a matter of personal opinion but rather a structured and effective approach. + +## Variables { #variables } + +**Any Measurable Characteristic is a Variable** +Variables can be broadly classified into two categories: + +1. Categorical (Qualitative) +2. Numerical (Quantitative) + +Understanding these categories is essential to selecting the correct chart type and designing it effectively. + +### Categorical Variables { #categorical-variables } + +- **Nominal** - Unordered categories (e.g., marital status). These categories do not have a meaningful order. + - For example, marital statuses like single, married, divorced, and widowed are distinct categories without a ranked order. +- **Ordinal** - Categories with a meaningful order (e.g., disease status). These categories have a logical sequence. + - For example, disease severity might be classified as mild, moderate, and severe, which has an inherent order. + +> **Note** +> +> **Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. + +![Variable categories](resources/images/dataviz_001.png) + +### Numerical Variables { #numerical-variables } + +- **Discrete** - Countable number of variables (e.g., number of siblings, dead/alive = discrete dichotomous). Discrete variables take specific values and cannot be meaningfully divided. + - For example, you can't have half a sibling or be half alive. +- **Continuous** - Infinite values within a given interval (e.g., weight and height, pass/fail = continuous dichotomous). Continuous variables can take any value within a range. + - For example, height can be 170.5 cm or 170.55 cm. + +## Choosing the Right Chart { #choosing-the-right-chart } + +What’s the best way to choose the right visualization for the data at hand? [From data to Viz](https://www.data-to-viz.com/) proposes an exhaustive map of visualizations matched to the category of data. + +Another Chart Chooser is mapped in the [Extreme Presentation Method](https://extremepresentation.com/). + +![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.jpg) + +The summary below is based on the visualizations available in the core DHIS2 Data Visualizer App. + +### Categorical Variables { #categorical-variables } + +#### Single categorical variable { #single-categorical-variable } + +- **Barplot**: Displays the frequency or proportion of categories using bars. Each bar represents a category, and its height indicates the value. +- **Pie chart**: Represents parts of a whole as slices of a circle. Each slice’s size is proportional to the category's frequency. +- **Spider plot**: Also known as a radar chart, it shows multiple categories on axes starting from the same point. Useful for displaying performance metrics across different categories. + +#### Multiple categorical variables { #multiple-categorical-variables } + +- **Grouped/stacked Barplot**: Grouped barplots show bars for each category side by side, while stacked barplots stack them on top of each other. +- **Heatmap**: Uses colour to represent values in a matrix format, where one dimension represents one category and another dimension represents the second category. + +### Numerical Variables { #numerical-variables } + +#### Single numerical variable { #single-numerical-variable } + +- **Histogram**: Shows the distribution of a numerical variable by dividing the data into bins and displaying the frequency of observations in each bin. + +#### Two numerical variables { #two-numerical-variables } + +- **Ordered** + - **Area plot**: Similar to line plots but with the area under the line filled. Useful for showing cumulative values over time. + - **Line plot**: Displays information as a series of data points connected by straight lines. Suitable for trends over time. +- **Unordered** + - **Histogram**: This can also be used to compare the distributions of two different variables. + - **Scatter plot**: Plots two variables as points on a Cartesian plane. Each point represents an observation's values on the two variables. + +#### Three numerical variables { #three-numerical-variables } + +- **Stacked area plot**: Shows multiple series of data as layers stacked on top of each other. Each layer represents a series' value. +- **Line plot**: Can be used to show multiple series of data over time. + +#### Four or more numerical variables { #four-or-more-numerical-variables } + +- **Ordered**: + - **Stacked area plot**: Shows multiple series of data as layers stacked on top of each other. Each layer represents a series' value. + - **Line plot**: This can show trends of several variables over time. +- **Unordered**: + - **Heatmap**: Uses color gradients to represent data values in a matrix, making it easy to spot patterns and outliers. + +### Specific Visualization Styles { #specific-visualization-styles } + +> **Note** +> +> **Data speaks louder than words!** + +In data visualization, choosing the right type of chart or graph is crucial for effectively communicating your data. Each visualization style has its strengths and is best suited for specific types of data and analytical purposes. This chapter explores a variety of visualization styles, detailing their applications and best practices. Whether you're looking to show trends over time, compare quantities, highlight correlations, or illustrate parts of a whole, selecting the appropriate visualization method will enhance clarity and insight. By understanding the nuances of each style, you can ensure that your data tells a compelling and accurate story. + +![Data visualization styles available in DHIS2](resources/images/dataviz_025.png) + +#### Correlation { #correlation } + +> **Caution** +> +> Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. + +- **Scatterplot**: Shows the relationship between two continuous variables, each having its axis. Each point represents an observation's values on the two variables. It's useful for identifying trends, clusters, and outliers. For example, a scatterplot can display the relationship between the number of immunization campaigns conducted in various districts and the resulting immunization coverage rate. + + +![Scatterplot found in the EPI-Program Performance Dashboard plotting coverage vs dropout rates](resources/images/dataviz_003.png) + +- **Column + line timeline**: Shows the relationship between an amount (columns) and a rate (line). This combination is often used to compare a quantity with its rate of change over time, such as HIV-tested patients (columns) and positivity rate (line). + +![Double axis chart with columns and line showing measles cases and coverage](resources/images/dataviz_004.png) + +#### Ranking { #ranking } + +> **Note** +> +> Emphasizes the item's position in an ordered list rather than the absolute value. + +- **Ordered bars/columns**: Shows ranks of values more easily when sorted. This visualization helps to quickly see the highest and lowest values. An ordered bar column chart can be used to display the number of TB cases in each district, sorted in descending order to highlight the districts with the highest burden. + +![Ordered stacked bar chart of TB cases by reporting district](resources/images/dataviz_005.png) + +- **Slopes**: Shows how ranks have changed over time. Useful for visualizing changes in ranking positions, such as tracking the incidence of malaria in different regions over several years to see how the ranking of regions by incidence rate changes over time. + +![Slopes on inpatient malaria incidence across different Districts through time](resources/images/dataviz_006.png) + +#### Change Over Time { #change-over-time } + +> **Note** +> +> Keep gaps between columns small to highlight data shape. +Use markers for irregular data points. + +- **Column**: Emphasizes changing trends. Columns are used to show discrete data points over time. For example, monthly case figures can be shown as a column chart. + - **Keeping the space between columns** in a column chart close to each other is crucial for emphasizing the continuity and patterns within the data. When columns are placed closely together, it creates a more cohesive visual representation, making it easier to compare values across categories or periods. This proximity helps the viewer quickly identify trends, variations, and overall data distribution, enhancing the clarity and effectiveness of the chart. Additionally, minimizing the gaps between columns reduces visual clutter and ensures that the focus remains on the data itself, rather than on the empty spaces. + +![Columns for monthly HIV cases](resources/images/dataviz_007.png) + +- **Line**: Best for visualizing continuous data over time. Line charts are effective for showing trends, cycles, and fluctuations. For example, a line chart could track the changes in CD4 cell counts over time for a cohort of patients, illustrating the impact of treatment interventions. + +- **Year over Year (column and line)** - Compares the same period across different years to show trends over multiple years using lines. For example, the YoY line could be used to compare malaria incidences across several years, while the YoY columns could be used to visualizing the annual malaria number of malaria cases over multiple years. + +- **Area charts**: Good to show changes in totals but tricky for components. Area charts are powerful for illustrating trends and changes over time, providing a strong visual impact by highlighting the magnitude and total values of data sets. They are particularly effective for showing cumulative data and allowing comparisons of multiple data series. However, they can become cluttered and difficult to read when multiple categories are involved, as distinguishing individual components can be challenging. Additionally, changes in lower layers can distort the perception of upper layers, potentially leading to misinterpretation. While effective for highlighting totals, area charts are less suitable for discrete data points or non-cumulative data and can be problematic for colourblind viewers or black-and-white prints. For example, it could be tracking the total number of TB or malaria cases reported across different regions over a year to visualize the overall burden and trends. + +![Area chart for the volume of malaria cases in three districts](resources/images/dataviz_008.png) + +#### Magnitude { #magnitude } + +> **Note** +> +> Small gaps highlight data shape. Best for a single series of data. + +- **Column/Paired column/bar**: Compare sizes, usually numbers rather than rates or percentages. For instance, HIV case figures for different regions can be compared using a bar chart. In this case, it is appropriate to keep the distance between the columns as they represent separate entities rather than variables through time. + +![Paired columns of HIV new cases and HIV new cases who started ART across different districts](resources/images/dataviz_009.png) + +#### Performance Metrics { #performance-metrics } + +- **Radar**: Radar charts, also known as spider or web charts, are efficient for displaying multiple variables, making them ideal for visualizing performance metrics such as the strengths and weaknesses of a team across various skills. They allow for a comprehensive view of data at a glance, highlighting comparative performance across different categories. However, radar charts can become cluttered and hard to interpret with more than five groups, leading to overlapping lines and a confusing presentation. This type of chart is not suitable for trendline visualizations as it does not effectively display changes over time. Pros of radar charts include their ability to compare multiple variables simultaneously and their intuitive, visual appeal. Cons include potential clutter with too many variables, difficulty in precise comparison, and the risk of misinterpretation due to the distortion of area size. Common mistakes include overloading the chart with too many variables, not starting scales from zero, and using them to represent data trends rather than comparative metrics. + +![Radar chart on Rehab condition groups and their use across two districts](resources/images/dataviz_010.png) + +#### Part-to-Whole { #part-to-whole } + +> **Tip** +> +> Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** + +![Imrpove the visualization choosing the most suitable colour set](resources/images/dataviz_022.png) + +- **Stacked column/bar**: Shows how a single entity breaks down into components. This is useful for comparing the composition of different groups. +Stacked columns or bar charts **should be avoided when** a detailed comparison of individual data points is required, when dealing with a large number of categories when showing trends over time, when data categories are not additive, when highlighting individual segment changes, or when data intervals are non-uniform. These charts can obscure important details and lead to misinterpretation if used improperly. + +![Stacked columns for TB cases - lab confirmed and clinically confirmed](resources/images/dataviz_011.png) + +- **Pie chart**: Each slice represents a part of the whole, which can be useful for showing proportions. Pie charts **should be avoided when** comparing multiple categories, showing trends over time, needing precise value representation, dealing with negative values, when the total is not meaningful, and for complex data sets. These limitations can lead to misinterpretation and obscure important details, making other chart types like bar, line, or scatter plots more appropriate for these scenarios. + +![Sex for notified TB cases](resources/images/dataviz_012.png) + +#### Single Value Display { #single-value-display } + +- **Gauge**: Used to represent a single value within a range, similar to a speedometer. It is ideal for showing progress towards a target or current status against a benchmark. It could be used to display the current immunization coverage rate as a percentage of the target. + +![Coverage rate for BCG](resources/images/dataviz_026.png) +- **Single Value**: Displays a single metric prominently. Useful for highlighting key performance indicators (KPIs) or critical numbers. In DHIS2 it is possible to associate colour-based legends to highlight progress or thresholds. + +![Coverage rate for BCG with a colour-based legend representative of the EPI coverage threshold](resources/images/dataviz_027.png) + +#### Detailed Analyses { #detailed-analyses } + +- **Pivot Tables**: Useful for summarizing, analyzing, exploring, and presenting summary data. Pivot tables are interactive and can be used to create custom reports. For example, tables can be used to summarize the number of TB cases by district and month, allowing users to drill down into specific data points for more detailed analysis. + +![Pivot table of the target population for a supplementary immunisation activity by age groups, distance from the PoC, and locations. Note the row and column totals as well as the subtotals by category](resources/images/dataviz_028.png) + +**Scorecards** provide an added value by visually representing key performance indicators (KPIs) against predefined targets. They are particularly useful for tracking progress, identifying areas for improvement, and communicating performance at a glance. For instance, a scorecard could display the performance of various health facilities in terms of patient satisfaction, staff efficiency, and resource utilization. This tool helps stakeholders quickly assess whether they are meeting their goals and where interventions might be needed. Scorecards foster accountability and transparency within health systems, ensuring everyone is aligned towards common objectives. + +![Scorecard highlighting the MR coverage reported by routine EPI- and SIA-related activities](resources/images/dataviz_031.png) + +#### Spatial { #spatial } + +- **Choropleth**: Standard for rates on maps. Uses varying shades of a colour to represent data values for different regions. For example, population density by region can be shown using a choropleth map. + +> **Note** +> +> **Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. + +![Map showing the percentage of PTB-BC cases in a region](resources/images/dataviz_013.png) + +- **Proportional symbol**: Good for totals. Symbols of different sizes are placed on a map to indicate the value at each location. + +![Map showing number of notified cases in a region](resources/images/dataviz_014.png) + +![Map showing the location of the unvaccinated children and the reason for the missed vaccination](resources/images/dataviz_015.png) + +- **Dot density**: Shows the location of events. Each dot represents a set number of occurrences of a phenomenon. + +![Map showing the population density in the region](resources/images/dataviz_021.png) + +- **Heat map**: Uses grid-based data values with an intensity colour scale. It shows data density and can be used for data that varies smoothly over an area, like temperature rates. + +![Map showing the mean temperatures across the country](resources/images/dataviz_016.png) + +#### Google Earth Integration with DHIS2 { #google-earth-integration-with-dhis2 } + +DHIS2 offers powerful integration with Google Earth Engine, allowing users to access a range of detailed datasets, such as population (WorldPop), building footprints, elevation, land use, and climate data. + +The detailed steps and best practices for integrating Google Earth Engine with DHIS2 can be found in the [DHIS2 Documentation](https://community.dhis2.org/t/using-population-elevation-landcover-and-climate-layers-in-dhis2-maps/51586) and the [DHIS2 Version 2.39 Overview](https://dhis2.org/overview/version-239/). These pages provide comprehensive guides and updates on the functionalities of DHIS2, including the integration with Google Earth Engine and the capabilities of using population, elevation, landcover, and climate layers within the DHIS2 Maps application. + +##### Best Practices for Integration { #best-practices-for-integration } + +- **Data Utilization**: Use the extensive datasets available from Google Earth Engine to enhance your spatial analysis. This includes integrating population density maps, land use patterns, and climate data to better understand health trends and resource distribution. +- **Customization**: Tailor the integration to meet the specific needs of your health programs by leveraging the flexibility of DHIS2’s mapping capabilities. This can involve customizing map layers to highlight key indicators relevant to your programs. +- **Performance Monitoring**: Regularly monitor and update your Google Earth Engine access and configurations to ensure optimal performance and data accuracy. + +### Common Mistakes { #common-mistakes } + +#### Ignoring Data Density { #ignoring-data-density } + +Overlooking the issue of data density can lead to charts that are cluttered and difficult to interpret. When data points overlap too much, important patterns and trends can be obscured, making it challenging for viewers to extract meaningful insights. + +#### Spaghetti Chart { #spaghetti-chart } + +**Avoid cluttering your chart with too much information**. A spaghetti chart is an overly complex line chart with many intersecting lines, making it hard to read. + +![The chart appears cluttered and difficult to interpret](resources/images/dataviz_017.png) + +Alternatives to avoid messy charts: + +- **Small multiples**, also known as panel charts or trellis charts, are a series of similar graphs or charts using the same scale and axes, allowing easy comparison across different categories. You can create multiple line charts and display them in the dashboard one next to the other. E.g. Showing the monthly TB cases for different regions in separate subplots. +- **Organizational Units**. Check whether it is necessary to provide the info for every OU. Highlight one or a few key series in a line chart and show the remaining series in a more muted colour to reduce clutter and emphasize important trends. E.g. Highlighting the regions with the highest TB cases while showing other regions in lighter lines for context. + +![Cluttered graph by lower OUs](resources/images/dataviz_032.png) + +- **Interactive dashboards** allow users to filter and explore data dynamically, which can be especially useful for complex multi-series data. In DHIS2 Dashboards users can select specific regions or periods to view detailed trends in TB cases. +- **Heatmaps** use colour to represent data values in a matrix, allowing for easy comparison of values across two dimensions. The maps in DHIS2 can be displayed as SIngle (Aggregate), Split views, or Timeline. + +#### Overcluttered Visuals { #overcluttered-visuals } + +Adding too many elements makes the chart hard to read. **Simplify visuals by focusing on the most relevant data and using clear, concise legends and labels**. + +![Overloading a map with too many layers and data points](resources/images/dataviz_023.png) + +In addition, this map uses a colour scheme that might not be accessible to colourblind individuals, making it difficult to interpret for a significant portion of the population. **Use colorblind-friendly palettes** that ensure all users can distinguish between different data values. Tools like [ColorBrewer](https://colorbrewer2.org/) provide palettes designed for colourblind accessibility. Refer to the “Part-to-whole” section of the document to see how to change the colour scheme of your visualizations. + +#### Crammed Dashboards { #crammed-dashboards } + +Squeezing too many visualizations into a single dashboard can make them unreadable and ineffective. Each visualization should have enough space to be interpreted. Overloading a dashboard with too many elements can overwhelm the viewer and obscure key insights. Aim for a balanced layout where each visualization can be easily read and understood. + +![The items in the dashboards are too small for what they need to convey, the labels are unreadable, the pivot table does not have space to display the variables](resources/images/dataviz_023.png) + +#### Lack of Context { #lack-of-context } + +Failing to provide necessary context, such as labels, titles, legends, and explanatory notes, can leave the audience confused about what the chart is representing. **Context is crucial for helping viewers understand the data being presented and drawing accurate conclusions**. + +A visualization should always have: + +- **Titles**: Always include a descriptive title that clearly states what the chart is about. The title should provide enough information to make the chart understandable at a glance. +- **Axis Labels**: Label the x-axis and y-axis to specify what data they represent. Include units of measurement where applicable. +- **Legends**: Provide a legend when using colours, symbols, or different lines to distinguish between multiple data series or categories. Ensure the legend is clear and easy to interpret. +- **Explanatory Notes**: Include any necessary explanatory notes or footnotes to clarify data sources, any assumptions made, or specific data points that require additional context. In DHIS2 one could add notes and explanations by clicking the three dots on teh right of the visualizations and selecting “Show details and interpretations”. + +![Contextualized graph](resources/images/dataviz_024.png) + +> **Caution** +> +> Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. + +#### Pie Chart { #pie-chart } + +**Humans are bad at reading angles**. Avoid pie charts for detailed comparisons. In a pie chart, it can be difficult to compare the sizes of slices accurately. +A bar or a column can be equally used through horizontal bars that focus more on the comparison between the categories than the values. + +![Pie charts with a lare number of categories to be compared](resources/images/dataviz_018.png) + +#### Totals and Parts { #totals-and-parts } + +**Presenting a total and its parts in the same chart can be misleading, redundant, and visually cluttered, making it difficult for the audience to accurately interpret the data**. To enhance clarity and focus, it is better to use separate charts for the total and its components. + +- **Misleading Representation**: Combining the total and its parts in the same chart can be misleading. The total value includes all parts, and placing them together may create a false impression of comparison between different metrics. Moreover, including both totals and parts in a single chart can detract from the clarity and focus. The audience might find it confusing to distinguish between the total and the individual contributions. +- **Scale Issues**: The total and its components often have vastly different scales. The total number will always be larger than any of its parts, making it difficult to interpret and compare the smaller values accurately. +- **Redundancy**: Showing both the total and its parts in the same chart is redundant. Since the total is simply the sum of the parts, it doesn’t provide additional information and can clutter the visualization. + +![Doses given as a total within the country and the doses by district](resources/images/dataviz_019.png) + +As an alternative, one could opt for: + +- **Separate Bar Charts**: Use one bar chart to display the total number of doses given in the country and another bar chart to show the doses distributed by each district. This separation maintains clarity and allows for easier comparison and understanding. +- **Stacked Bar Chart**: Use a stacked bar chart where each bar represents the total doses for the country, but the bar is divided into segments representing each district. This method keeps the parts and totals together but differentiates the contributions of each part. This is only acceptable if the number of entities is not cluttering the visualization and falling into the same trap as the spaghetti chart. + +#### Inappropriate Chart Types { #inappropriate-chart-types } + +Using the wrong type of chart for the data can mislead viewers and obscure the intended message. Each chart type has its strengths and weaknesses, and choosing the correct one is crucial for effective data visualization. + +- **Example 1**: Using a line chart to display categorical data, such as the number of health facilities by type (e.g., clinics, hospitals, mobile units), is inappropriate. Line charts are designed to show trends over time and assume a sequential order in the data points. Categorical data, however, do not have a natural order and are best represented by bar charts or pie charts. +- **Example 2**: Using a pie chart to display small differences in a large number of categories, such as the number of malaria cases in different regions, is inappropriate. Pie charts work best with a small number of categories where differences are large and easily distinguishable. With many categories, the slices become too small to differentiate, making the chart hard to read and interpret. Bar charts are better for comparing many categories with small differences. For example +- **Example 3**: Using a radar chart (also known as a spider chart) to display trendlines over time is inappropriate. Radar charts are designed to compare multiple variables across different categories in a circular format. They are not suited for showing trends over time because they do not follow a sequential order and can make it difficult to interpret changes over time. Line charts or bar charts are more appropriate for illustrating trends over time as they depict changes in data points along a continuous timeline. + +![Spider chart used wrongly to display the changes in notified TB cases over time](resources/images/dataviz_029.png) + +- **Example 4**: Using a double-axis chart with columns to display the number of HIV tests performed in different districts (x-axis) and a line to depict the HIV test positivity rate across these districts is inappropriate. The line incorrectly implies a sequential relationship and trend across districts. Each district's positivity rate is a standalone value and should not be connected as if they follow a continuous trend. Instead, the best way to visualize this data would be a pivot table. A pivot table allows you to display the number of HIV tests and the positivity rate side by side for each district without implying a false trend or relationship between the districts. + +![Double axis wrongly unifying stand alone entities](resources/images/dataviz_030.png) + +#### Separate Entities vs Change Over Time { #separate-entities-vs-change-over-time } + +When visualizing separate entities, such as the doses of a vaccine distributed across different districts, using distinct columns for each district helps clearly distinguish between the different entities. This approach ensures that the data for each district is easy to compare, highlighting the variations in vaccine distribution between districts. Conversely, when visualizing changes over time, such as the number of vaccines distributed in a specific organizational unit, columns should be placed with minimal separation to emphasize the continuity and trends over the period. This close placement helps to illustrate the flow and progression of vaccine distribution, making it easier to identify patterns, peaks, and troughs in the data. + +![Separate entities on the left vs continuous change over time on the right](resources/images/dataviz_020.png) + +### Conclusion { #conclusion } + +**Effective data visualization requires selecting the appropriate chart type based on the variable types and the message you wish to convey**. It’s essential to avoid common mistakes and ensure clarity for the audience. For instance, when illustrating spatial distribution, a map is more relevant as it effectively shows clusters and the distribution of high and low-coverage areas. When checking efforts, absolute numbers are more meaningful if they include target values for comparison. Additionally, for accurate comparisons, it is crucial to normalize data distribution. Good visualization practices enhance understanding and facilitate better decision-making, ensuring that the data tells a compelling and accurate story. + +Would you like to test your knowledge of variables and data visualization best practices? **Take the [quiz](https://docs.google.com/forms/d/e/1FAIpQLSddz_jtVrFSJssNiCYTHQ12tm6x1A6Gs6QB5Lhlmeq0Je3vDw/viewform?usp=sf_link)**! + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md new file mode 100644 index 00000000..7d9305f2 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -0,0 +1,206 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-design.md" +revision_date: '2023-03-31' +tags: +- Осуществлять +--- + +# COVID-19 Surveillance - Aggregate System Design Guide { #c19-agg-design } + +## Purpose { #purpose } + +The COVID-19 Surveillance Aggregate System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +This aggregate design has been updated to reflect new aggregate reporting requirements from the [Global surveillance of COVID-19: WHO process for reporting aggregated data](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form), last updated on August 7, 2020. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| **Type of Surveillance Package** | **Case-based Surveillance (Tracker)** | **Case surveillance line-listing (Event)** | **Case surveillance (Aggregate)** | +| --- | --- | --- | --- | +| **Description** | Enrolls a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables weekly reporting of key aggregate data points | +| **Pros** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| **Cons** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation)| + +**This document covers only the design of the aggregate package**; separate system design documents are available for DHIS2 Tracker and Line-listing (event-based) packages. As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The aggregate package is designed to meet the most critical reporting requirements and analytical capacities for surveillance and response. + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated August 7, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +The aggregate COVID-19 surveillance package includes + +1. Weekly aggregate data set and data elements for key COVID-19 surveillance reporting +2. Categories for data disaggregation +3. Core indicators +4. Dashboard and its items + +The dataset captures a minimum number of data points that meet the current WHO weekly reporting requirements; and generate a core set of indicators and dashboards for national and sub-national decision-makers to rapidly analyze and respond to disease trends. + +| **Name** | **Periodicity** | **Purpose** | +| --- | --- | --- | +| Aggregate Weekly Surveillance | Weekly| Reporting of key COVID-19 surveillance data including cases, tests and deaths. | + +It is recommended that the weekly dataset is assigned to Organisation Units at the lowest level of the health system feasible for reporting data, such as health facilities. + +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). + +### Intended users { #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. +- 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 + +## Datasets { #datasets } + +This dataset is intended to capture weekly data needed for rapid response to disease transmission. If the burden of reporting becomes too great or when it is no longer considered an emergency situation in the country, the data set may be changed to monthly according to MOH policies. + +### Daily Surveillance Data Elements { #daily-surveillance-data-elements } + +The following lists the data elements and disaggregation (category combinations) included in the data set: + +| **Data Elements** | **Category Combinations** | +| --- | --- | +| New Confirmed Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Confirmed Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Hospitalized Cases | None | +| New Discharged Cases | None | +| New Cases Among Health Workers (Confirmed + Probable) | None | +| New Deaths Among Health Workers (Confirmed + Probable) | None | +| Number of Persons Tested for COVID-19 | None | +| Number of persons Tested with PCR Assay | None | +| Transmission Classification | None | + +### Weekly Surveillance Data Entry Form { #weekly-surveillance-data-entry-form } + +- **Section 1: New confirmed and probable Cases** + +Data should be entered for all new confirmed and probable cases reported during the reporting period. Confirmed cases refer to laboratory confirmed cases per WHO guidance; probable cases are defined by WHO as cases where laboratory test result is inconclusive; however countries may apply their own case definitions. The total column is automatically summed during data entry. +![Picture1](resources/images/AGG_Picture1.png) + +- **Section 2: New confirmed and probable deaths** + +Data should be entered for new confirmed and probable deaths reported during the reporting period. The total column is automatically summed during data entry. + +![Picture2](resources/images/AGG_Picture2.png) + +- **Section 3: Health worker infection and death** + +This section captures data for health workers' new confirmed and probable cases including deaths reported during the reporting period. + +![Picture3](resources/images/AGG_Picture3.png) + +- **Section 4: Hospitalisation and discharges** + +This section captures data for new hospitalisation and discharges during the reporting period. + +![Picture4](resources/images/AGG_Picture4.png) + +- **Section 5: Tests conducted** + +This section captures data for tests conducted with additional requirement to report tests conducted using PCR during the reporting period + +![Picture5](resources/images/AGG_Picture5.png) + +- **Section 6: Transmission Classification** + +This section summarizes the major form of transmission classification experienced by the reporting unit. + +![Picture7](resources/images/AGG_Picture6.png) + +### Customizing Data Entry Forms { #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) + +## Data Validation { #data-validation } + +The following data validation rules have been configured. These validation rules do not run in the data entry form itself as it is anticipated that the urgent reporting of data where events occur in different time frames (e.g. one week can see only 3 new cases but 5 deaths). + +| **Name** | **Operator** | **Instruction** | **Left side description** | **Right side description** | +| --- | --- | --- | --- | --- | +| COVID19 - PCR tests \<= tested | less\_than\_or\_equal\_to | Tested with PCR should be less than or equal to total tests conducted | Tested with PCR | Tested conducted | +| COVID19 - New Cases hospitalised \<= All New Cases | less\_than\_or\_equal\_to | New Cases hospitalised should be less than or equal to all new cases | New Cases hospitalised | All New Cases | +| COVID19 - New confirmed deaths \<= New confirmed cases | less\_than\_or\_equal\_to | New confirmed deaths should be less than or equal to New confirmed cases | New confirmed deaths | New confirmed cases | +| COVID19 - Probable deaths \<= New probable cases | less\_than\_or\_equal\_to | Probable deaths should be less than or equal to New probable cases | Probable deaths | New probable cases | +| COVID19 - New deaths among HW (confirmed + probable) \<= All deaths reported | less\_than\_or\_equal\_to | New deaths among HW (confirmed + probable) should be less than or equal to All deaths reported | New deaths among HW (confirmed + probable) | All deaths reported | +| 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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Please refer to the [installation guidance](covid-19-aggregate-installation.html) for more information. + +## Indicators { #indicators } + +From the data captured, we can calculate at least the following indicators, many of which are recommended by the WHO for [weekly reporting](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) and present them in a dashboard. All COVID-19 program indicators are assigned to the Indicator Group 'COVID19'. + +| **name** | **description** | +| --- | --- | +| COVID19 - New Confirmed Deaths | Number of new confirmed deaths | +| COVID19 - New Cases Among HW (Confirmed + Probable) | Number of New Cases Among HW (Confirmed + Probable) | +| COVID19 - Proportion of HW amongst reported cases (%) | Proportion of HW amongst reported cases (%) | +| COVID19 - Active cases | Number of of active cases | +| COVID19 - Closed cases | Number of closed cases | +| COVID19 - New Confirmed cases | Number of new Confirmed cases | +| COVID19 - Recovery rate (%) | Recovery rate of confirmed cases | +| COVID19 - Case fatality rate among HW (%) | Case fatality rate among HW | +| COVID19 - New Hospitalized Cases | New Hospitalized Cases | +| COVID19 - Tested | Total number of tests conducted | +| COVID19 - Tested with PCR Assay | Tested with PCR assay | +| COVID19 - Positivity rate (%) | Positivity rate | +| COVID19 - New Probable Cases | Number of new probable cases | +| COVID19 - New Discharged Cases | Number of new discharged cases | +| COVID19 - New Deaths Among HW (Confirmed + Probable) | Number of new deaths among HW (Confirmed + Probable) | +| COVID19 - Proportion of PCR tests (%) | Proportion of PCR tests conducted | +| COVID19 - All cases (Confirmed + Probable) | Number of all cases (Confirmed + Probable) | +| COVID19 - New Probable Deaths | Number of new probable deaths | +| COVID19 - Case fatality rate (%) | Case fatality rate among confirmed cases | + +## Dashboards { #dashboards } + +Key analytic items have been configured and added onto the dashboard “COVID19 - Aggregate Weekly Surveillance”. These items include; pivot tables, charts and a map designed to provide data visualization for some of the data captured based on the indicators. In the process of adopting this package, users can modify or create additional items as suits their analytical needs and equally make the necessary adjustments to the dashboard. + +| **name**|**type**| +| --- | --- | +|COVID19 - Tested, tests with PCR and positivity rate by subnational level this year |Pivot table| +|COVID19 - HW amongst reported cases this year |Chart| +|COVID19 - Fatality rate amongst HW.|Chart| +|COVID19 - New confirmed cases and deaths in the last 12 weeks|Chart| +|COVID19 - Cumulative tests conducted, cases reported, hospitalised, discharged and deaths|Chart| +|COVID19 - Cumulative confirmed cases by subnational|Map| +|COVID19 - Deaths by age groups last weeks|Chart| +|COVID19 - Confirmed cases by sex in the last 14 weeks|Chart| +|COVID19 - Closed and active cases at subnational last months|Chart| +|COVID19 - Case recovery and fatality rates last 12 weeks|Chart| +|COVID19 - Active and Closed Cases last 12 weeks|Chart| + +## References { #references } + +- Installation guidance: [https://www.dhis2.org/covid-19](covid-19-aggregate-installation.html) +- WHO Interim guidelines on nCoV-19 surveillance & case definitions (last updated March 20, 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions>]() +- WHO COVID-19 surveillance data dictionary (v6) +[https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98\_2](https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2) +- WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) + [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +- WHO Coronavirus situation reports + [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports>]() +- Global surveillance of COVID-19: WHO process for reporting aggregated data +[https://www.who.int/publications/i/item/aggregated-weekly-reporting-form](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md new file mode 100644 index 00000000..b31bed64 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-installation.md" +revision_date: '2022-11-07' +tags: +- Осуществлять +--- + +# Aggregate Package Installation Guide { #c19-agg-installation } + +## Overview { #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. + +The configuration packages for DHIS2 consists of a metadata file in [JSON](https://en.wikipedia.org/wiki/JSON) format which can be imported into a DHIS2 instance, as well as accompanying documentation. The package provides pre-defined, standard content according to WHO recommendations. This document is concerned with complete packages that include configurations of data collection (data sets, data elements, validation rules) as well as analysis and dashboards (chart, map and pivot table favourites). This is intended for use where there is no data collection configured in DHIS2, or if replacing/revising existing content to align with WHO recommendations. + +The configuration packages consists of 4 main components: + +* data sets with data elements; +* a set of indicators; +* analytical outputs (pivot table, data visualizer and GIS favourites); and +* a set of dashboards. + +These components are all linked, i.e. the indicators are based on the included data elements, the analytical outputs are based on the included indicators, and the dashboards are made up of the included analytical outputs. + +## Installation { #installation } + +Installation of the module consists of two steps: + +1. [Preparing](#preparing-the-metadata-file) a metadata file with DHIS2 metadata. +2. [Importing](#importing-a-metadata-file-into-dhis2) a metadata file into DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Performing](#examples-of-other-modifications) package-specific modifications. + +This section deals with the first two steps of preparing and importing the metadata file into DHIS2, whilst the configuration procedure is discussed in the next section. It is recommended to first read through both sections before starting the installation and configuration process in DHIS2. In addition to the general steps described here, some of the configuration packages have annexes to the installation guide, describing particular issues. These are listed in the appropriate section [here](https://dhis2.org/who-package-downloads). + +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. + +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 } + +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): + +* data elements (including categories) +* data sets +* indicators +* indicator types +* dashboards +* data visualizer, pivot table and GIS favourites + +The full list of objects included in the module (for which the administrator needs authorities to manage) can be found in the Metadata reference document for the particular configuration package. + +In cases where modifications to the .json metadata file of the configuration package are necessary [(see below)](https://who.dhis2.org/documentation/installation_guide_complete.html#preparing-the_metadata-file), a [text editor](https://en.wikipedia.org/wiki/Text_editor) is needed - these modifications should not be done with a word processor such as Microsoft Word. + +The configuration package can be installed in DHIS2 through the DHIS2 Health App, or manually through a .json file with DHIS2 metadata using the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. The procedure described in the rest of this section applies to the process of manually importing metadata. + +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 } + +**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. + +## Default data dimension { #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| +|--|--|--| +|Category|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Category option|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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 } + +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| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Percentage|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. + +**Note 2**: An alternative approach to re-using the existing indicator types is to import those included in the configuration package, and removing the existing ones that overlap. This would require all indicators that use these existing indicator types to be updated to the newly imported indicator types, before the indicator types can be deleted. + +## Importing a metadata file into DHIS2 { #importing-a-metadata-file-into-dhis2 } + +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 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 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 } + +**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 } + +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 } + +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. + +#### 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. +* 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. + +## Additional Configuration { #additional-configuration } + +Once all metadata has been successfully imported, the module should be useable with only a few minor additional adjustments. In addition, depending entirely on the DHIS2 instance the module has been imported into, some additional configuration and modification might be necessary or advantageous. This section will first go through the necessary configuration steps, then mention some of the other types of modifications or configuration that might be relevant. + +## Required configuration { #required-configuration } + +Before the configuration packages can be used for data collection, there are two steps that are required. + +* Assign the data set(s) to appropriate organisation units +* Share the data set(s) with appropriate user groups +* Add your user(s) to the appropriate user groups + +The data sets should be assigned to the organisation units (facilities) which are expected to report on that particular data set. + +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 } + +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: + +* Data elements/Data element groups +* Indicators/Indicator groups +* Data Sets +* Dashboards + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +We recommend the following access + +|Object|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| +|_Indicators/Indicator group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| +|_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 } + +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. + +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 data element categories exists these duplications can be hidden to end users through category option group sets, or certain metadata objects can be hidden for groups of users through sharing. + +It is recommended not to remove or replace the indicators included in configuration packages even though the same indicator already exists, so that the analytical outputs (which as based exclusively on indicators) can be kept. This will allow training material based on the configuration packages to be re-used. + +## Examples of other modifications { #examples-of-other-modifications } + +In addition to the required configuration, there are a number of other modifications and configuration that might be relevant, depending on the specific situation. It will not be possible to provide guidance and recommendations that cover all the different scenarios, but a brief discussion of some common problems are presented here. + +### Translations { #translations } + +Additional translations might have to be added, if other languages than those included are needed. + +### Adding additional variables { #adding-additional-variables } + +The configuration packages includes key recommended data elements and indicators. However, it might in some cases be necessary to add additional variables to address country-specific information needs. These could be added to the included data sets. + +### Updating layout of reporting forms { #updating-layout-of-reporting-forms } + +To facilitate the work of personnel doing data entry in DHIS2, it is sometimes desirable to add a custom data entry form that match the format of paper forms used at the primary level. + +## Maintenance { #maintenance } + +No particular maintenance is required for the configuration packages, since they are made up of standard DHIS2 metadata objects. However, before upgrading to new versions of DHIS2, it is important to test all functionality of the system in general on a staging/test server before upgrading any production instances of the system. + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md new file mode 100644 index 00000000..0f5c8c53 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/overview.md" +revision_date: '2023-03-07' +tags: +- Осуществлять +--- + +# COVID-19 Aggregate Surveillance { #covid-19-aggregate-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-agg-release-note) + +## Design { #design } + +- [Version 2.0.0](#c19-agg-design) + +## Installation { #installation } + +- [Installation Guide](#c19-agg-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 2.0.0](https://packages.dhis2.org/en/C19_AGG/2.0.0/DHIS2.39/C19_AGG_COMPLETE_2.0.0_DHIS2.39.xlsx) + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md new file mode 100644 index 00000000..f3240cb5 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md @@ -0,0 +1,26 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Осуществлять +--- + +# Release Note { #c19-agg-release-note } + +To see additional details of the metadata objects mentioned below, refer to the metadata reference documentation of the relevant version. + +## 2.0.0 { #200 } + +* The changes leading to this version were based on the revised [WHO Global surveillance of COVID-19 Weekly Aggregate Report ](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) +* The major were made on the age disaggregations with 5 year age bands used for <20 years and 60+ years spanning upto 80+years. +* Unknown age and Unknown sex were also introduced in the disaggregations to cater data that cannot be categorized with the options provided. +* Data elements for cases and deaths among health workers (Confirmed + Probable), tests with PCR assay, deaths amongst probable cases and health workers were introduced in this version. +* Data elements for logistics and cases by transmission classifications were removed. +* Considering these changes, all the core metadata objects; data elements, indicators, dashboard and its items, dataSets, indicator groups and data elements groups were newly created. +* This version now has only one dataSet designed for weekly reporting unlike in the previous version that had 2 dataSets reported weekly and daily basis. +* All the core metadata objects have been coded in support for international standard for aggregate data exchange (ADX). + +## 1.0.0 { #100 } + +Initial release of COVID-19 Aggregate Surveillance package + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md new file mode 100644 index 00000000..c126bf3f --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -0,0 +1,291 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-design.md" +revision_date: '2022-09-13' +tags: +- Осуществлять +--- + +# COVID-19 Case Surveillance & Contact Tracing Design { #c19-cs-design } + +Demo: [https://demos.dhis2.org/covid-19](https://demos.dhis2.org/covid-19) + +## Purpose { #purpose } + +The COVID-19 Surveillance System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +**This design has been updated to reflect new aggregate reporting requirements from the [WHO interim surveillance guidelines updated March 20, 2020][1]**. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| Type of Surveillance Package | Case Surveillance (Tracker) | Surveillance (Event) | Surveillance (Aggregate) | +|---|---|---|---| +| ***Description*** | Enrols a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables daily or weekly reporting of key aggregate data points | +| ***Pros*** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| ***Cons*** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) | + +**This document covers only the design of the surveillance tracker program package**; separate system design documents are available for DHIS2 event and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing case disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 surveillance package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions][2], updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +The DHIS2 case surveillance tracker metadata was based on the **[WHO COVID-19 case reporting template][3]** and the mapping of data dictionaries can be accessed at: [DHIS2 CBS tracker metadata WHO line-list data dictionary][4]. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles][5] and a common [naming convention][6]. + +The COVID-19 digital data package supports surveillance workflows and automated analysis for key components of routine and active surveillance. This package includes a Case Surveillance Tracker and Contact registration & follow-up tracker, which are installed together in the same metadata package. The tracker programs are optimized to be installed with other COVID-19 surveillance packages, including the Points of Entry Screening Tracker and aggregate daily surveillance dataset. + +1. **[Use Case 1: COVID-19 Case surveillance tracker][7]**: enrols & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. Metadata for the case surveillance tracker is aligned with the WHO [COVID-19 surveillance data dictionary][8] + + > n.b. The COVID-19 case tracker can be implemented either as a ‘standalone’ program for COVID-19 specific disease surveillance as described here; or, COVID-19 concepts can be integrated into an existing case surveillance tracker program if one already exists in-country. Please refer to installation and implementation guidance for more details. + +1. **[Use Case 2: Contact registration & follow-up][9]**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. + +Digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [Google Play store][10]. + +## Use Case 1: COVID-19 Case surveillance tracker { #use-case-1-covid-19-case-surveillance-tracker } + +The COVID-19 case surveillance tracker can be adapted and used by countries to supplement existing national disease surveillance programs. The basic case surveillance program is designed to: + +1. Enroll suspected\* COVID-19 cases (*generally appearing at a health facility, but may be enrolled at other places*) +2. Capture key information about the suspected case including demographics and exposures, such as symptoms, contact with a previously confirmed case & travel history +3. Generate lab requests +4. Record laboratory diagnosis +5. Record contacts of a confirmed\*\* or probable\*\*\* case for follow-up +6. Record case outcome +7. Facilitate case notification and national/regional/global case reporting +8. Generate dashboards and analytics tools for monitoring disease trends and planning response efforts + +The design of the case tracker program assumes that [WHO case definitions][1] are followed in the use case; its use can be adapted to local case definitions as needed. The WHO case definitions were updated on March 20, 2020 and noted below. + +> \* Suspected case: A) a patient with acute respiratory illness (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness of breath), AND with no other aetiology that fully explains the clinical presentation AND a history of travel to or residence in a country/area or territory reporting local transmission of COVID-19 disease during the 14 days prior to symptom onset; **OR**, B) A patient with any acute respiratory illness AND having been in contact with a confirmed or probable COVID-19 case (see definition of contact) in the last 14 days prior to onset of symptoms; **OR,** C) A patient with severe acute respiratory infection (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness breath) AND requiring hospitalization AND with no other aetiology that fully explains the clinical presentation. +> +>\*\* Probable case: A) a suspect case for whom testing for COVID-19 is inconclusive (inconclusive being the result of the test reported by the laboratory) **OR,** B) a suspect case for whom testing could not be performed for any reason. +> +>\*\*\* Confirmed case: A person with laboratory confirmation of COVID-19 infection, irrespective of clinical signs and symptoms. + +### Intended Users { #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 +* 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 + +### Workflow: COVID-19 Case Surveillance Tracker { #workflow-covid-19-case-surveillance-tracker } + +![Workflow of the DHIS2 COVID-19 Case Surveillance Tracker](resources/images/sdd-tracker-v3-case1-workflow.png) + +### Structure: COVID-19 Case Surveillance Tracker Program { #structure-covid-19-case-surveillance-tracker-program } + +![Structure of the COVID-19 Case Surveillance Tracker Program](resources/images/sdd-tracker-v3-case1-structure-v2.png) + +#### Program Description: COVID-19 Case Testing, Diagnosis & Outcome { #program-description-covid-19-case-testing-diagnosis-outcome } + +| Stage | Description | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is the case, which is represented by a Tracked Entity Type of ‘person.’ The *Enrollment date* is the date of registration of the case. The Related programs is *COVID-19 Contact registration & follow-up*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *Age*, *First Name*, *Surname*, *Sex*, *Case phone number*, *First Name (parent or care)*, *Surname (parent or carer)*, *Home Address*, *Workplace/school physical address*, *Country of Residence*, *Facility contact number*| +| **Stage 1: Clinical Examination and Exposures** | This stage records a suspected case’s clinical symptoms and exposures including: *Symptoms*, *Pregnancy and underlying conditions*, *Hospitalisation and Isolation*, *Exposures in 14 days prior to symptoms*, *Travel history*, *Contact with confirmed case*. After examination, you can record if the case has been hospitalised or isolated, and information surrounding this. | +| **Stage 2: Lab Request [repeatable]** | The lab request records the reason for testing and other information that a lab needs to process a sample and test it for COVID19. The information provided here can help lab personnel prioritize lab tests when resources are limited. The person entering this data could be the same person who registered the suspected case and recorded the patient’s clinical exam and exposures; or may be other personnel charged with making lab requests. | +| **Stage 3: Lab Results [repeatable]** | The Lab Results stage records the type and results from laboratory testing. It can be done directly at the lab or as secondary data entry. This stage is repeatable as samples for a given case may be tested multiple times (i.e. in the case of an inconclusive laboratory results, a new lab test can be conducted and results recorded). | +| **Stage 4: Health Outcome** | The health outcome records the final outcome of the case: (recovered, not recovered, dead or unknown) including date of discharge or death as applicable. | + +#### Enrollment Stage { #enrollment-stage } + +![Enrollment](resources/images/sdd-tracker-v3-case1-enrollment.png) + +#### Program Stage 1 - Clinical Examination & Diagnosis { #program-stage-1-clinical-examination-diagnosis } + +##### Section 1 - Clinical Signs and symptoms { #section-1-clinical-signs-and-symptoms } + +Selecting “yes” to the Data Element ‘Any signs or symptoms?’ reveals the rest of the options. + +![Section 1](resources/images/sdd-tracker-v3-case1-stage1-section1.png) + +##### Section 2 - Pregnancy Details { #section-2-pregnancy-details } + +This section is hidden unless gender is selected as ‘Female.’ + +![Section 2](resources/images/sdd-tracker-v3-case1-stage1-section2.png) + +##### Section 3 - Underlying Conditions/Comorbidity { #section-3-underlying-conditionscomorbidity } + +The details of this section are hidden unless “Any underlying conditions” is marked as “Yes”. + +![Section 3](resources/images/sdd-tracker-v3-case1-stage1-section3.png) + +##### Section 4 - Hospitalisation { #section-4-hospitalisation } + +The details of this section is hidden unless “Hospitalised” is marked as “Yes”. + +![Section 4](resources/images/sdd-tracker-v3-case1-stage1-section4.png) + +##### Section 5 - Exposure Risk { #section-5-exposure-risk } + +This section is used to record exposures + + 1. The fields ***country, city and facility*** are hidden by program rules if the case is not a health care worker; + 2. The fields for contact IDs are hidden by program rules if the case has not had contact with a confirmed case in 14 days. + +A suspected case’s exposure to a *previously confirmed* case is distinct from prospective contact tracing in Program Stage 5. + +![Section 5](resources/images/sdd-tracker-v3-case1-stage1-section5.png) + +##### Section 6 - Travel History { #section-6-travel-history } + +![Section 6](resources/images/sdd-tracker-v3-case1-stage1-section6.png) + +#### Program Stage 2: Lab Request { #program-stage-2-lab-request } + +![Stage 2](resources/images/sdd-tracker-v3-case1-stage2.png) + +#### Stage 3: Lab Results { #stage-3-lab-results } + +![Stage 3](resources/images/sdd-tracker-v3-case1-stage3.png) + +#### Stage 4: Health Outcomes { #stage-4-health-outcomes } + +![Stage 4](resources/images/sdd-tracker-v3-case1-stage4.png) + +### Program Rules: COVID19 Case Surveillance Tracker { #program-rules-covid19-case-surveillance-tracker } + +The following program rules have been configured. If a country has an existing case surveillance program and wishes to incorporate elements of the COVID-19 case tracker into their existing program, special attention must be paid to the configuration of program rules. + +| Program Rule Name | Program Rule Description | +|---|---| +| Assign Enrollment Date | This assigns the enrollment date if there is no onset date available to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators. | +| Assign Onset Date| This assigns the onset date to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators.| +| Calculate and assign patient age in years | Calculate and assign patient age in years based on DOB | +| Display patient age in years + days | Display patient age in years + days | +| Hide Date of Death | Hide the Date of Death unless Death is the health outcome | +| Hide Date of Discharge | Hide Date of Discharge if no outcome or if the outcome is death | +| Hide Measured Temperature field | Hide Measured Temperature field until Fever is selected | +| Hide confirmed case ID's if no contact with other confirmed cases| Hides any contact ID's if the case has not been in any contact with other confirmed cases | +| Hide health care worker details if not a health worker | Hide health care worker details if not a health worker | +| Hide health outcome explanation if health outcome is not other | Hide health outcome explanation if health outcome is not other | +| Hide hospitalisation details if hospitalisation is no or unknown | Hide hospitalisation details if hospitalisation is no or unknown | +| Hide isolation date if case is not in isolation | Hide isolation date if case is not in isolation | +| Hide pregnancy details for a female if not pregnant | Hide pregnancy details for a female if not pregnant | +| Hide pregnancy details section if sex is male | Hide pregnancy details section if sex is male | +| Hide reason for testing explanation if an option is selected | Hide reason for testing explanation if an option is selected | +| Hide travel history details if no travel 14 days prior to symptom onset | Hide travel history details if no travel 14 days prior to symptom onset | +| Hide underlying conditions if case does not have any | Hide underlying conditions if case does not have any | +| Show warning if the event date is after the enrollment date | Show warning on completion of an event if the event date is before the enrollment date | + +You can read more about program rules here: [https://docs.dhis2.org/master/en/user/html/configure\_program\_rule.html][11] + +### Program Indicators { #program-indicators } + +From the data captured in the COVID-19 case surveillance program, we can calculate at least the following indicators including those recommended by the WHO for daily and weekly aggregate reporting and present them in a dashboard: + +| Indicator name | Description | +|---|---| +| COVID-19 - Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU) | *Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU)* | +| COVID-19 Contacts | *Counts the number of relationships (‘has been in contact with’) created that are linked to the case TEI* | +| COVID-19 - Deaths (all suspected cases) | *COVID-19 related deaths (deaths recorded among all suspected cases)* | +| COVID-19 - Deaths (confirmed cases) | *COVID-19 related deaths (deaths recorded among confirmed cases)* | +| COVID-19 - Deaths (probable cases) | *COVID-19 related deaths (deaths recorded among all probable cases)* | +| COVID-19 - Confirmed Hospitalised Cases | *Number of confirmed cases that were admitted into hospital* | +| COVID-19 - Imported Cases | *Cases where likely source of infection is recorded as another country or imported from another country.* | +| COVID-19 - Laboratory confirmed cases | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by report date* | +| COVID-19 - Laboratory confirmed cases - by onset of symptoms | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by date of onset of symptoms* | +| COVID-19 - Laboratory tested cases | *Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)* | +| COVID-19 - Local transmission cases | *Number of suspected cases where transmission is local (no travel in last 14 days* | +| COVID-19 - Probable cases | *Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date* | +| COVID-19 - Probable cases - by onset of symptoms | *Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms* | +| COVID-19 - Recovered confirmed cases | *Number of laboratory confirmed cases with outcome recovered*| +| COVID-19 - Suspected cases | *Total number of cases suspected with COVID-19, by report date* | +| COVID-19 - Suspected cases - by onset of symptoms | *Total number of cases suspected with COVID-19, by date of onset of symptoms* | +| COVID-19 - Suspected cases without a positive test result | *Total number of suspected cases without a positive lab result* | +| COVID-19 Total number of laboratory tests conducted | *Total number of lab tests conducted (count of tests, not cases)* | +| COVID-19 Total number of positive tests | *Total number of lab tests returned with positive results (count of tests, not cases* | +| COVID-19 Deaths by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Confirmed cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Suspected cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | + +## Use Case 2: COVID-19 Contact registration & follow-up { #use-case-2-covid-19-contact-registration-follow-up } + +This program can be used in addition to the case surveillance tracker to facilitate the registration and follow-up of contacts of a confirmed case. In this scenario, it is assumed that if any contacts of a confirmed case meet criteria for suspected case and are referred for testing, the case will be enrolled into the COVID-19 Case Surveillance tracker program. + +The Contact registration & follow-up program registers each contact of a case (as described in COVID-19 Case Surveillance Use Case) as a new Tracked Entity Instance (person) and links them to the case in the COVID-19 Case Surveillance Program via a ‘relationship.’ It has a simple repeatable follow-up stage where symptoms and any follow-up undertaken can be registered. + +### Workflow: Contact registration & follow-up { #workflow-contact-registration-follow-up } + +![Worflow of the Contact registration & follow-up](resources/images/sdd-tracker-v3-case2-workflow.png) + +### Program Description: Contact registration & follow-up { #program-description-contact-registration-follow-up } + +| Stage | Description | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is represented by a Tracked Entity Type of ‘person.’ The Related program is *COVID-19 Case based surveillance*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *First Name*, *Surname*, *Date of birth*, *Age*, *Sex*, *Phone number (local)*, *Home Address*, *Country of Residence* | +| **Stage 1: Follow-Up [non-repeatable]** | This stage is meant to record information related to contact tracing follow up, given that a contact has already been identified. It is divided into two sections: *1. Relation with case*, *2. Exposure Assessment* | +| **Stage 2: Symptoms[repeatable]** | This stage is intended to record symptoms of the case. Follow-up to check on the symptoms of a contact can be repeated until the follow-up period is complete (for example, after 14 days or according to national guidelines). When follow-up period is complete, the enrollment can be ‘completed.’ *1. Symptoms*| + +Contacts are added to the index case using the relationships menu in the case surveillance program: + +![Profile](resources/images/sdd-tracker-v3-case2-profile.png) + +Once you select “Add” from the relationships box, you are able to select the relationship and program and either select an existing person or enroll a new contact using the enrollment stage that appears. This will enroll the contact into the contact registration and follow-up +program. + +![Add a relationship](resources/images/sdd-tracker-v3-case2-add-relationship.png) + +Contacts that are added will then be listed on the case’s tracker dashboard in the relationship +widget + +![Relationships widget](resources/images/sdd-tracker-v3-case2-relationships-widget.png) + +You may also enroll them separately into the program. Once enrolled, you will be able to find them for the follow-up as required. + +#### Enrollment { #enrollment } + +![iEnrollment in the use case 2](resources/images/sdd-tracker-v3-case2-enrollment-case2.png) + +#### Program Stage 1 : Follow - Up { #program-stage-1-follow-up } + +![Case 2 Stage 1](resources/images/sdd-tracker-v3-case2-stage1.png) + +#### Program Stage 2 : Symptoms { #program-stage-2-symptoms } + +![Case 2 Stage 2](resources/images/sdd-tracker-v3-case2-stage2.png) + +### Program Indicators: Contact Registration { #program-indicators-contact-registration } + +| Program Indicator Name | Description | +|---|---| +| COVID-19 travelers screened | Total number of travelers screened and enrolled in screening program from POE | +| COVID-19 travelers cleared at POE | Number of travelers cleared after POE screening (no follow-up required) | +| COVID-19 travelers with symptoms at POE | Number of travelers presenting with symptoms during POE screening | +| COVID-19 travelers cleared after 14 days monitoring | Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period) | +| COVID-19 travelers referred to health facility | Number of travelers that were referred to a health facility at any time during 14 day followup | +| COVID-19 travelers enrolled for 14 day follow-up | Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening | +| COVID-19 currently under follow-up | Number of travelers that have not been cleared or referred to a health facility | +| COVID-19 travelers developed symptoms during follow-up | Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening) | + +## References { #references } + +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form [https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + +[1]: https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf +[2]: https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions +[3]: https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx +[4]: https://drive.google.com/open?id=1vigXHkP7L2hJ2lrZpdf9u4csQtppMH16 +[5]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html +[6]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html +[7]: #use-case-1-covid-19-case-surveillance-tracker +[8]: https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2 +[9]: #use-case-2-covid-19-Contact-registration-follow-up +[10]: https://play.google.com/store/apps/details?id=com.dhis2&hl=en +[11]: https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md new file mode 100644 index 00000000..03d82723 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-installation.md" +revision_date: '2022-09-13' +tags: +- Осуществлять +--- + +# COVID-19 Surveillance - Installation Guide { #c19-cs-installation } + +## Overview { #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: + +1. COVID-19 Case-based Surveillance Tracker program & COVID-19 Contact Registration & Follow-Up program +2. Points of Entry Screening Tracker program + +You will have to follow the instructions in full for each separate package that you install. + +## Installation { #installation } + +Installation of the module consists of several steps: + +1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. +2. [Importing](#importing-metadata) the metadata file into DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Adapting](#adapting-the-tracker-program) the program after being imported + +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 } + +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 } + +**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. + +### Default data dimension { #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| +|--|--|--| +|Category|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Category option|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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 } + +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| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Percentage|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| +|--|--|--| +|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| + +## Importing metadata { #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 } + +***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 } + +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 } + +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. + +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. + +#### 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: + +* 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. + +## 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. + +### Sharing { #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 +* Program +* Program stages +* Dashboards + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +By default the following is assigned to these user groups + +|Object|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| +|_*Program*_|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| +|_*Dashboards*_|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: + +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. + +### Organisation Units { #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 } + +**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. + +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). + +## 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. +* 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. + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md new file mode 100644 index 00000000..b0e3a1d3 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md @@ -0,0 +1,29 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/overview.md" +revision_date: '2022-11-22' +tags: +- Осуществлять +--- + +# COVID-19 Case Surveillance { #covid-19-case-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-cs-release-note) + +## Design { #design } + +- [Version 1.0.2](#c19-cs-design) + +## Installation { #installation } + +- [Installation Guide](#c19-cs-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 1.0.2](https://packages.dhis2.org/en/C19_CS/1.0.2/C19_CS_COMPLETE_1.0.2_DHIS2.37.xlsx) + +## Training Material { #training-material } + +- [COVID-19 Training Material](https://dhis2.org/covid-training-material) + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..fe1e1949 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Осуществлять +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Overview { #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/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md new file mode 100644 index 00000000..3dc10ddc --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -0,0 +1,136 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/c19_poe-design.md" +revision_date: '2022-07-05' +tags: +- Осуществлять +--- + +# COVID-19 Points of Entry Tracker Design { #c19-poe-design } + +Demo: [https://covid19.dhis2.org/](https://covid19.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Points of Entry (POE) Screening System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +The Points of Entry Screening Tracker is inspired by the pioneering design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health. In January 2020, the Sri Lanka MOH implemented screening measures at ports of entry like airports to identify travelers who may have been exposed to nCoV-19. DHIS2 tracker was to enroll travelers entering Sri Lanka who had visited countries impacted by COVID-19. DHIS2 tracker enabled follow-up with travelers at field level for 14 days to ensure no symptoms developed. If symptoms developed, travelers would be referred to a health facility for clinical examination and testing. The POE tracker can be used in combination with other COVID-19 digital data packages that include case surveillance and contact tracing. + +The World Health Organisation (WHO) has published [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). Points of entry (POE) include international airports, seaports and land crossings. POE measures include 1) detection of ill travellers; 2) interview of ill travellers for COVID-19; 3) reporting of alerts of ill travellers with suspected COVID-19 infection and 4) isolation, initial case management and referral of ill travellers with suspected COVID-19 infection. These guidelines should be consulted, in addition to national protocols for points of entry. + +## System Design Summary { #system-design-summary } + +### Use Case { #use-case } + +The POE tracker program use case was designed to support the registration of travelers 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. For this use case, it is assumed that a traveler may be 1) screened and cleared immediately with no follow-up needed; 2) screened and followed up for 14 days [with or without isolation measures] to ensure no symptoms develop; or 3) screened and referred for testing and/or initial case management. The current design proposes that a traveler meeting the country’s definition of a suspected case would be enrolled into the complementary DHIS2 COVID-19 Case-Based Surveillance (CBS) Tracker. For example, a traveler enrolled in this program who later meets the definition of a suspected case during follow-up (i.e. an asymptomatic traveler from a country with known transmission is registered at the POE and later develops symptoms) is enrolled as a suspected case into the COVID-19 CBS program to capture all clinical details, exposures and follow the case through laboratory diagnosis and case outcome. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +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). + +### Intended users { #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. +* National and local health authorities: monitor and analyse data through dashboards and analytics tools to conduct risk assessments and plan response measures. + +### Workflow { #workflow } + +The Points of Entry program workflow is based on the following scenario + +![Scenario](resources/images/POE_image01.png "Scenario") + +In this design, it is assumed a traveler would complete their enrollment in the POE under the following scenarios: + +1. Traveler is marked as ‘cleared’ during initial screening or after 14 day follow-up +2. Traveler is referred to health facility at any point during follow-up + +**A traveler that is referred to a health facility is expected to be enrolled in the COVID-19 Case-based Surveillance Tracker as a suspected case** (according to national guidelines). Details about a suspected case including clinical exam, exposures, laboratory results and case outcome would be recorded in the CBS program. + +### Structure: Points of Entry Screening Tracker Program { #structure-points-of-entry-screening-tracker-program } + +![Structure](resources/images/POE_image02.png "Structure") + +#### Consideration for Organisation Units & Geography { #consideration-for-organisation-units-geography } + +This program design assumes that Points of Entry such as airports, seaports or land crossings will be created as organisation units included in the OU hierarchy. The program would be assigned to the POE org units. Primary analysis is based on the enrolling Org Unit (the port of entry). + +Additional geographical components are also captured as other dimensions: + +1. TEI coordinates: It is possible to capture TEI coordinates when registering the traveler as TEI. These can be displayed in the maps app. Local protocols may choose what coordinates to enter, for example the TEI’s local residence where he/she may be self-quarantined for 14 days. +2. Event coordinates: for screening and follow-up stages, coordinates can be captured on the event and displayed in a map. For example, the user may capture a traveler’s location each time they are followed up (i.e. in the case of tourists or others not in home quarantine). + +#### Program Description { #program-description } + +|Stage|Description| +|--|--| +|**Registration**|The Tracked Entity is the traveler, which is represented by the Tracked Entity Type of ‘person.’ The TEI is configured to collect a geographic ‘point’ during registration. These can be analyzed in a map.| +|**Enrollment details**|Enrollment date
The first Program Stage is configured to appear on the Registration page so that a user does not need to click through to add the first event.| +|**Attributes**|Attributes include basic personal information and unique case identifiers
- Passport number
- Local Case ID
- Age
- First Name
- Surname
- Country of residence
- Sex
- Date of birth
- Local address
- Home address
- Telephone (local)
- Telephone (foreign)
- Emergency contact
- Emergency contact phone
- Email| +|**Stage 1**
**Screening at POE**
**(non-repeatable)**|This stage records:
- Traveler details (countries visited, flight number, date of departure, etc)
- Examination: recorded temperature
- Symptoms: this list includes symptoms typically checked for both COVID-19 symptoms and symptoms of other potential notifiable diseases
- Case clearance

If the traveler is marked as ‘cleared’, no further follow up is required; the enrollment may be closed. If the traveler requires follow-up, an event can be scheduled for follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 2:**
**Follow-up (within 14 days)**
**(repeatable)**|Data is entered at this stage if any interim follow-up is performed before the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment may be closed if no further monitoring & follow-up is planned in this program.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 3:**
**Follow-up (after 14 days)**
**(non-repeatable)**|Data is entered at this stage at the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)
- Case clearance

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment should be closed at the completion of 14 day follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization. + +![Enrollment](resources/images/POE_image03.png "Enrollment") + +![Program Stage 1 - Screening at POE](resources/images/POE_image04.png "Program Stage 1 - Screening at POE") + +![Program Stage 1 - Screening at POE](resources/images/POE_image05.png "Program Stage 1 - Screening at POE") + +![Program Stage 2: Follow-up (within 14 days)](resources/images/POE_image06.png "Program Stage 2: Follow-up (within 14 days)") + +![Program Stage 3: Follow up (after 14 days)](resources/images/POE_image07.png "Program Stage 3: Follow up (after 14 days)") + +#### How to refer the TEI to another Organisation Unit { #how-to-refer-the-tei-to-another-organisation-unit } + +Primary analysis is completed on the enrolling organisation unit (the port of entry). Referral facility is captured as a Data Element (type: Organisation Unit) in order to display travelers by referral to health facility in the analytics apps (i.e. Event Report). In some use cases, it may be desirable to refer the TEI (the traveler) to another Org Unit for follow-up. + +A TEI can be ‘referred’ to another org unit such as a health facility for one event or permanently. In this case, health facility user must be able to search TEIs enrolled in the relevant Points of Entry org units. For example, if after screening a traveler at the POE, the traveler may be “referred” to a district health office near the traveler’s local address for follow-up by district health staff. After completing the data entry for Stage 1 (screening), the user would refer the TEI to a District Health Center. Read more about referrals in tracker in [DHIS2 User Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/tracking-individual-level-data/tracker-capture.html). + +![alt_text](resources/images/POE_image08.png "image_tooltip") + +### Program Relationships { #program-relationships } + +This program has the relationshipType ‘Has been in contact with’. Users can create a relationship between TEIs enrolled in the POE program and TEIs in other COVID-19 tracker programs (Case-based Surveillance, Contact Registration & Follow-up). The relationship can be added at any point in the program stages during data entry. + +### Program Rules { #program-rules } + +The following program rules have been configured. + +|Program Rule Name|Program Rule Description| +|--|--| +|Calculate and assign patient age in years|Calculate and assign patient age in years| +|Hide countries if not visited|Hide countries if not visited| +|Hide Follow-Up Stages|Hide Follow-Up Stages if the case is cleared at the port of entry| +|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)| +|Hide symptoms if no symptoms present (Follow Up within 14 days)|Hide symptoms if no symptoms present (Follow Up within 14 days)| +|Hide symptoms if no symptoms present (PoE)|Hide symptoms if no symptoms present (PoE)| + +You can read more about program rules here: +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +||| +|--|--| +|COVID-19 travelers screened|Total number of travelers screened and enrolled in screening program from POE| +|COVID-19 travelers cleared at POE|Number of travelers cleared after POE screening (no follow-up required)| +|COVID-19 travelers with symptoms at POE|Number of travelers presenting with symptoms during POE screening| +|COVID-19 travelers cleared after 14 days monitoring|Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period)| +|COVID-19 travelers referred to health facility|Number of travelers that were referred to a health facility at any time during 14 day followup| +|COVID-19 travelers enrolled for 14 day follow-up|Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| +|COVID-19 currently under follow-up|Number of travelers that have not been cleared or referred to a health facility| +|COVID-19 travelers developed symptoms during follow-up|Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)| +|COVID-19 % travelers developed symptoms during 14-day follow-up|Numerator: Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)
Denominator: Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| + +Users can also generate an Event Report to see: + +1. Travelers by nationality and/or originating country +2. Referrals to health facility + +## References { #references } + +* DHIS2 COVID-19 [Tracker Package Installation Guide](covid-19-tracker-installation.html) +* World Health Organisation (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) (interim guidance, published 19 March 2020) + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md new file mode 100644 index 00000000..fd7a0c49 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Осуществлять +--- + +# COVID-19 Points of Entry { #covid-19-points-of-entry } + +## Design { #design } + +[Version 1.0.2](#c19-poe-design) + +## Installation { #installation } + +[Installation Guide](#c19-poe-installation) + +## Release Note { #release-note } + +[Release Note](#c19-poe-release-note) + +## Metadata Reference { #metadata-reference } + +[Version 1.0.2](https://packages.dhis2.org/en/C19_POE/1.0.2/C19_POE_COMPLETE_1.0.2_DHIS2.37.xlsx) + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md new file mode 100644 index 00000000..aead4bda --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -0,0 +1,164 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/c19_evt-design.md" +revision_date: '2022-11-08' +tags: +- Осуществлять +--- + +# COVID-19 Surveillance Line-list Design { #c19-evt-design } + +Demo: [https://covid.dhis2.org](https://covid.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Surveillance Event Program System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +|Type of Surveillance Package|Case-based Surveillance (Tracker)|Surveillance (Event)|Surveillance (Aggregate)| +|--|--|--|--| +|_Description_|Enrolls a case and tracks over time through laboratory confirmation & case outcome|Captures critical case details in line-listing format|Enables daily or weekly reporting of key aggregate data points| +|_Pros_|Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case|More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity|Low complexity, easy to implement, most manageable when cases numbers are high| +|_Cons_|Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation|Does not support case-follow up or other decentralized workflows|Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) + +**This document covers only the design of the surveillance event program package**; separate system design documents are available for DHIS2 Tracker and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +This package is designed as a DHIS2 [Event Program](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#about_event_program). **The Event Program is not designed to capture all data variables contained in the [WHO case reporting template](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx)**. To capture a complete set of WHO case reporting variables, please refer to the DHIS2 COVID-19 Case-based Surveillance Tracker. Rather, the event program is a simplified program that captures a subset of minimum critical data points to facilitate high data quality when the number of caseloads or burden of reporting exceeds capacity for successfully completing the full line-list for suspected COVID-19 cases. For implementers who wish to capture the complete WHO line-listing, please refer to the COVID-19 Case-based Surveillance Tracker Package. + +The COVID-19 Surveillance Event Program data package includes: + +1. Event program and data elements case reporting +2. Core indicators +3. Dashboard + +### Use Case: Simplified line-listing of COVID-19 cases { #use-case-simplified-line-listing-of-covid-19-cases } + +As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The event package is designed to capture the most critical data points in a line-list and analytical capacities for surveillance and response. The event package is designed as a standalone program. However, countries may use the event package in combination with other packages (i.e. event reports and daily aggregate reporting); or, they may shift from tracker to event to aggregate as caseloads and reporting burden increases. **_Countries should plan carefully how they intend to implement these packages in combination, including reporting flows, transitioning from one data model to another, and how to maintain historical data for analysis if transitioning between data models. _** + +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. + +#### Intended users { #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 + +#### Workflow { #workflow } + +Unlike the tracker program, there are limitations to decentralization of the data reporting workflow in an Event program. The most significant limitation is that the Case Outcome (recovery or death) is often not known until days or weeks after the case is reported. The current program design allows for the following workflow options: + +1. Event is created when a suspected case is reported. All known data is entered, but the event is not completed. A user can select an ‘Active Event’ from a working list based on User filters and criteria. When missing data becomes available (i.e. the case outcome), the user can enter the remaining data fields and complete the event. Cases can be identified in the event list by the Case ID data element. See the image below as an example which can be accessed within the Capture App: +![Capture App](resources/images/EVENT_image1.png "Capture App") + +2. Event is created. All case related data is entered retrospectively, including the Outcome. Event is completed. _The limitation is this approach is timeliness of the data reporting, as new suspected cases might not be captured until their outcome which is often too late for decision making._ + +### Program Structure { #program-structure } + +The program is called ‘COVID-19 Cases (events)’ + +|Section|Description| +|--|--| +|Date of report|Event Date
_Countries may re-name the event date to apply to their protocols._| +|Section 1
**Basic Information**|Records basic demographic data.
_Countries may add data elements as desired._
- **Patient ID**
Can be used to filter events in working lists, eg. Active events
- **Sex**
- **Age**| +|Section 2
Case Details|Records information about the case including symptoms, severity, testing, etc.
- **Symptoms**
Options: Yes / No
Specifies whether a case has any symptoms at time of notification

- **Date of symptoms onset**
Only appears if symptoms are present;
Date of symptoms onset, if available, will replace “Date of Report” in data analytics and reporting.

- **Case Severity (at time of notification)**
Options: Mild / Moderate / Severe / Critical
- **Laboratory tested?**
Options: Yes / No/ Unknown
Specifies whether a case has been laboratory tested for COVID-19

- **Test Result**
Only appears if the case was laboratory tested
Options: Inconclusive / Positive / Negative / Unknown
The program is designed to capture only the final test result. Results for each individual test (if available) and the total number of tests performed are not captured.
- **Case Classification**
Options: Suspected case / Probable case / Laboratory confirmed case
Automatically assigned values
The values are assigned by Program rules in accordance with WHO case definitions
This feature can be useful in filtering active cases in the working lists.| +|Section 3
**Exposures**|- **Has the case traveled in the 14 days prior to symptoms onset?**
Options: Yes / No / Unknown
Specifies travel history of the case.

- **Likely Infection Source**
Options: Imported case* / Local Transmission / Exposure unknown
* Imported case option appears only if the case traveled in the 14 days prior to symptoms onset

- **Specify local source**
Only appears if Likely Infection Source is Local Transmission
Options: Community (workplace, public transport, etc.) / Household / Healthcare Facility / Close Contact with Other Infected Individual / Exposure Unknown

- **Case Type**
Options: New index case / Linked to existing cluster / Unknown
Specifies whether the case is connected to an existing cluster or is a new index case| +|Section 4
**Treatment**|- **Hospitalised**
Options: Yes / No

- **Did the case receive care in an intensive care unit (ICU)?**
Only appears if the case is hospitalised
Options: Yes / No| +|Section 5
**Contacts**|- **Total number of contacts followed for this case**
Records number of contacts| +|Section 6
**Outcome**|- **Health outcome**
Options: Recovered / Death| +|Section 7
**Assigned Date of onset of symptoms**|- **Calculated onset date (for Indicators)**
This section is used only to calculate indicators based on report date vs. date of onset of symptoms]
This automatically assigned date is used in program indicators. Initially, it is the report date. If the date of onset of symptoms is available, the date is replaced by the date of onset of symptoms.| +|**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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Currently, only users assigned to the COVID19 data capture group will have access to capture data in the program. Please refer to the installation guidance for more instructions. + +### Program Rules { #program-rules } + +The following program rules have been configured for the program: + +|Program Rule Name|Program Rule Description| +|--|--| +|Assign Empty Value to Class Classification|Automation: Assign Empty Value to Class Classification| +|Assign Event Date|Automation: Assign Event date if to onset date if no Onset date is available| +|Assign 'Laboratory Confirmed Case' to Case Classification|Automation: Assign 'Laboratory Confirmed Case' to Case Classification| +|Assign Onset Date|Automation: Assign Symptoms Onset Date if available| +|Assign 'Probable Case' to Case Classification|Automation: Assign 'Probable Case' to Case Classification| +|Assign 'Suspected Case' to Case Classification|Automation: Assign Suspected Case' to Case Classification| +|Hide Case Classification Field|Hide Case Classification Field until Lab Test question is answered| +|Hide ICU field|Hide ICU field unless Hospitalised| +|Hide 'Imported Case'|Hide 'Imported Case' if not traveled| +|Hide Onset of Symptoms Date|Hide Onset of Symptoms Date if no symptoms| +|Hide Outcome Options|Hide irrelevant Outcome Options| +|Hide 'Specify Local Infection Source'|Hide 'Specify Local Infection Source' unless Local Transmission is selected| +|Hide Test Result Field|Hide Test Result Field until Lab Test question is answered with yes| +|Hide Test Result Options|Hide Irrelevant Test Result Options| +|Hide Unknown Options|Hide Irrelevant Unknown Options| + +You can read more about program rules here: + +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +From the data captured in the COVID-19 line-listing program, we can calculate the following indicators, including those recommended by the WHO for daily and weekly reporting, present them in a dashboard. All COVID-19 program indicators based on the event program are assigned to the Program Indicator Group ‘COVID-19 Events.’ + +||| +|--|--| +|COVID-19 - Cases admitted in intensive care unit (ICU)|COVID-19 Cases admitted in intensive care unit (ICU)| +|COVID-19 - Cases exposed through healthcare facility|Cases where infection is suspected to have occurred in a health care setting| +|COVID-19 - Cases infected by community transmission|Cases where infection is suspected to have occurred through community spread| +|COVID-19 - Cases infected by household transmission|Cases where infection is suspected to have occurred within the household| +|COVID-19 - Cases infected by local transmission|Cases where infection is suspected to have occurred locally, not in another country| +|COVID-19 - Cases infected through other contact with other infected individual|Cases where infection is suspected to have occurred through other close contact with an infected individual (excluding those listed: household, known cluster, HCF)| +|COVID-19 - Cases linked to known cluster|Cases where infection is suspected to have occurred by linkage to a known cluster of cases| +|COVID-19 - Cases with unknown exposure|Cases where source of infection or exposure is unknown| +|COVID-19 - Deaths|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 - Confirmed Hospitalised Cases|Number of confirmed cases that were admitted into hospital| +|COVID-19 - Imported Cases|Cases where likely source of infection is recorded as another country or imported from another country.| +|COVID-19 - Laboratory confirmed cases|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by report date| +|COVID-19 - Laboratory confirmed cases - by onset of symptoms|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by date of onset of symptoms| +|COVID-19 - Laboratory tested cases|Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)| +|COVID-19 - Probable cases|Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date| +|COVID-19 - Probable cases - by onset of symptoms|Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms| +|COVID-19 - Recovered cases|Number of cases that are recovered (By date of onset of symptoms)| +|COVID-19 - Suspected cases|Total number of cases suspected with COVID-19, by report date| +|COVID-19 - Suspected cases - by onset of symptoms|Total number of cases suspected with COVID-19, by date of onset of symptoms| +|COVID-19 - Suspected cases not tested|Total number of suspected cases without a lab result| +|COVID-19 Event - case fatality rate|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 Deaths by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Confirmed cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Suspected cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| + +## References { #references } + +* [COVID-19 Surveillance, Response & Vaccine Delivery Toolkit](https://dhis2.org/covid-19) +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form +[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md new file mode 100644 index 00000000..0776cbd4 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md @@ -0,0 +1,13 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Осуществлять +--- + +# COVID-19 Surveillance Events { #covid-19-surveillance-events } + +## Design { #design } + +[Version 0.3.2](#c19-evt-design) + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md new file mode 100644 index 00000000..3ceb0d72 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md @@ -0,0 +1,22 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_surveillance-digital_data_package-2022.md" +revision_date: '2023-09-01' +tags: +- Осуществлять +--- + +# COVID-19 Surveillance { #covid-19-surveillance } + +DHIS2 released a digital metadata package to accelerate case detection, situation reporting, active surveillance and response for COVID-19. The design is inspired by the Ministry of Health Sri Lanka’s pioneering use of DHIS2 tracker for COVID-19 case detection and draws on years of collaboration with the World Health Organisation (WHO) to develop information system standards for case-based disease surveillance. The COVID-19 digital data package includes standard metadata aligned with the WHO’s [technical guidance on COVID-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and implementation guidance to enable rapid deployment in countries. + +The design of these modules can be adapted, modified and reused for new and emerging infectious disease threats to strengthen health emergency preparedness and response systems in countries. + +## COVID-19 Surveillance Modules { #covid-19-surveillance-modules } + +DHIS2 supports surveillance workflows and automated analysis for key components of routine and active surveillance: + +* **COVID-19 Case Surveillance tracker**: enrolls & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. +* **Contact Registration & Follow-up tracker**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. +* **Ports of Entry Screening & Follow-up tracker**: enrols travellers who have visited high-risk locations at Ports of Entry for 14-day monitoring and follow-up. +* **COVID-19 Aggregate Situation Reports**: an aggregate reporting dataset that captures minimum necessary data points for daily or weekly reporting and includes key information for generating situation reports. + diff --git a/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..fe1e1949 --- /dev/null +++ b/projects/docs-full-site/ru/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Осуществлять +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Overview { #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/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md index 09f0daeb..ec258559 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-235__ANDROID-APP-VERSION-230__release-notes-md @@ -3,8 +3,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/ revision_date: '2020-11-03' tags: - Android app version 2.3.0 -- DHIS core version 2.35 - Осуществлять +- DHIS core version 2.35 --- # DHIS2 Android App version 2.3 Release Note { #dhis2-android-app-version-23-release-note } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md index fb2da766..b0cbede5 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-236__ANDROID-APP-VERSION-240__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.4/ReleaseNote-2.4.0.md" revision_date: '2021-04-27' tags: -- DHIS core version 2.36 - Осуществлять +- DHIS core version 2.36 - Android app version 2.4.0 --- diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md index e61761ec..bd105891 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-237__ANDROID-APP-VERSION-250__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.5/ReleaseNote-2.5.0.md" revision_date: '2021-11-24' tags: -- Android app version 2.5.0 - DHIS core version 2.37 - Осуществлять +- Android app version 2.5.0 --- # DHIS2 Android App version 2.5 Release Notes { #dhis2-android-app-version-25-release-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md index 99202e61..909fe11d 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-238__ANDROID-APP-VERSION-260__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.6/ReleaseNote-2.6.0.md" revision_date: '2022-04-18' tags: -- DHIS core version 2.38 - Осуществлять +- DHIS core version 2.38 - Android app version 2.6.0 --- diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md index 031c2b3d..3ceb5eb0 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-239__ANDROID-APP-VERSION-270__release-notes-md @@ -3,8 +3,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/ revision_date: '2023-05-11' tags: - Android app version 2.7.0 -- DHIS core version 2.39 - Осуществлять +- DHIS core version 2.39 --- # DHIS2 Android App version 2.7 Release Notes { #dhis2-android-app-version-27-release-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md index 17730beb..e7d86e8b 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-280__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/android-releases/2.8/ReleaseNote-2.8.0.md" revision_date: '2023-05-08' tags: -- DHIS core version 2.40 - Android app version 2.8.0 - Осуществлять +- DHIS core version 2.40 --- # DHIS2 Android App version 2.8 Release Notes { #dhis2-android-app-version-28-release-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md index 33e3267c..aca0d1a2 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__ANDROID-APP-RELEASES__DHIS-CORE-VERSION-240__ANDROID-APP-VERSION-290__release-notes-md @@ -2,9 +2,9 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/2.9/android-releases/2.9/ReleaseNote-2.9.0.md" revision_date: '2023-11-20' tags: -- DHIS core version 2.40 - Осуществлять - Android app version 2.9.0 +- DHIS core version 2.40 --- # DHIS2 Android App version 2.9 Release Notes { #dhis2-android-app-version-29-release-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md index b54bbd9f..2a402e01 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/ReleaseNote-2.35.0.md" revision_date: '2020-10-22' tags: -- DHIS core version 2.35 - Осуществлять +- DHIS core version 2.35 --- # DHIS version 2.35 Release Note { #dhis-version-235-release-note } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md index bb68edbc..34994bc5 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-235__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.35/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.35 - Осуществлять +- DHIS core version 2.35 --- # 2.35 Upgrade Notes { #235-upgrade-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md index 82fe9dcd..6ad54829 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/ReleaseNote-2.36.md" revision_date: '2021-10-27' tags: -- DHIS core version 2.36 - Осуществлять +- DHIS core version 2.36 --- # DHIS version 2.36 Release Note { #dhis-version-236-release-note } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md index 9b9304c1..27ffd7a2 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-236__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.36/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.36 - Осуществлять +- DHIS core version 2.36 --- # 2.36 Upgrade Notes { #236-upgrade-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md index 4160e88e..028a4af8 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/ReleaseNote-2.38.md" revision_date: '2022-10-12' tags: -- DHIS core version 2.38 - Осуществлять +- DHIS core version 2.38 --- # DHIS version 2.38 Release Note { #dhis-version-238-release-note } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md index 2796694a..029ec72f 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-238__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.38/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.38 - Осуществлять +- DHIS core version 2.38 --- # 2.38 Upgrade Notes { #238-upgrade-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md index 348439c0..ac674109 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/ReleaseNote-2.39.md" revision_date: '2023-01-26' tags: -- DHIS core version 2.39 - Осуществлять +- DHIS core version 2.39 --- # DHIS version 2.39 Release Note { #dhis-version-239-release-note } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md index d2076888..c75ac4c1 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-239__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.39/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.39 - Осуществлять +- DHIS core version 2.39 --- # 2.39 Upgrade Notes { #239-upgrade-notes } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md index 725c531c..fb4e5076 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__release-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/ReleaseNote-2.40.md" revision_date: '2023-05-12' tags: -- DHIS core version 2.40 - Осуществлять +- DHIS core version 2.40 --- # DHIS2 version 40 Release Note { #dhis2-version-40-release-note } diff --git a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md index 978dcacb..6dfa145d 100644 --- a/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md +++ b/projects/docs-full-site/ru/IMPLEMENT__SOFTWARE-RELEASE-INFORMATION__DHIS2-CORE-RELEASES__DHIS-CORE-VERSION-240__upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-releases/blob/master/releases/2.40/README.md" revision_date: '2023-08-30' tags: -- DHIS core version 2.40 - Осуществлять +- DHIS core version 2.40 --- # 2.40 Upgrade Notes { #240-upgrade-notes } 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 1a2ad547..18a90b57 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__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 b01f742a..7dca8951 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 - Использовать +- 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 f5fc61a2..3b38f015 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 - Использовать +- 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 95f829fd..c338d025 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 - Использовать +- 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 99942e29..b29fc820 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 - Использовать +- 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 5c630078..b0b52e99 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 - Использовать +- 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 7680ff30..933b2566 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 - Использовать +- 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 99244685..ede7841d 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 - Использовать +- 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 fdbd0c73..fd7cc9be 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 - Использовать +- 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 db7a93d6..267007b5 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 - Использовать +- 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 07464214..fd5284a1 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 - Использовать +- 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 70867e4b..862e7371 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 - Использовать +- 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 71b7089a..cc75c95c 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 - Использовать +- 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 540ffe84..cb3f1e43 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 - Использовать +- 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 5938411c..44c63add 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 - Использовать +- 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 0219ad95..dd6c5560 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 - Использовать +- 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 e2294a54..99797852 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 - Использовать +- 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 83fa2957..a04fb8b1 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 - Использовать +- 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 543aafc4..06ad9b37 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 - Использовать +- 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 579657da..a0f9bada 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 - Использовать +- 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 66bd0d80..cf8ee4ae 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 - Использовать +- 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 2d20f766..bc2ca1d3 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 - Использовать +- 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 8c2c4bbe..0b3d20d4 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 - Использовать +- 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 3ae2bead..c2f2e429 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 - Использовать +- 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 c7cd05d5..6f9e08ff 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 - Использовать +- 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 7a3b1f40..0f53f25f 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 - Использовать +- 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 dd88cac7..cbeb5f41 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 - Использовать +- 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 1ca05359..ae2069fe 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 - Использовать +- 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 ff12c7f9..b3538e57 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 - Использовать +- 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 817e3480..fc9707fc 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 - Использовать +- 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 10eb2383..c92a359e 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 - Использовать +- 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 a032717c..5c52cef7 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 - Использовать +- 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 fe13ba9a..db22d97d 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 - Использовать +- 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 d3157361..555ebb93 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 - Использовать +- 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 d5b439e1..e3b9b88b 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-10-14' tags: -- DHIS core version 2.38 - Использовать +- 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 6ecaa0cb..c5559945 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 - Использовать +- 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 e3053c54..45bc62d4 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 - Использовать +- 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 ad03eb3d..8e5d0d6b 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 - Использовать +- 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 0d7ab33e..2ae4a48f 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 - Использовать +- 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 db3413e3..41114b5c 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 - Использовать +- 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 269105b3..ef5fd8b5 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 - Использовать +- 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 3f4841c1..19f69258 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 - Использовать +- 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 d7215fd8..beb171c0 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 - Использовать +- 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 82c3006f..498e913e 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 - Использовать +- 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 51ce1268..6b7a05ab 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 - Использовать +- 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 b223a45f..75d9e7ea 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 - Использовать +- 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 5176eb20..f9a1488c 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 - Использовать +- 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 814b1570..bb077ce4 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 - Использовать +- 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 bd643f5d..d30dbc2b 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 - Использовать +- 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 eec3b064..7c5668ca 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 - Использовать +- 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 f806b5eb..87d9b4d6 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 - Использовать +- 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 3cefbfa7..eb302d2d 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 - Использовать +- 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 664f1b3e..bc0cfa36 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 - Использовать +- 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 48f8e3dc..23448afd 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 - Использовать +- 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 562c8fed..edf82fc5 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 - Использовать +- 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 87a00494..2ef79234 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 - Использовать +- 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 550a391a..159d7a15 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 - Использовать +- 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 632a634e..c8687445 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 - Использовать +- 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 ef53947e..88d2d5a6 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 - Использовать +- 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 7391cea5..7f8dc09e 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 - Использовать +- 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 31444679..f04a3483 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 - Использовать +- 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 2eaf180d..cdfa2729 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 - Использовать +- 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 40983222..a60b3357 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 - Использовать +- 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 5ab1dc17..57746376 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 - Использовать +- 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 065de4ff..5ab9b0d6 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 - Использовать +- 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 394f787a..b3e8a890 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 - Использовать +- 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 d3ed54fe..e13509bc 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 - Использовать +- 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 ab2ec14b..733c2eb3 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 - Использовать +- 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 918df03a..c855dfca 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 - Использовать +- 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 7c0e2942..8a233478 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 - Использовать +- 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 2e992999..34a156e8 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 - Использовать +- 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 bd8ff976..1c5dea55 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 - Использовать +- 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 bc5bee39..9526da35 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 - Использовать +- 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 a64941b9..36e97d0a 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 - Использовать +- 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 6baab624..2925045e 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 - Использовать +- 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 d8620f0a..a13babe1 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 - Использовать +- 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 230f2fbe..a9b0517b 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 - Использовать +- 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 f54a4674..1f1bf3bc 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 - Использовать +- 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 f5bce97b..f0db5165 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-10-14' tags: -- DHIS core version 2.39 - Использовать +- 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 1b7bd948..3ad9d156 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 - Использовать +- 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 1c4a653b..c7831cae 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 - Использовать +- 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 f81e5195..15a411af 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 - Использовать +- 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 f39789bf..0dd1d0d2 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 - Использовать +- 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 08993b81..29bb0f8a 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 - Использовать +- 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 81fe43e7..ef243100 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 - Использовать +- 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 a0c040ee..eee45808 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 - Использовать +- 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 5203d779..1df47dc2 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 - Использовать +- 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-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md index 4fd97013..487edd4a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__demo-server-live-package-and-database-design-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-demo-server-live-package-and-database-design.md" revision_date: '2022-09-21' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # 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-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md index 45839e72..f8e2d9d3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-frequently-asked-questions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-frequently-asked-questions.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # DHIS2 Frequently Asked Questions { #dhis2-frequently-asked-questions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md index 483b4dc2..19cadb27 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-glossary-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-glossary.md" revision_date: '2021-07-13' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # DHIS2 Glossary { #dhis2_glossary } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md index e78e65b7..f2dee33a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__dhis2-tutorials-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/dhis2-tutorials.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # DHIS2 Tutorials { #dhis2_tutorials } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md index 1033071e..4bc9debf 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ADDITIONAL-INFORMATION__release-and-upgrade-notes-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/release-and-upgrade-notes.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Release and upgrade notes { #release-and-upgrade-notes } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md index 19ac864e..e3c1f38c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__dashboards-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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.40 - Использовать +- DHIS core version 2.40 --- # Managing dashboards { #dashboard } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md index 0747c2c1..00943b9e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__data-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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.40 - Использовать +- DHIS core version 2.40 --- # Using the Data Visualizer app { #data_visualizer } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md index ed6183bf..a8c1e945 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-reports-app.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Event Reports app { #event_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md index 56686c2e..63fae162 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__event-visualizer-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-visualizer-app.md" revision_date: '2022-03-21' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Event Visualizer app { #event_visualizer_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md index 6ac3d986..398d3368 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__line-listing-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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.40 - Использовать +- DHIS core version 2.40 --- # Using the Line Listing app { #using-the-line-listing-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md index ccdbf5d9..585160d6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/maps-app/blob/master/docs/maps.md" revision_date: '2024-07-31' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Maps app { #using_maps } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md index ba0fb911..cbff26a9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__ANALYSING-DATA__reports-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-reporting-functionality.md" revision_date: '2022-02-08' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Reporting functionality in the reports app { #using_the_reports_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md index aad8428b..355809f2 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__approving-data-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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.40 - Использовать +- DHIS core version 2.40 --- # Data approval { #data_approval_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md index 7d5c1620..37f3034d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__APPROVING-DATA__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-approval.md" revision_date: '2021-11-04' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Data approval overview { #data_approval_overview } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md index 4aec4248..781b71fc 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-beta-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-aggregate-data-entry-app.md" revision_date: '2022-10-20' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Data Entry (beta) app { #data-entry-beta-app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md index 829cae12..b1a2d1c5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-data-entry-app.md" revision_date: '2024-07-12' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Data Entry app { #data_entry_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md index 97f83d2c..1e742285 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__COLLECTING-DATA__data-quality-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/control-data-quality.md" revision_date: '2021-11-04' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Control data quality { #control_data_quality } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md index 49bbdb36..e40648ff 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__about-sharing-of-objects-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-sharing-of-objects.md" revision_date: '2021-10-07' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # About sharing of objects { #sharing } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md index d38470c8..0a46e7b6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__maps-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-the-gis-app.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Configure DHIS2 Maps { #gis_creating } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md index 48e4dc7e..8a83abf6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata.md" revision_date: '2023-07-20' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Configure metadata { #maintenance_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md index 9336b00b..5c060e53 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__programs-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-programs-in-the-maintenance-app.md" revision_date: '2024-07-12' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # 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-240__CONFIGURING-THE-SYSTEM__report-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md index d38abdd2..7178774e 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__report-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-report-functionality.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Configure report functionality { #setting_up_reporting } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md index 6c8e5741..3cf42574 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__system-settings-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/system-settings.md" revision_date: '2024-01-25' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # System settings { #settings } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md index 6ed6f14a..44d40558 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__user-authorities-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/user-authorities.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # User authorities { #user_authorities } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md index dc25b0ce..dc665c0c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__CONFIGURING-THE-SYSTEM__users-roles-and-groups-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/manage-users-user-roles-and-user-groups.md" revision_date: '2022-10-12' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # 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-240__EXCHANGING-DATA__data-exchange-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md index 459de235..7247234d 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-exchange.md" revision_date: '2023-02-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Data Exchange app { #data_exchange } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md index b753ca50..ca647c0a 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__importexport-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/importexport-app.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Import/Export App { #import_export } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md index 74a5e81d..9080152c 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__EXCHANGING-DATA__metadata-synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/configure-metadata-synchronizing.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Configure metadata synchronizing { #metadata_sync } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md index ce8e1496..63165c55 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__configure-sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/sms-configuration.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Configuring SMS { #sms-configuration-intro } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md index effbbf44..eb362f58 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__data-administration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/data-administration.md" revision_date: '2024-07-04' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Data Administration { #data_admin } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md index e6cc27a7..578152f1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__datastore-manager-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/datastore-manager.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Datastore Manager { #datastore_manager_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md index 55c23fcc..ec62a9be 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__installing-applications-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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.40 - Использовать +- DHIS core version 2.40 --- > **Caution** diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md index d5629703..2f4a5513 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__mobile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/mobile.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Mobile { #mobile } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md index fd4bbdc6..bc1cc577 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/scheduling.md" revision_date: '2022-03-19' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Scheduling { #scheduling } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md index 217145c6..2c3f8d71 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__MAINTAINING-THE-SYSTEM__visualize-usage-statistics-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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.40 - Использовать +- DHIS core version 2.40 --- # Visualize usage statistics { #using_usage_analytics } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md index cc0e1cdd..ad28aa18 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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-10-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Capture app { #capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md index 305462a4..4b12dfa3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__event-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-event-capture-app.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Event Capture app { #event_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md index 448940bb..638808f9 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__TRACKING-INDIVIDUAL-LEVEL-DATA__tracker-capture-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/using-the-tracker-capture-app.md" revision_date: '2022-03-10' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Using the Tracker Capture app { #tracker_capture_app } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md index 96aea458..c87c19a5 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__about-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/about-data-dimensions.md" revision_date: '2021-11-18' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # About data dimensions { #data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md index 83405ef4..5c1a93a3 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__additional-data-dimensions-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/additional-data-dimensions.md" revision_date: '2021-08-17' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Additional data dimensions { #additional_data_dimensions } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md index d79bfcf0..98ee9671 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__UNDERSTANDING-THE-DATA-MODEL__relationship-model-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/relationship-model.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Relationship model { #relationship_model } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md index 03365195..3cbc42c6 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Messaging { #messages } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md index bd8a61a8..6b501c17 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__personal-access-tokens-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/user/personal-access-tokens.md" revision_date: '2022-03-21' tags: -- DHIS core version 2.40 - Использовать +- DHIS core version 2.40 --- # Personal access tokens { #personal_access_tokens } diff --git a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md index aa70370d..aeb208e1 100644 --- a/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__WORKING-WITH-YOUR-ACCOUNT__set-user-account-preferences-md +++ b/projects/docs-full-site/ru/USE__USER-GUIDES__DHIS-CORE-VERSION-240__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.40 - Использовать +- DHIS core version 2.40 --- # 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 33186499..5fa21ad6 100644 --- a/projects/docs-full-site/si/.cache_timestamp +++ b/projects/docs-full-site/si/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:23:06Z \ No newline at end of file +2024-10-19T21:23:39Z \ No newline at end of file diff --git a/projects/docs-full-site/si/IMPLEMENT__DATA-USE__data-visualization-md b/projects/docs-full-site/si/IMPLEMENT__DATA-USE__data-visualization-md new file mode 100644 index 00000000..1c0a9753 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__DATA-USE__data-visualization-md @@ -0,0 +1,341 @@ +--- +edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/data-use/data-visualization.md" +revision_date: '2024-10-18' +tags: +- Implement +--- + +# Data Visualization Best Practices { #data-visualization-best-practices } + +## Introduction { #introduction } +Data visualization is a powerful tool for understanding and communicating data. The choices made in visualization are crucial and should be guided by the type of data and the message that needs to be conveyed. Proper visualization can reveal patterns, trends, and insights that might be missed in raw data. Fortunately, data visualization follows established rules and design principles that align with the type of variables being used, ensuring that it is not a matter of personal opinion but rather a structured and effective approach. + +## Variables { #variables } + +**Any Measurable Characteristic is a Variable** +Variables can be broadly classified into two categories: + +1. Categorical (Qualitative) +2. Numerical (Quantitative) + +Understanding these categories is essential to selecting the correct chart type and designing it effectively. + +### Categorical Variables { #categorical-variables } + +- **Nominal** - Unordered categories (e.g., marital status). These categories do not have a meaningful order. + - For example, marital statuses like single, married, divorced, and widowed are distinct categories without a ranked order. +- **Ordinal** - Categories with a meaningful order (e.g., disease status). These categories have a logical sequence. + - For example, disease severity might be classified as mild, moderate, and severe, which has an inherent order. + +> **Note** +> +> **Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. + +![Variable categories](resources/images/dataviz_001.png) + +### Numerical Variables { #numerical-variables } + +- **Discrete** - Countable number of variables (e.g., number of siblings, dead/alive = discrete dichotomous). Discrete variables take specific values and cannot be meaningfully divided. + - For example, you can't have half a sibling or be half alive. +- **Continuous** - Infinite values within a given interval (e.g., weight and height, pass/fail = continuous dichotomous). Continuous variables can take any value within a range. + - For example, height can be 170.5 cm or 170.55 cm. + +## Choosing the Right Chart { #choosing-the-right-chart } + +What’s the best way to choose the right visualization for the data at hand? [From data to Viz](https://www.data-to-viz.com/) proposes an exhaustive map of visualizations matched to the category of data. + +Another Chart Chooser is mapped in the [Extreme Presentation Method](https://extremepresentation.com/). + +![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.jpg) + +The summary below is based on the visualizations available in the core DHIS2 Data Visualizer App. + +### Categorical Variables { #categorical-variables } + +#### Single categorical variable { #single-categorical-variable } + +- **Barplot**: Displays the frequency or proportion of categories using bars. Each bar represents a category, and its height indicates the value. +- **Pie chart**: Represents parts of a whole as slices of a circle. Each slice’s size is proportional to the category's frequency. +- **Spider plot**: Also known as a radar chart, it shows multiple categories on axes starting from the same point. Useful for displaying performance metrics across different categories. + +#### Multiple categorical variables { #multiple-categorical-variables } + +- **Grouped/stacked Barplot**: Grouped barplots show bars for each category side by side, while stacked barplots stack them on top of each other. +- **Heatmap**: Uses colour to represent values in a matrix format, where one dimension represents one category and another dimension represents the second category. + +### Numerical Variables { #numerical-variables } + +#### Single numerical variable { #single-numerical-variable } + +- **Histogram**: Shows the distribution of a numerical variable by dividing the data into bins and displaying the frequency of observations in each bin. + +#### Two numerical variables { #two-numerical-variables } + +- **Ordered** + - **Area plot**: Similar to line plots but with the area under the line filled. Useful for showing cumulative values over time. + - **Line plot**: Displays information as a series of data points connected by straight lines. Suitable for trends over time. +- **Unordered** + - **Histogram**: This can also be used to compare the distributions of two different variables. + - **Scatter plot**: Plots two variables as points on a Cartesian plane. Each point represents an observation's values on the two variables. + +#### Three numerical variables { #three-numerical-variables } + +- **Stacked area plot**: Shows multiple series of data as layers stacked on top of each other. Each layer represents a series' value. +- **Line plot**: Can be used to show multiple series of data over time. + +#### Four or more numerical variables { #four-or-more-numerical-variables } + +- **Ordered**: + - **Stacked area plot**: Shows multiple series of data as layers stacked on top of each other. Each layer represents a series' value. + - **Line plot**: This can show trends of several variables over time. +- **Unordered**: + - **Heatmap**: Uses color gradients to represent data values in a matrix, making it easy to spot patterns and outliers. + +### Specific Visualization Styles { #specific-visualization-styles } + +> **Note** +> +> **Data speaks louder than words!** + +In data visualization, choosing the right type of chart or graph is crucial for effectively communicating your data. Each visualization style has its strengths and is best suited for specific types of data and analytical purposes. This chapter explores a variety of visualization styles, detailing their applications and best practices. Whether you're looking to show trends over time, compare quantities, highlight correlations, or illustrate parts of a whole, selecting the appropriate visualization method will enhance clarity and insight. By understanding the nuances of each style, you can ensure that your data tells a compelling and accurate story. + +![Data visualization styles available in DHIS2](resources/images/dataviz_025.png) + +#### Correlation { #correlation } + +> **Caution** +> +> Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. + +- **Scatterplot**: Shows the relationship between two continuous variables, each having its axis. Each point represents an observation's values on the two variables. It's useful for identifying trends, clusters, and outliers. For example, a scatterplot can display the relationship between the number of immunization campaigns conducted in various districts and the resulting immunization coverage rate. + + +![Scatterplot found in the EPI-Program Performance Dashboard plotting coverage vs dropout rates](resources/images/dataviz_003.png) + +- **Column + line timeline**: Shows the relationship between an amount (columns) and a rate (line). This combination is often used to compare a quantity with its rate of change over time, such as HIV-tested patients (columns) and positivity rate (line). + +![Double axis chart with columns and line showing measles cases and coverage](resources/images/dataviz_004.png) + +#### Ranking { #ranking } + +> **Note** +> +> Emphasizes the item's position in an ordered list rather than the absolute value. + +- **Ordered bars/columns**: Shows ranks of values more easily when sorted. This visualization helps to quickly see the highest and lowest values. An ordered bar column chart can be used to display the number of TB cases in each district, sorted in descending order to highlight the districts with the highest burden. + +![Ordered stacked bar chart of TB cases by reporting district](resources/images/dataviz_005.png) + +- **Slopes**: Shows how ranks have changed over time. Useful for visualizing changes in ranking positions, such as tracking the incidence of malaria in different regions over several years to see how the ranking of regions by incidence rate changes over time. + +![Slopes on inpatient malaria incidence across different Districts through time](resources/images/dataviz_006.png) + +#### Change Over Time { #change-over-time } + +> **Note** +> +> Keep gaps between columns small to highlight data shape. +Use markers for irregular data points. + +- **Column**: Emphasizes changing trends. Columns are used to show discrete data points over time. For example, monthly case figures can be shown as a column chart. + - **Keeping the space between columns** in a column chart close to each other is crucial for emphasizing the continuity and patterns within the data. When columns are placed closely together, it creates a more cohesive visual representation, making it easier to compare values across categories or periods. This proximity helps the viewer quickly identify trends, variations, and overall data distribution, enhancing the clarity and effectiveness of the chart. Additionally, minimizing the gaps between columns reduces visual clutter and ensures that the focus remains on the data itself, rather than on the empty spaces. + +![Columns for monthly HIV cases](resources/images/dataviz_007.png) + +- **Line**: Best for visualizing continuous data over time. Line charts are effective for showing trends, cycles, and fluctuations. For example, a line chart could track the changes in CD4 cell counts over time for a cohort of patients, illustrating the impact of treatment interventions. + +- **Year over Year (column and line)** - Compares the same period across different years to show trends over multiple years using lines. For example, the YoY line could be used to compare malaria incidences across several years, while the YoY columns could be used to visualizing the annual malaria number of malaria cases over multiple years. + +- **Area charts**: Good to show changes in totals but tricky for components. Area charts are powerful for illustrating trends and changes over time, providing a strong visual impact by highlighting the magnitude and total values of data sets. They are particularly effective for showing cumulative data and allowing comparisons of multiple data series. However, they can become cluttered and difficult to read when multiple categories are involved, as distinguishing individual components can be challenging. Additionally, changes in lower layers can distort the perception of upper layers, potentially leading to misinterpretation. While effective for highlighting totals, area charts are less suitable for discrete data points or non-cumulative data and can be problematic for colourblind viewers or black-and-white prints. For example, it could be tracking the total number of TB or malaria cases reported across different regions over a year to visualize the overall burden and trends. + +![Area chart for the volume of malaria cases in three districts](resources/images/dataviz_008.png) + +#### Magnitude { #magnitude } + +> **Note** +> +> Small gaps highlight data shape. Best for a single series of data. + +- **Column/Paired column/bar**: Compare sizes, usually numbers rather than rates or percentages. For instance, HIV case figures for different regions can be compared using a bar chart. In this case, it is appropriate to keep the distance between the columns as they represent separate entities rather than variables through time. + +![Paired columns of HIV new cases and HIV new cases who started ART across different districts](resources/images/dataviz_009.png) + +#### Performance Metrics { #performance-metrics } + +- **Radar**: Radar charts, also known as spider or web charts, are efficient for displaying multiple variables, making them ideal for visualizing performance metrics such as the strengths and weaknesses of a team across various skills. They allow for a comprehensive view of data at a glance, highlighting comparative performance across different categories. However, radar charts can become cluttered and hard to interpret with more than five groups, leading to overlapping lines and a confusing presentation. This type of chart is not suitable for trendline visualizations as it does not effectively display changes over time. Pros of radar charts include their ability to compare multiple variables simultaneously and their intuitive, visual appeal. Cons include potential clutter with too many variables, difficulty in precise comparison, and the risk of misinterpretation due to the distortion of area size. Common mistakes include overloading the chart with too many variables, not starting scales from zero, and using them to represent data trends rather than comparative metrics. + +![Radar chart on Rehab condition groups and their use across two districts](resources/images/dataviz_010.png) + +#### Part-to-Whole { #part-to-whole } + +> **Tip** +> +> Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** + +![Imrpove the visualization choosing the most suitable colour set](resources/images/dataviz_022.png) + +- **Stacked column/bar**: Shows how a single entity breaks down into components. This is useful for comparing the composition of different groups. +Stacked columns or bar charts **should be avoided when** a detailed comparison of individual data points is required, when dealing with a large number of categories when showing trends over time, when data categories are not additive, when highlighting individual segment changes, or when data intervals are non-uniform. These charts can obscure important details and lead to misinterpretation if used improperly. + +![Stacked columns for TB cases - lab confirmed and clinically confirmed](resources/images/dataviz_011.png) + +- **Pie chart**: Each slice represents a part of the whole, which can be useful for showing proportions. Pie charts **should be avoided when** comparing multiple categories, showing trends over time, needing precise value representation, dealing with negative values, when the total is not meaningful, and for complex data sets. These limitations can lead to misinterpretation and obscure important details, making other chart types like bar, line, or scatter plots more appropriate for these scenarios. + +![Sex for notified TB cases](resources/images/dataviz_012.png) + +#### Single Value Display { #single-value-display } + +- **Gauge**: Used to represent a single value within a range, similar to a speedometer. It is ideal for showing progress towards a target or current status against a benchmark. It could be used to display the current immunization coverage rate as a percentage of the target. + +![Coverage rate for BCG](resources/images/dataviz_026.png) +- **Single Value**: Displays a single metric prominently. Useful for highlighting key performance indicators (KPIs) or critical numbers. In DHIS2 it is possible to associate colour-based legends to highlight progress or thresholds. + +![Coverage rate for BCG with a colour-based legend representative of the EPI coverage threshold](resources/images/dataviz_027.png) + +#### Detailed Analyses { #detailed-analyses } + +- **Pivot Tables**: Useful for summarizing, analyzing, exploring, and presenting summary data. Pivot tables are interactive and can be used to create custom reports. For example, tables can be used to summarize the number of TB cases by district and month, allowing users to drill down into specific data points for more detailed analysis. + +![Pivot table of the target population for a supplementary immunisation activity by age groups, distance from the PoC, and locations. Note the row and column totals as well as the subtotals by category](resources/images/dataviz_028.png) + +**Scorecards** provide an added value by visually representing key performance indicators (KPIs) against predefined targets. They are particularly useful for tracking progress, identifying areas for improvement, and communicating performance at a glance. For instance, a scorecard could display the performance of various health facilities in terms of patient satisfaction, staff efficiency, and resource utilization. This tool helps stakeholders quickly assess whether they are meeting their goals and where interventions might be needed. Scorecards foster accountability and transparency within health systems, ensuring everyone is aligned towards common objectives. + +![Scorecard highlighting the MR coverage reported by routine EPI- and SIA-related activities](resources/images/dataviz_031.png) + +#### Spatial { #spatial } + +- **Choropleth**: Standard for rates on maps. Uses varying shades of a colour to represent data values for different regions. For example, population density by region can be shown using a choropleth map. + +> **Note** +> +> **Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. + +![Map showing the percentage of PTB-BC cases in a region](resources/images/dataviz_013.png) + +- **Proportional symbol**: Good for totals. Symbols of different sizes are placed on a map to indicate the value at each location. + +![Map showing number of notified cases in a region](resources/images/dataviz_014.png) + +![Map showing the location of the unvaccinated children and the reason for the missed vaccination](resources/images/dataviz_015.png) + +- **Dot density**: Shows the location of events. Each dot represents a set number of occurrences of a phenomenon. + +![Map showing the population density in the region](resources/images/dataviz_021.png) + +- **Heat map**: Uses grid-based data values with an intensity colour scale. It shows data density and can be used for data that varies smoothly over an area, like temperature rates. + +![Map showing the mean temperatures across the country](resources/images/dataviz_016.png) + +#### Google Earth Integration with DHIS2 { #google-earth-integration-with-dhis2 } + +DHIS2 offers powerful integration with Google Earth Engine, allowing users to access a range of detailed datasets, such as population (WorldPop), building footprints, elevation, land use, and climate data. + +The detailed steps and best practices for integrating Google Earth Engine with DHIS2 can be found in the [DHIS2 Documentation](https://community.dhis2.org/t/using-population-elevation-landcover-and-climate-layers-in-dhis2-maps/51586) and the [DHIS2 Version 2.39 Overview](https://dhis2.org/overview/version-239/). These pages provide comprehensive guides and updates on the functionalities of DHIS2, including the integration with Google Earth Engine and the capabilities of using population, elevation, landcover, and climate layers within the DHIS2 Maps application. + +##### Best Practices for Integration { #best-practices-for-integration } + +- **Data Utilization**: Use the extensive datasets available from Google Earth Engine to enhance your spatial analysis. This includes integrating population density maps, land use patterns, and climate data to better understand health trends and resource distribution. +- **Customization**: Tailor the integration to meet the specific needs of your health programs by leveraging the flexibility of DHIS2’s mapping capabilities. This can involve customizing map layers to highlight key indicators relevant to your programs. +- **Performance Monitoring**: Regularly monitor and update your Google Earth Engine access and configurations to ensure optimal performance and data accuracy. + +### Common Mistakes { #common-mistakes } + +#### Ignoring Data Density { #ignoring-data-density } + +Overlooking the issue of data density can lead to charts that are cluttered and difficult to interpret. When data points overlap too much, important patterns and trends can be obscured, making it challenging for viewers to extract meaningful insights. + +#### Spaghetti Chart { #spaghetti-chart } + +**Avoid cluttering your chart with too much information**. A spaghetti chart is an overly complex line chart with many intersecting lines, making it hard to read. + +![The chart appears cluttered and difficult to interpret](resources/images/dataviz_017.png) + +Alternatives to avoid messy charts: + +- **Small multiples**, also known as panel charts or trellis charts, are a series of similar graphs or charts using the same scale and axes, allowing easy comparison across different categories. You can create multiple line charts and display them in the dashboard one next to the other. E.g. Showing the monthly TB cases for different regions in separate subplots. +- **Organizational Units**. Check whether it is necessary to provide the info for every OU. Highlight one or a few key series in a line chart and show the remaining series in a more muted colour to reduce clutter and emphasize important trends. E.g. Highlighting the regions with the highest TB cases while showing other regions in lighter lines for context. + +![Cluttered graph by lower OUs](resources/images/dataviz_032.png) + +- **Interactive dashboards** allow users to filter and explore data dynamically, which can be especially useful for complex multi-series data. In DHIS2 Dashboards users can select specific regions or periods to view detailed trends in TB cases. +- **Heatmaps** use colour to represent data values in a matrix, allowing for easy comparison of values across two dimensions. The maps in DHIS2 can be displayed as SIngle (Aggregate), Split views, or Timeline. + +#### Overcluttered Visuals { #overcluttered-visuals } + +Adding too many elements makes the chart hard to read. **Simplify visuals by focusing on the most relevant data and using clear, concise legends and labels**. + +![Overloading a map with too many layers and data points](resources/images/dataviz_023.png) + +In addition, this map uses a colour scheme that might not be accessible to colourblind individuals, making it difficult to interpret for a significant portion of the population. **Use colorblind-friendly palettes** that ensure all users can distinguish between different data values. Tools like [ColorBrewer](https://colorbrewer2.org/) provide palettes designed for colourblind accessibility. Refer to the “Part-to-whole” section of the document to see how to change the colour scheme of your visualizations. + +#### Crammed Dashboards { #crammed-dashboards } + +Squeezing too many visualizations into a single dashboard can make them unreadable and ineffective. Each visualization should have enough space to be interpreted. Overloading a dashboard with too many elements can overwhelm the viewer and obscure key insights. Aim for a balanced layout where each visualization can be easily read and understood. + +![The items in the dashboards are too small for what they need to convey, the labels are unreadable, the pivot table does not have space to display the variables](resources/images/dataviz_023.png) + +#### Lack of Context { #lack-of-context } + +Failing to provide necessary context, such as labels, titles, legends, and explanatory notes, can leave the audience confused about what the chart is representing. **Context is crucial for helping viewers understand the data being presented and drawing accurate conclusions**. + +A visualization should always have: + +- **Titles**: Always include a descriptive title that clearly states what the chart is about. The title should provide enough information to make the chart understandable at a glance. +- **Axis Labels**: Label the x-axis and y-axis to specify what data they represent. Include units of measurement where applicable. +- **Legends**: Provide a legend when using colours, symbols, or different lines to distinguish between multiple data series or categories. Ensure the legend is clear and easy to interpret. +- **Explanatory Notes**: Include any necessary explanatory notes or footnotes to clarify data sources, any assumptions made, or specific data points that require additional context. In DHIS2 one could add notes and explanations by clicking the three dots on teh right of the visualizations and selecting “Show details and interpretations”. + +![Contextualized graph](resources/images/dataviz_024.png) + +> **Caution** +> +> Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. + +#### Pie Chart { #pie-chart } + +**Humans are bad at reading angles**. Avoid pie charts for detailed comparisons. In a pie chart, it can be difficult to compare the sizes of slices accurately. +A bar or a column can be equally used through horizontal bars that focus more on the comparison between the categories than the values. + +![Pie charts with a lare number of categories to be compared](resources/images/dataviz_018.png) + +#### Totals and Parts { #totals-and-parts } + +**Presenting a total and its parts in the same chart can be misleading, redundant, and visually cluttered, making it difficult for the audience to accurately interpret the data**. To enhance clarity and focus, it is better to use separate charts for the total and its components. + +- **Misleading Representation**: Combining the total and its parts in the same chart can be misleading. The total value includes all parts, and placing them together may create a false impression of comparison between different metrics. Moreover, including both totals and parts in a single chart can detract from the clarity and focus. The audience might find it confusing to distinguish between the total and the individual contributions. +- **Scale Issues**: The total and its components often have vastly different scales. The total number will always be larger than any of its parts, making it difficult to interpret and compare the smaller values accurately. +- **Redundancy**: Showing both the total and its parts in the same chart is redundant. Since the total is simply the sum of the parts, it doesn’t provide additional information and can clutter the visualization. + +![Doses given as a total within the country and the doses by district](resources/images/dataviz_019.png) + +As an alternative, one could opt for: + +- **Separate Bar Charts**: Use one bar chart to display the total number of doses given in the country and another bar chart to show the doses distributed by each district. This separation maintains clarity and allows for easier comparison and understanding. +- **Stacked Bar Chart**: Use a stacked bar chart where each bar represents the total doses for the country, but the bar is divided into segments representing each district. This method keeps the parts and totals together but differentiates the contributions of each part. This is only acceptable if the number of entities is not cluttering the visualization and falling into the same trap as the spaghetti chart. + +#### Inappropriate Chart Types { #inappropriate-chart-types } + +Using the wrong type of chart for the data can mislead viewers and obscure the intended message. Each chart type has its strengths and weaknesses, and choosing the correct one is crucial for effective data visualization. + +- **Example 1**: Using a line chart to display categorical data, such as the number of health facilities by type (e.g., clinics, hospitals, mobile units), is inappropriate. Line charts are designed to show trends over time and assume a sequential order in the data points. Categorical data, however, do not have a natural order and are best represented by bar charts or pie charts. +- **Example 2**: Using a pie chart to display small differences in a large number of categories, such as the number of malaria cases in different regions, is inappropriate. Pie charts work best with a small number of categories where differences are large and easily distinguishable. With many categories, the slices become too small to differentiate, making the chart hard to read and interpret. Bar charts are better for comparing many categories with small differences. For example +- **Example 3**: Using a radar chart (also known as a spider chart) to display trendlines over time is inappropriate. Radar charts are designed to compare multiple variables across different categories in a circular format. They are not suited for showing trends over time because they do not follow a sequential order and can make it difficult to interpret changes over time. Line charts or bar charts are more appropriate for illustrating trends over time as they depict changes in data points along a continuous timeline. + +![Spider chart used wrongly to display the changes in notified TB cases over time](resources/images/dataviz_029.png) + +- **Example 4**: Using a double-axis chart with columns to display the number of HIV tests performed in different districts (x-axis) and a line to depict the HIV test positivity rate across these districts is inappropriate. The line incorrectly implies a sequential relationship and trend across districts. Each district's positivity rate is a standalone value and should not be connected as if they follow a continuous trend. Instead, the best way to visualize this data would be a pivot table. A pivot table allows you to display the number of HIV tests and the positivity rate side by side for each district without implying a false trend or relationship between the districts. + +![Double axis wrongly unifying stand alone entities](resources/images/dataviz_030.png) + +#### Separate Entities vs Change Over Time { #separate-entities-vs-change-over-time } + +When visualizing separate entities, such as the doses of a vaccine distributed across different districts, using distinct columns for each district helps clearly distinguish between the different entities. This approach ensures that the data for each district is easy to compare, highlighting the variations in vaccine distribution between districts. Conversely, when visualizing changes over time, such as the number of vaccines distributed in a specific organizational unit, columns should be placed with minimal separation to emphasize the continuity and trends over the period. This close placement helps to illustrate the flow and progression of vaccine distribution, making it easier to identify patterns, peaks, and troughs in the data. + +![Separate entities on the left vs continuous change over time on the right](resources/images/dataviz_020.png) + +### Conclusion { #conclusion } + +**Effective data visualization requires selecting the appropriate chart type based on the variable types and the message you wish to convey**. It’s essential to avoid common mistakes and ensure clarity for the audience. For instance, when illustrating spatial distribution, a map is more relevant as it effectively shows clusters and the distribution of high and low-coverage areas. When checking efforts, absolute numbers are more meaningful if they include target values for comparison. Additionally, for accurate comparisons, it is crucial to normalize data distribution. Good visualization practices enhance understanding and facilitate better decision-making, ensuring that the data tells a compelling and accurate story. + +Would you like to test your knowledge of variables and data visualization best practices? **Take the [quiz](https://docs.google.com/forms/d/e/1FAIpQLSddz_jtVrFSJssNiCYTHQ12tm6x1A6Gs6QB5Lhlmeq0Je3vDw/viewform?usp=sf_link)**! + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md new file mode 100644 index 00000000..fcf860d2 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -0,0 +1,206 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-design.md" +revision_date: '2023-03-31' +tags: +- Implement +--- + +# COVID-19 Surveillance - Aggregate System Design Guide { #c19-agg-design } + +## Purpose { #purpose } + +The COVID-19 Surveillance Aggregate System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +This aggregate design has been updated to reflect new aggregate reporting requirements from the [Global surveillance of COVID-19: WHO process for reporting aggregated data](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form), last updated on August 7, 2020. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| **Type of Surveillance Package** | **Case-based Surveillance (Tracker)** | **Case surveillance line-listing (Event)** | **Case surveillance (Aggregate)** | +| --- | --- | --- | --- | +| **Description** | Enrolls a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables weekly reporting of key aggregate data points | +| **Pros** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| **Cons** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation)| + +**This document covers only the design of the aggregate package**; separate system design documents are available for DHIS2 Tracker and Line-listing (event-based) packages. As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The aggregate package is designed to meet the most critical reporting requirements and analytical capacities for surveillance and response. + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated August 7, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +The aggregate COVID-19 surveillance package includes + +1. Weekly aggregate data set and data elements for key COVID-19 surveillance reporting +2. Categories for data disaggregation +3. Core indicators +4. Dashboard and its items + +The dataset captures a minimum number of data points that meet the current WHO weekly reporting requirements; and generate a core set of indicators and dashboards for national and sub-national decision-makers to rapidly analyze and respond to disease trends. + +| **Name** | **Periodicity** | **Purpose** | +| --- | --- | --- | +| Aggregate Weekly Surveillance | Weekly| Reporting of key COVID-19 surveillance data including cases, tests and deaths. | + +It is recommended that the weekly dataset is assigned to Organisation Units at the lowest level of the health system feasible for reporting data, such as health facilities. + +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). + +### Intended users { #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. +- 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 + +## Datasets { #datasets } + +This dataset is intended to capture weekly data needed for rapid response to disease transmission. If the burden of reporting becomes too great or when it is no longer considered an emergency situation in the country, the data set may be changed to monthly according to MOH policies. + +### Daily Surveillance Data Elements { #daily-surveillance-data-elements } + +The following lists the data elements and disaggregation (category combinations) included in the data set: + +| **Data Elements** | **Category Combinations** | +| --- | --- | +| New Confirmed Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Confirmed Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Hospitalized Cases | None | +| New Discharged Cases | None | +| New Cases Among Health Workers (Confirmed + Probable) | None | +| New Deaths Among Health Workers (Confirmed + Probable) | None | +| Number of Persons Tested for COVID-19 | None | +| Number of persons Tested with PCR Assay | None | +| Transmission Classification | None | + +### Weekly Surveillance Data Entry Form { #weekly-surveillance-data-entry-form } + +- **Section 1: New confirmed and probable Cases** + +Data should be entered for all new confirmed and probable cases reported during the reporting period. Confirmed cases refer to laboratory confirmed cases per WHO guidance; probable cases are defined by WHO as cases where laboratory test result is inconclusive; however countries may apply their own case definitions. The total column is automatically summed during data entry. +![Picture1](resources/images/AGG_Picture1.png) + +- **Section 2: New confirmed and probable deaths** + +Data should be entered for new confirmed and probable deaths reported during the reporting period. The total column is automatically summed during data entry. + +![Picture2](resources/images/AGG_Picture2.png) + +- **Section 3: Health worker infection and death** + +This section captures data for health workers' new confirmed and probable cases including deaths reported during the reporting period. + +![Picture3](resources/images/AGG_Picture3.png) + +- **Section 4: Hospitalisation and discharges** + +This section captures data for new hospitalisation and discharges during the reporting period. + +![Picture4](resources/images/AGG_Picture4.png) + +- **Section 5: Tests conducted** + +This section captures data for tests conducted with additional requirement to report tests conducted using PCR during the reporting period + +![Picture5](resources/images/AGG_Picture5.png) + +- **Section 6: Transmission Classification** + +This section summarizes the major form of transmission classification experienced by the reporting unit. + +![Picture7](resources/images/AGG_Picture6.png) + +### Customizing Data Entry Forms { #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) + +## Data Validation { #data-validation } + +The following data validation rules have been configured. These validation rules do not run in the data entry form itself as it is anticipated that the urgent reporting of data where events occur in different time frames (e.g. one week can see only 3 new cases but 5 deaths). + +| **Name** | **Operator** | **Instruction** | **Left side description** | **Right side description** | +| --- | --- | --- | --- | --- | +| COVID19 - PCR tests \<= tested | less\_than\_or\_equal\_to | Tested with PCR should be less than or equal to total tests conducted | Tested with PCR | Tested conducted | +| COVID19 - New Cases hospitalised \<= All New Cases | less\_than\_or\_equal\_to | New Cases hospitalised should be less than or equal to all new cases | New Cases hospitalised | All New Cases | +| COVID19 - New confirmed deaths \<= New confirmed cases | less\_than\_or\_equal\_to | New confirmed deaths should be less than or equal to New confirmed cases | New confirmed deaths | New confirmed cases | +| COVID19 - Probable deaths \<= New probable cases | less\_than\_or\_equal\_to | Probable deaths should be less than or equal to New probable cases | Probable deaths | New probable cases | +| COVID19 - New deaths among HW (confirmed + probable) \<= All deaths reported | less\_than\_or\_equal\_to | New deaths among HW (confirmed + probable) should be less than or equal to All deaths reported | New deaths among HW (confirmed + probable) | All deaths reported | +| 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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Please refer to the [installation guidance](covid-19-aggregate-installation.html) for more information. + +## Indicators { #indicators } + +From the data captured, we can calculate at least the following indicators, many of which are recommended by the WHO for [weekly reporting](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) and present them in a dashboard. All COVID-19 program indicators are assigned to the Indicator Group 'COVID19'. + +| **name** | **description** | +| --- | --- | +| COVID19 - New Confirmed Deaths | Number of new confirmed deaths | +| COVID19 - New Cases Among HW (Confirmed + Probable) | Number of New Cases Among HW (Confirmed + Probable) | +| COVID19 - Proportion of HW amongst reported cases (%) | Proportion of HW amongst reported cases (%) | +| COVID19 - Active cases | Number of of active cases | +| COVID19 - Closed cases | Number of closed cases | +| COVID19 - New Confirmed cases | Number of new Confirmed cases | +| COVID19 - Recovery rate (%) | Recovery rate of confirmed cases | +| COVID19 - Case fatality rate among HW (%) | Case fatality rate among HW | +| COVID19 - New Hospitalized Cases | New Hospitalized Cases | +| COVID19 - Tested | Total number of tests conducted | +| COVID19 - Tested with PCR Assay | Tested with PCR assay | +| COVID19 - Positivity rate (%) | Positivity rate | +| COVID19 - New Probable Cases | Number of new probable cases | +| COVID19 - New Discharged Cases | Number of new discharged cases | +| COVID19 - New Deaths Among HW (Confirmed + Probable) | Number of new deaths among HW (Confirmed + Probable) | +| COVID19 - Proportion of PCR tests (%) | Proportion of PCR tests conducted | +| COVID19 - All cases (Confirmed + Probable) | Number of all cases (Confirmed + Probable) | +| COVID19 - New Probable Deaths | Number of new probable deaths | +| COVID19 - Case fatality rate (%) | Case fatality rate among confirmed cases | + +## Dashboards { #dashboards } + +Key analytic items have been configured and added onto the dashboard “COVID19 - Aggregate Weekly Surveillance”. These items include; pivot tables, charts and a map designed to provide data visualization for some of the data captured based on the indicators. In the process of adopting this package, users can modify or create additional items as suits their analytical needs and equally make the necessary adjustments to the dashboard. + +| **name**|**type**| +| --- | --- | +|COVID19 - Tested, tests with PCR and positivity rate by subnational level this year |Pivot table| +|COVID19 - HW amongst reported cases this year |Chart| +|COVID19 - Fatality rate amongst HW.|Chart| +|COVID19 - New confirmed cases and deaths in the last 12 weeks|Chart| +|COVID19 - Cumulative tests conducted, cases reported, hospitalised, discharged and deaths|Chart| +|COVID19 - Cumulative confirmed cases by subnational|Map| +|COVID19 - Deaths by age groups last weeks|Chart| +|COVID19 - Confirmed cases by sex in the last 14 weeks|Chart| +|COVID19 - Closed and active cases at subnational last months|Chart| +|COVID19 - Case recovery and fatality rates last 12 weeks|Chart| +|COVID19 - Active and Closed Cases last 12 weeks|Chart| + +## References { #references } + +- Installation guidance: [https://www.dhis2.org/covid-19](covid-19-aggregate-installation.html) +- WHO Interim guidelines on nCoV-19 surveillance & case definitions (last updated March 20, 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions>]() +- WHO COVID-19 surveillance data dictionary (v6) +[https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98\_2](https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2) +- WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) + [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +- WHO Coronavirus situation reports + [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports>]() +- Global surveillance of COVID-19: WHO process for reporting aggregated data +[https://www.who.int/publications/i/item/aggregated-weekly-reporting-form](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md new file mode 100644 index 00000000..9597ff7e --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-installation.md" +revision_date: '2022-11-07' +tags: +- Implement +--- + +# Aggregate Package Installation Guide { #c19-agg-installation } + +## Overview { #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. + +The configuration packages for DHIS2 consists of a metadata file in [JSON](https://en.wikipedia.org/wiki/JSON) format which can be imported into a DHIS2 instance, as well as accompanying documentation. The package provides pre-defined, standard content according to WHO recommendations. This document is concerned with complete packages that include configurations of data collection (data sets, data elements, validation rules) as well as analysis and dashboards (chart, map and pivot table favourites). This is intended for use where there is no data collection configured in DHIS2, or if replacing/revising existing content to align with WHO recommendations. + +The configuration packages consists of 4 main components: + +* data sets with data elements; +* a set of indicators; +* analytical outputs (pivot table, data visualizer and GIS favourites); and +* a set of dashboards. + +These components are all linked, i.e. the indicators are based on the included data elements, the analytical outputs are based on the included indicators, and the dashboards are made up of the included analytical outputs. + +## Installation { #installation } + +Installation of the module consists of two steps: + +1. [Preparing](#preparing-the-metadata-file) a metadata file with DHIS2 metadata. +2. [Importing](#importing-a-metadata-file-into-dhis2) a metadata file into DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Performing](#examples-of-other-modifications) package-specific modifications. + +This section deals with the first two steps of preparing and importing the metadata file into DHIS2, whilst the configuration procedure is discussed in the next section. It is recommended to first read through both sections before starting the installation and configuration process in DHIS2. In addition to the general steps described here, some of the configuration packages have annexes to the installation guide, describing particular issues. These are listed in the appropriate section [here](https://dhis2.org/who-package-downloads). + +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. + +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 } + +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): + +* data elements (including categories) +* data sets +* indicators +* indicator types +* dashboards +* data visualizer, pivot table and GIS favourites + +The full list of objects included in the module (for which the administrator needs authorities to manage) can be found in the Metadata reference document for the particular configuration package. + +In cases where modifications to the .json metadata file of the configuration package are necessary [(see below)](https://who.dhis2.org/documentation/installation_guide_complete.html#preparing-the_metadata-file), a [text editor](https://en.wikipedia.org/wiki/Text_editor) is needed - these modifications should not be done with a word processor such as Microsoft Word. + +The configuration package can be installed in DHIS2 through the DHIS2 Health App, or manually through a .json file with DHIS2 metadata using the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. The procedure described in the rest of this section applies to the process of manually importing metadata. + +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 } + +**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. + +## Default data dimension { #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| +|--|--|--| +|Category|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Category option|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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 } + +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| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Percentage|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. + +**Note 2**: An alternative approach to re-using the existing indicator types is to import those included in the configuration package, and removing the existing ones that overlap. This would require all indicators that use these existing indicator types to be updated to the newly imported indicator types, before the indicator types can be deleted. + +## Importing a metadata file into DHIS2 { #importing-a-metadata-file-into-dhis2 } + +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 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 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 } + +**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 } + +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 } + +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. + +#### 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. +* 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. + +## Additional Configuration { #additional-configuration } + +Once all metadata has been successfully imported, the module should be useable with only a few minor additional adjustments. In addition, depending entirely on the DHIS2 instance the module has been imported into, some additional configuration and modification might be necessary or advantageous. This section will first go through the necessary configuration steps, then mention some of the other types of modifications or configuration that might be relevant. + +## Required configuration { #required-configuration } + +Before the configuration packages can be used for data collection, there are two steps that are required. + +* Assign the data set(s) to appropriate organisation units +* Share the data set(s) with appropriate user groups +* Add your user(s) to the appropriate user groups + +The data sets should be assigned to the organisation units (facilities) which are expected to report on that particular data set. + +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 } + +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: + +* Data elements/Data element groups +* Indicators/Indicator groups +* Data Sets +* Dashboards + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +We recommend the following access + +|Object|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| +|_Indicators/Indicator group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| +|_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 } + +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. + +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 data element categories exists these duplications can be hidden to end users through category option group sets, or certain metadata objects can be hidden for groups of users through sharing. + +It is recommended not to remove or replace the indicators included in configuration packages even though the same indicator already exists, so that the analytical outputs (which as based exclusively on indicators) can be kept. This will allow training material based on the configuration packages to be re-used. + +## Examples of other modifications { #examples-of-other-modifications } + +In addition to the required configuration, there are a number of other modifications and configuration that might be relevant, depending on the specific situation. It will not be possible to provide guidance and recommendations that cover all the different scenarios, but a brief discussion of some common problems are presented here. + +### Translations { #translations } + +Additional translations might have to be added, if other languages than those included are needed. + +### Adding additional variables { #adding-additional-variables } + +The configuration packages includes key recommended data elements and indicators. However, it might in some cases be necessary to add additional variables to address country-specific information needs. These could be added to the included data sets. + +### Updating layout of reporting forms { #updating-layout-of-reporting-forms } + +To facilitate the work of personnel doing data entry in DHIS2, it is sometimes desirable to add a custom data entry form that match the format of paper forms used at the primary level. + +## Maintenance { #maintenance } + +No particular maintenance is required for the configuration packages, since they are made up of standard DHIS2 metadata objects. However, before upgrading to new versions of DHIS2, it is important to test all functionality of the system in general on a staging/test server before upgrading any production instances of the system. + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md new file mode 100644 index 00000000..4322bbef --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/overview.md" +revision_date: '2023-03-07' +tags: +- Implement +--- + +# COVID-19 Aggregate Surveillance { #covid-19-aggregate-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-agg-release-note) + +## Design { #design } + +- [Version 2.0.0](#c19-agg-design) + +## Installation { #installation } + +- [Installation Guide](#c19-agg-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 2.0.0](https://packages.dhis2.org/en/C19_AGG/2.0.0/DHIS2.39/C19_AGG_COMPLETE_2.0.0_DHIS2.39.xlsx) + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md new file mode 100644 index 00000000..f10d3d99 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md @@ -0,0 +1,26 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implement +--- + +# Release Note { #c19-agg-release-note } + +To see additional details of the metadata objects mentioned below, refer to the metadata reference documentation of the relevant version. + +## 2.0.0 { #200 } + +* The changes leading to this version were based on the revised [WHO Global surveillance of COVID-19 Weekly Aggregate Report ](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) +* The major were made on the age disaggregations with 5 year age bands used for <20 years and 60+ years spanning upto 80+years. +* Unknown age and Unknown sex were also introduced in the disaggregations to cater data that cannot be categorized with the options provided. +* Data elements for cases and deaths among health workers (Confirmed + Probable), tests with PCR assay, deaths amongst probable cases and health workers were introduced in this version. +* Data elements for logistics and cases by transmission classifications were removed. +* Considering these changes, all the core metadata objects; data elements, indicators, dashboard and its items, dataSets, indicator groups and data elements groups were newly created. +* This version now has only one dataSet designed for weekly reporting unlike in the previous version that had 2 dataSets reported weekly and daily basis. +* All the core metadata objects have been coded in support for international standard for aggregate data exchange (ADX). + +## 1.0.0 { #100 } + +Initial release of COVID-19 Aggregate Surveillance package + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md new file mode 100644 index 00000000..c74c3f11 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -0,0 +1,291 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-design.md" +revision_date: '2022-09-13' +tags: +- Implement +--- + +# COVID-19 Case Surveillance & Contact Tracing Design { #c19-cs-design } + +Demo: [https://demos.dhis2.org/covid-19](https://demos.dhis2.org/covid-19) + +## Purpose { #purpose } + +The COVID-19 Surveillance System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +**This design has been updated to reflect new aggregate reporting requirements from the [WHO interim surveillance guidelines updated March 20, 2020][1]**. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| Type of Surveillance Package | Case Surveillance (Tracker) | Surveillance (Event) | Surveillance (Aggregate) | +|---|---|---|---| +| ***Description*** | Enrols a case and tracks over time through laboratory confirmation & case outcome | Captures critical case details in line-listing format | Enables daily or weekly reporting of key aggregate data points | +| ***Pros*** | Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case | More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity | Low complexity, easy to implement, most manageable when cases numbers are high | +| ***Cons*** | Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation | Does not support case-follow up or other decentralized workflows | Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) | + +**This document covers only the design of the surveillance tracker program package**; separate system design documents are available for DHIS2 event and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing case disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 surveillance package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions][2], updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +The DHIS2 case surveillance tracker metadata was based on the **[WHO COVID-19 case reporting template][3]** and the mapping of data dictionaries can be accessed at: [DHIS2 CBS tracker metadata WHO line-list data dictionary][4]. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles][5] and a common [naming convention][6]. + +The COVID-19 digital data package supports surveillance workflows and automated analysis for key components of routine and active surveillance. This package includes a Case Surveillance Tracker and Contact registration & follow-up tracker, which are installed together in the same metadata package. The tracker programs are optimized to be installed with other COVID-19 surveillance packages, including the Points of Entry Screening Tracker and aggregate daily surveillance dataset. + +1. **[Use Case 1: COVID-19 Case surveillance tracker][7]**: enrols & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. Metadata for the case surveillance tracker is aligned with the WHO [COVID-19 surveillance data dictionary][8] + + > n.b. The COVID-19 case tracker can be implemented either as a ‘standalone’ program for COVID-19 specific disease surveillance as described here; or, COVID-19 concepts can be integrated into an existing case surveillance tracker program if one already exists in-country. Please refer to installation and implementation guidance for more details. + +1. **[Use Case 2: Contact registration & follow-up][9]**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. + +Digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [Google Play store][10]. + +## Use Case 1: COVID-19 Case surveillance tracker { #use-case-1-covid-19-case-surveillance-tracker } + +The COVID-19 case surveillance tracker can be adapted and used by countries to supplement existing national disease surveillance programs. The basic case surveillance program is designed to: + +1. Enroll suspected\* COVID-19 cases (*generally appearing at a health facility, but may be enrolled at other places*) +2. Capture key information about the suspected case including demographics and exposures, such as symptoms, contact with a previously confirmed case & travel history +3. Generate lab requests +4. Record laboratory diagnosis +5. Record contacts of a confirmed\*\* or probable\*\*\* case for follow-up +6. Record case outcome +7. Facilitate case notification and national/regional/global case reporting +8. Generate dashboards and analytics tools for monitoring disease trends and planning response efforts + +The design of the case tracker program assumes that [WHO case definitions][1] are followed in the use case; its use can be adapted to local case definitions as needed. The WHO case definitions were updated on March 20, 2020 and noted below. + +> \* Suspected case: A) a patient with acute respiratory illness (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness of breath), AND with no other aetiology that fully explains the clinical presentation AND a history of travel to or residence in a country/area or territory reporting local transmission of COVID-19 disease during the 14 days prior to symptom onset; **OR**, B) A patient with any acute respiratory illness AND having been in contact with a confirmed or probable COVID-19 case (see definition of contact) in the last 14 days prior to onset of symptoms; **OR,** C) A patient with severe acute respiratory infection (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness breath) AND requiring hospitalization AND with no other aetiology that fully explains the clinical presentation. +> +>\*\* Probable case: A) a suspect case for whom testing for COVID-19 is inconclusive (inconclusive being the result of the test reported by the laboratory) **OR,** B) a suspect case for whom testing could not be performed for any reason. +> +>\*\*\* Confirmed case: A person with laboratory confirmation of COVID-19 infection, irrespective of clinical signs and symptoms. + +### Intended Users { #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 +* 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 + +### Workflow: COVID-19 Case Surveillance Tracker { #workflow-covid-19-case-surveillance-tracker } + +![Workflow of the DHIS2 COVID-19 Case Surveillance Tracker](resources/images/sdd-tracker-v3-case1-workflow.png) + +### Structure: COVID-19 Case Surveillance Tracker Program { #structure-covid-19-case-surveillance-tracker-program } + +![Structure of the COVID-19 Case Surveillance Tracker Program](resources/images/sdd-tracker-v3-case1-structure-v2.png) + +#### Program Description: COVID-19 Case Testing, Diagnosis & Outcome { #program-description-covid-19-case-testing-diagnosis-outcome } + +| Stage | Description | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is the case, which is represented by a Tracked Entity Type of ‘person.’ The *Enrollment date* is the date of registration of the case. The Related programs is *COVID-19 Contact registration & follow-up*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *Age*, *First Name*, *Surname*, *Sex*, *Case phone number*, *First Name (parent or care)*, *Surname (parent or carer)*, *Home Address*, *Workplace/school physical address*, *Country of Residence*, *Facility contact number*| +| **Stage 1: Clinical Examination and Exposures** | This stage records a suspected case’s clinical symptoms and exposures including: *Symptoms*, *Pregnancy and underlying conditions*, *Hospitalisation and Isolation*, *Exposures in 14 days prior to symptoms*, *Travel history*, *Contact with confirmed case*. After examination, you can record if the case has been hospitalised or isolated, and information surrounding this. | +| **Stage 2: Lab Request [repeatable]** | The lab request records the reason for testing and other information that a lab needs to process a sample and test it for COVID19. The information provided here can help lab personnel prioritize lab tests when resources are limited. The person entering this data could be the same person who registered the suspected case and recorded the patient’s clinical exam and exposures; or may be other personnel charged with making lab requests. | +| **Stage 3: Lab Results [repeatable]** | The Lab Results stage records the type and results from laboratory testing. It can be done directly at the lab or as secondary data entry. This stage is repeatable as samples for a given case may be tested multiple times (i.e. in the case of an inconclusive laboratory results, a new lab test can be conducted and results recorded). | +| **Stage 4: Health Outcome** | The health outcome records the final outcome of the case: (recovered, not recovered, dead or unknown) including date of discharge or death as applicable. | + +#### Enrollment Stage { #enrollment-stage } + +![Enrollment](resources/images/sdd-tracker-v3-case1-enrollment.png) + +#### Program Stage 1 - Clinical Examination & Diagnosis { #program-stage-1-clinical-examination-diagnosis } + +##### Section 1 - Clinical Signs and symptoms { #section-1-clinical-signs-and-symptoms } + +Selecting “yes” to the Data Element ‘Any signs or symptoms?’ reveals the rest of the options. + +![Section 1](resources/images/sdd-tracker-v3-case1-stage1-section1.png) + +##### Section 2 - Pregnancy Details { #section-2-pregnancy-details } + +This section is hidden unless gender is selected as ‘Female.’ + +![Section 2](resources/images/sdd-tracker-v3-case1-stage1-section2.png) + +##### Section 3 - Underlying Conditions/Comorbidity { #section-3-underlying-conditionscomorbidity } + +The details of this section are hidden unless “Any underlying conditions” is marked as “Yes”. + +![Section 3](resources/images/sdd-tracker-v3-case1-stage1-section3.png) + +##### Section 4 - Hospitalisation { #section-4-hospitalisation } + +The details of this section is hidden unless “Hospitalised” is marked as “Yes”. + +![Section 4](resources/images/sdd-tracker-v3-case1-stage1-section4.png) + +##### Section 5 - Exposure Risk { #section-5-exposure-risk } + +This section is used to record exposures + + 1. The fields ***country, city and facility*** are hidden by program rules if the case is not a health care worker; + 2. The fields for contact IDs are hidden by program rules if the case has not had contact with a confirmed case in 14 days. + +A suspected case’s exposure to a *previously confirmed* case is distinct from prospective contact tracing in Program Stage 5. + +![Section 5](resources/images/sdd-tracker-v3-case1-stage1-section5.png) + +##### Section 6 - Travel History { #section-6-travel-history } + +![Section 6](resources/images/sdd-tracker-v3-case1-stage1-section6.png) + +#### Program Stage 2: Lab Request { #program-stage-2-lab-request } + +![Stage 2](resources/images/sdd-tracker-v3-case1-stage2.png) + +#### Stage 3: Lab Results { #stage-3-lab-results } + +![Stage 3](resources/images/sdd-tracker-v3-case1-stage3.png) + +#### Stage 4: Health Outcomes { #stage-4-health-outcomes } + +![Stage 4](resources/images/sdd-tracker-v3-case1-stage4.png) + +### Program Rules: COVID19 Case Surveillance Tracker { #program-rules-covid19-case-surveillance-tracker } + +The following program rules have been configured. If a country has an existing case surveillance program and wishes to incorporate elements of the COVID-19 case tracker into their existing program, special attention must be paid to the configuration of program rules. + +| Program Rule Name | Program Rule Description | +|---|---| +| Assign Enrollment Date | This assigns the enrollment date if there is no onset date available to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators. | +| Assign Onset Date| This assigns the onset date to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators.| +| Calculate and assign patient age in years | Calculate and assign patient age in years based on DOB | +| Display patient age in years + days | Display patient age in years + days | +| Hide Date of Death | Hide the Date of Death unless Death is the health outcome | +| Hide Date of Discharge | Hide Date of Discharge if no outcome or if the outcome is death | +| Hide Measured Temperature field | Hide Measured Temperature field until Fever is selected | +| Hide confirmed case ID's if no contact with other confirmed cases| Hides any contact ID's if the case has not been in any contact with other confirmed cases | +| Hide health care worker details if not a health worker | Hide health care worker details if not a health worker | +| Hide health outcome explanation if health outcome is not other | Hide health outcome explanation if health outcome is not other | +| Hide hospitalisation details if hospitalisation is no or unknown | Hide hospitalisation details if hospitalisation is no or unknown | +| Hide isolation date if case is not in isolation | Hide isolation date if case is not in isolation | +| Hide pregnancy details for a female if not pregnant | Hide pregnancy details for a female if not pregnant | +| Hide pregnancy details section if sex is male | Hide pregnancy details section if sex is male | +| Hide reason for testing explanation if an option is selected | Hide reason for testing explanation if an option is selected | +| Hide travel history details if no travel 14 days prior to symptom onset | Hide travel history details if no travel 14 days prior to symptom onset | +| Hide underlying conditions if case does not have any | Hide underlying conditions if case does not have any | +| Show warning if the event date is after the enrollment date | Show warning on completion of an event if the event date is before the enrollment date | + +You can read more about program rules here: [https://docs.dhis2.org/master/en/user/html/configure\_program\_rule.html][11] + +### Program Indicators { #program-indicators } + +From the data captured in the COVID-19 case surveillance program, we can calculate at least the following indicators including those recommended by the WHO for daily and weekly aggregate reporting and present them in a dashboard: + +| Indicator name | Description | +|---|---| +| COVID-19 - Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU) | *Cases treated with mechanical ventilation or ECMO or admitted in intensive care unit (ICU)* | +| COVID-19 Contacts | *Counts the number of relationships (‘has been in contact with’) created that are linked to the case TEI* | +| COVID-19 - Deaths (all suspected cases) | *COVID-19 related deaths (deaths recorded among all suspected cases)* | +| COVID-19 - Deaths (confirmed cases) | *COVID-19 related deaths (deaths recorded among confirmed cases)* | +| COVID-19 - Deaths (probable cases) | *COVID-19 related deaths (deaths recorded among all probable cases)* | +| COVID-19 - Confirmed Hospitalised Cases | *Number of confirmed cases that were admitted into hospital* | +| COVID-19 - Imported Cases | *Cases where likely source of infection is recorded as another country or imported from another country.* | +| COVID-19 - Laboratory confirmed cases | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by report date* | +| COVID-19 - Laboratory confirmed cases - by onset of symptoms | *Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is* "Positive"*); displayed by date of onset of symptoms* | +| COVID-19 - Laboratory tested cases | *Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)* | +| COVID-19 - Local transmission cases | *Number of suspected cases where transmission is local (no travel in last 14 days* | +| COVID-19 - Probable cases | *Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date* | +| COVID-19 - Probable cases - by onset of symptoms | *Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms* | +| COVID-19 - Recovered confirmed cases | *Number of laboratory confirmed cases with outcome recovered*| +| COVID-19 - Suspected cases | *Total number of cases suspected with COVID-19, by report date* | +| COVID-19 - Suspected cases - by onset of symptoms | *Total number of cases suspected with COVID-19, by date of onset of symptoms* | +| COVID-19 - Suspected cases without a positive test result | *Total number of suspected cases without a positive lab result* | +| COVID-19 Total number of laboratory tests conducted | *Total number of lab tests conducted (count of tests, not cases)* | +| COVID-19 Total number of positive tests | *Total number of lab tests returned with positive results (count of tests, not cases* | +| COVID-19 Deaths by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Confirmed cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | +| COVID-19 Suspected cases by sex and age group | ***Male**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+ | **Female**: 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+* | + +## Use Case 2: COVID-19 Contact registration & follow-up { #use-case-2-covid-19-contact-registration-follow-up } + +This program can be used in addition to the case surveillance tracker to facilitate the registration and follow-up of contacts of a confirmed case. In this scenario, it is assumed that if any contacts of a confirmed case meet criteria for suspected case and are referred for testing, the case will be enrolled into the COVID-19 Case Surveillance tracker program. + +The Contact registration & follow-up program registers each contact of a case (as described in COVID-19 Case Surveillance Use Case) as a new Tracked Entity Instance (person) and links them to the case in the COVID-19 Case Surveillance Program via a ‘relationship.’ It has a simple repeatable follow-up stage where symptoms and any follow-up undertaken can be registered. + +### Workflow: Contact registration & follow-up { #workflow-contact-registration-follow-up } + +![Worflow of the Contact registration & follow-up](resources/images/sdd-tracker-v3-case2-workflow.png) + +### Program Description: Contact registration & follow-up { #program-description-contact-registration-follow-up } + +| Stage | Description | +|---|---| +| **Enrollment details & Attributes** | The Tracked Entity is represented by a Tracked Entity Type of ‘person.’ The Related program is *COVID-19 Case based surveillance*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *First Name*, *Surname*, *Date of birth*, *Age*, *Sex*, *Phone number (local)*, *Home Address*, *Country of Residence* | +| **Stage 1: Follow-Up [non-repeatable]** | This stage is meant to record information related to contact tracing follow up, given that a contact has already been identified. It is divided into two sections: *1. Relation with case*, *2. Exposure Assessment* | +| **Stage 2: Symptoms[repeatable]** | This stage is intended to record symptoms of the case. Follow-up to check on the symptoms of a contact can be repeated until the follow-up period is complete (for example, after 14 days or according to national guidelines). When follow-up period is complete, the enrollment can be ‘completed.’ *1. Symptoms*| + +Contacts are added to the index case using the relationships menu in the case surveillance program: + +![Profile](resources/images/sdd-tracker-v3-case2-profile.png) + +Once you select “Add” from the relationships box, you are able to select the relationship and program and either select an existing person or enroll a new contact using the enrollment stage that appears. This will enroll the contact into the contact registration and follow-up +program. + +![Add a relationship](resources/images/sdd-tracker-v3-case2-add-relationship.png) + +Contacts that are added will then be listed on the case’s tracker dashboard in the relationship +widget + +![Relationships widget](resources/images/sdd-tracker-v3-case2-relationships-widget.png) + +You may also enroll them separately into the program. Once enrolled, you will be able to find them for the follow-up as required. + +#### Enrollment { #enrollment } + +![iEnrollment in the use case 2](resources/images/sdd-tracker-v3-case2-enrollment-case2.png) + +#### Program Stage 1 : Follow - Up { #program-stage-1-follow-up } + +![Case 2 Stage 1](resources/images/sdd-tracker-v3-case2-stage1.png) + +#### Program Stage 2 : Symptoms { #program-stage-2-symptoms } + +![Case 2 Stage 2](resources/images/sdd-tracker-v3-case2-stage2.png) + +### Program Indicators: Contact Registration { #program-indicators-contact-registration } + +| Program Indicator Name | Description | +|---|---| +| COVID-19 travelers screened | Total number of travelers screened and enrolled in screening program from POE | +| COVID-19 travelers cleared at POE | Number of travelers cleared after POE screening (no follow-up required) | +| COVID-19 travelers with symptoms at POE | Number of travelers presenting with symptoms during POE screening | +| COVID-19 travelers cleared after 14 days monitoring | Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period) | +| COVID-19 travelers referred to health facility | Number of travelers that were referred to a health facility at any time during 14 day followup | +| COVID-19 travelers enrolled for 14 day follow-up | Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening | +| COVID-19 currently under follow-up | Number of travelers that have not been cleared or referred to a health facility | +| COVID-19 travelers developed symptoms during follow-up | Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening) | + +## References { #references } + +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form [https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + +[1]: https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf +[2]: https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions +[3]: https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx +[4]: https://drive.google.com/open?id=1vigXHkP7L2hJ2lrZpdf9u4csQtppMH16 +[5]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html +[6]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html +[7]: #use-case-1-covid-19-case-surveillance-tracker +[8]: https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2 +[9]: #use-case-2-covid-19-Contact-registration-follow-up +[10]: https://play.google.com/store/apps/details?id=com.dhis2&hl=en +[11]: https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md new file mode 100644 index 00000000..b3913fde --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-installation.md" +revision_date: '2022-09-13' +tags: +- Implement +--- + +# COVID-19 Surveillance - Installation Guide { #c19-cs-installation } + +## Overview { #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: + +1. COVID-19 Case-based Surveillance Tracker program & COVID-19 Contact Registration & Follow-Up program +2. Points of Entry Screening Tracker program + +You will have to follow the instructions in full for each separate package that you install. + +## Installation { #installation } + +Installation of the module consists of several steps: + +1. [Preparing](#preparing-the-metadata-file) the metadata file with DHIS2 metadata. +2. [Importing](#importing-metadata) the metadata file into DHIS2. +3. [Configuring](#additional-configuration) the imported metadata. +4. [Adapting](#adapting-the-tracker-program) the program after being imported + +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 } + +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 } + +**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. + +### Default data dimension { #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| +|--|--|--| +|Category|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|Category option|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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 } + +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| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|Percentage|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| +|--|--|--| +|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| + +## Importing metadata { #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 } + +***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 } + +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 } + +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. + +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. + +#### 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: + +* 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. + +## 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. + +### Sharing { #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 +* Program +* Program stages +* Dashboards + +There are three user groups that come with the package: + +* COVID19 access +* COVID19 admin +* COVID 19 data capture + +By default the following is assigned to these user groups + +|Object|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| +|_*Program*_|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| +|_*Dashboards*_|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: + +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. + +### Organisation Units { #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 } + +**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. + +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). + +## 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. +* 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. + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md new file mode 100644 index 00000000..60263176 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md @@ -0,0 +1,29 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/overview.md" +revision_date: '2022-11-22' +tags: +- Implement +--- + +# COVID-19 Case Surveillance { #covid-19-case-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-cs-release-note) + +## Design { #design } + +- [Version 1.0.2](#c19-cs-design) + +## Installation { #installation } + +- [Installation Guide](#c19-cs-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 1.0.2](https://packages.dhis2.org/en/C19_CS/1.0.2/C19_CS_COMPLETE_1.0.2_DHIS2.37.xlsx) + +## Training Material { #training-material } + +- [COVID-19 Training Material](https://dhis2.org/covid-training-material) + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..27d88ae2 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implement +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Overview { #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/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md new file mode 100644 index 00000000..699918f3 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -0,0 +1,136 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/c19_poe-design.md" +revision_date: '2022-07-05' +tags: +- Implement +--- + +# COVID-19 Points of Entry Tracker Design { #c19-poe-design } + +Demo: [https://covid19.dhis2.org/](https://covid19.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Points of Entry (POE) Screening System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +The Points of Entry Screening Tracker is inspired by the pioneering design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health. In January 2020, the Sri Lanka MOH implemented screening measures at ports of entry like airports to identify travelers who may have been exposed to nCoV-19. DHIS2 tracker was to enroll travelers entering Sri Lanka who had visited countries impacted by COVID-19. DHIS2 tracker enabled follow-up with travelers at field level for 14 days to ensure no symptoms developed. If symptoms developed, travelers would be referred to a health facility for clinical examination and testing. The POE tracker can be used in combination with other COVID-19 digital data packages that include case surveillance and contact tracing. + +The World Health Organisation (WHO) has published [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). Points of entry (POE) include international airports, seaports and land crossings. POE measures include 1) detection of ill travellers; 2) interview of ill travellers for COVID-19; 3) reporting of alerts of ill travellers with suspected COVID-19 infection and 4) isolation, initial case management and referral of ill travellers with suspected COVID-19 infection. These guidelines should be consulted, in addition to national protocols for points of entry. + +## System Design Summary { #system-design-summary } + +### Use Case { #use-case } + +The POE tracker program use case was designed to support the registration of travelers 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. For this use case, it is assumed that a traveler may be 1) screened and cleared immediately with no follow-up needed; 2) screened and followed up for 14 days [with or without isolation measures] to ensure no symptoms develop; or 3) screened and referred for testing and/or initial case management. The current design proposes that a traveler meeting the country’s definition of a suspected case would be enrolled into the complementary DHIS2 COVID-19 Case-Based Surveillance (CBS) Tracker. For example, a traveler enrolled in this program who later meets the definition of a suspected case during follow-up (i.e. an asymptomatic traveler from a country with known transmission is registered at the POE and later develops symptoms) is enrolled as a suspected case into the COVID-19 CBS program to capture all clinical details, exposures and follow the case through laboratory diagnosis and case outcome. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +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). + +### Intended users { #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. +* National and local health authorities: monitor and analyse data through dashboards and analytics tools to conduct risk assessments and plan response measures. + +### Workflow { #workflow } + +The Points of Entry program workflow is based on the following scenario + +![Scenario](resources/images/POE_image01.png "Scenario") + +In this design, it is assumed a traveler would complete their enrollment in the POE under the following scenarios: + +1. Traveler is marked as ‘cleared’ during initial screening or after 14 day follow-up +2. Traveler is referred to health facility at any point during follow-up + +**A traveler that is referred to a health facility is expected to be enrolled in the COVID-19 Case-based Surveillance Tracker as a suspected case** (according to national guidelines). Details about a suspected case including clinical exam, exposures, laboratory results and case outcome would be recorded in the CBS program. + +### Structure: Points of Entry Screening Tracker Program { #structure-points-of-entry-screening-tracker-program } + +![Structure](resources/images/POE_image02.png "Structure") + +#### Consideration for Organisation Units & Geography { #consideration-for-organisation-units-geography } + +This program design assumes that Points of Entry such as airports, seaports or land crossings will be created as organisation units included in the OU hierarchy. The program would be assigned to the POE org units. Primary analysis is based on the enrolling Org Unit (the port of entry). + +Additional geographical components are also captured as other dimensions: + +1. TEI coordinates: It is possible to capture TEI coordinates when registering the traveler as TEI. These can be displayed in the maps app. Local protocols may choose what coordinates to enter, for example the TEI’s local residence where he/she may be self-quarantined for 14 days. +2. Event coordinates: for screening and follow-up stages, coordinates can be captured on the event and displayed in a map. For example, the user may capture a traveler’s location each time they are followed up (i.e. in the case of tourists or others not in home quarantine). + +#### Program Description { #program-description } + +|Stage|Description| +|--|--| +|**Registration**|The Tracked Entity is the traveler, which is represented by the Tracked Entity Type of ‘person.’ The TEI is configured to collect a geographic ‘point’ during registration. These can be analyzed in a map.| +|**Enrollment details**|Enrollment date
The first Program Stage is configured to appear on the Registration page so that a user does not need to click through to add the first event.| +|**Attributes**|Attributes include basic personal information and unique case identifiers
- Passport number
- Local Case ID
- Age
- First Name
- Surname
- Country of residence
- Sex
- Date of birth
- Local address
- Home address
- Telephone (local)
- Telephone (foreign)
- Emergency contact
- Emergency contact phone
- Email| +|**Stage 1**
**Screening at POE**
**(non-repeatable)**|This stage records:
- Traveler details (countries visited, flight number, date of departure, etc)
- Examination: recorded temperature
- Symptoms: this list includes symptoms typically checked for both COVID-19 symptoms and symptoms of other potential notifiable diseases
- Case clearance

If the traveler is marked as ‘cleared’, no further follow up is required; the enrollment may be closed. If the traveler requires follow-up, an event can be scheduled for follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 2:**
**Follow-up (within 14 days)**
**(repeatable)**|Data is entered at this stage if any interim follow-up is performed before the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment may be closed if no further monitoring & follow-up is planned in this program.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 3:**
**Follow-up (after 14 days)**
**(non-repeatable)**|Data is entered at this stage at the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)
- Case clearance

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment should be closed at the completion of 14 day follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization. + +![Enrollment](resources/images/POE_image03.png "Enrollment") + +![Program Stage 1 - Screening at POE](resources/images/POE_image04.png "Program Stage 1 - Screening at POE") + +![Program Stage 1 - Screening at POE](resources/images/POE_image05.png "Program Stage 1 - Screening at POE") + +![Program Stage 2: Follow-up (within 14 days)](resources/images/POE_image06.png "Program Stage 2: Follow-up (within 14 days)") + +![Program Stage 3: Follow up (after 14 days)](resources/images/POE_image07.png "Program Stage 3: Follow up (after 14 days)") + +#### How to refer the TEI to another Organisation Unit { #how-to-refer-the-tei-to-another-organisation-unit } + +Primary analysis is completed on the enrolling organisation unit (the port of entry). Referral facility is captured as a Data Element (type: Organisation Unit) in order to display travelers by referral to health facility in the analytics apps (i.e. Event Report). In some use cases, it may be desirable to refer the TEI (the traveler) to another Org Unit for follow-up. + +A TEI can be ‘referred’ to another org unit such as a health facility for one event or permanently. In this case, health facility user must be able to search TEIs enrolled in the relevant Points of Entry org units. For example, if after screening a traveler at the POE, the traveler may be “referred” to a district health office near the traveler’s local address for follow-up by district health staff. After completing the data entry for Stage 1 (screening), the user would refer the TEI to a District Health Center. Read more about referrals in tracker in [DHIS2 User Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/tracking-individual-level-data/tracker-capture.html). + +![alt_text](resources/images/POE_image08.png "image_tooltip") + +### Program Relationships { #program-relationships } + +This program has the relationshipType ‘Has been in contact with’. Users can create a relationship between TEIs enrolled in the POE program and TEIs in other COVID-19 tracker programs (Case-based Surveillance, Contact Registration & Follow-up). The relationship can be added at any point in the program stages during data entry. + +### Program Rules { #program-rules } + +The following program rules have been configured. + +|Program Rule Name|Program Rule Description| +|--|--| +|Calculate and assign patient age in years|Calculate and assign patient age in years| +|Hide countries if not visited|Hide countries if not visited| +|Hide Follow-Up Stages|Hide Follow-Up Stages if the case is cleared at the port of entry| +|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)| +|Hide symptoms if no symptoms present (Follow Up within 14 days)|Hide symptoms if no symptoms present (Follow Up within 14 days)| +|Hide symptoms if no symptoms present (PoE)|Hide symptoms if no symptoms present (PoE)| + +You can read more about program rules here: +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +||| +|--|--| +|COVID-19 travelers screened|Total number of travelers screened and enrolled in screening program from POE| +|COVID-19 travelers cleared at POE|Number of travelers cleared after POE screening (no follow-up required)| +|COVID-19 travelers with symptoms at POE|Number of travelers presenting with symptoms during POE screening| +|COVID-19 travelers cleared after 14 days monitoring|Number of travelers that are cleared after 14 day follow up (no onset of symptoms during 14 day period)| +|COVID-19 travelers referred to health facility|Number of travelers that were referred to a health facility at any time during 14 day followup| +|COVID-19 travelers enrolled for 14 day follow-up|Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| +|COVID-19 currently under follow-up|Number of travelers that have not been cleared or referred to a health facility| +|COVID-19 travelers developed symptoms during follow-up|Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)| +|COVID-19 % travelers developed symptoms during 14-day follow-up|Numerator: Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)
Denominator: Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| + +Users can also generate an Event Report to see: + +1. Travelers by nationality and/or originating country +2. Referrals to health facility + +## References { #references } + +* DHIS2 COVID-19 [Tracker Package Installation Guide](covid-19-tracker-installation.html) +* World Health Organisation (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) (interim guidance, published 19 March 2020) + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md new file mode 100644 index 00000000..d1bde3b7 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Points of Entry { #covid-19-points-of-entry } + +## Design { #design } + +[Version 1.0.2](#c19-poe-design) + +## Installation { #installation } + +[Installation Guide](#c19-poe-installation) + +## Release Note { #release-note } + +[Release Note](#c19-poe-release-note) + +## Metadata Reference { #metadata-reference } + +[Version 1.0.2](https://packages.dhis2.org/en/C19_POE/1.0.2/C19_POE_COMPLETE_1.0.2_DHIS2.37.xlsx) + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md new file mode 100644 index 00000000..38e326d0 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -0,0 +1,164 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/c19_evt-design.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Surveillance Line-list Design { #c19-evt-design } + +Demo: [https://covid.dhis2.org](https://covid.dhis2.org/demo) + +## Purpose { #purpose } + +The COVID-19 Surveillance Event Program System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## Background { #background } + +The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +|Type of Surveillance Package|Case-based Surveillance (Tracker)|Surveillance (Event)|Surveillance (Aggregate)| +|--|--|--|--| +|_Description_|Enrolls a case and tracks over time through laboratory confirmation & case outcome|Captures critical case details in line-listing format|Enables daily or weekly reporting of key aggregate data points| +|_Pros_|Highly granular data and multiple time dimensions for analysis, can support decentralized workflow, all events linked to the case|More granular than aggregate and can capture key time dimensions (i.e. report date vs onset of symptoms); reduced burden of data entry compared to tracker and little complexity|Low complexity, easy to implement, most manageable when cases numbers are high| +|_Cons_|Burden of data entry may be overwhelming when number of cases reach threshold; complexity of implementation|Does not support case-follow up or other decentralized workflows|Less granularity for detailed analysis (i.e. analysis only based on case reporting date, limited disaggregation) + +**This document covers only the design of the surveillance event program package**; separate system design documents are available for DHIS2 Tracker and aggregate packages. + +WHO is “urging all countries to prepare for the potential arrival of COVID-19 by readying emergency response systems; increasing capacity to detect and care for patients; ensuring hospitals have the space, supplies and necessary personnel; and developing life-saving medical interventions.” + +The objectives of COVID-19 surveillance are: + +1. to monitor trends of the disease where human to human transmission occurs; +2. rapidly detect new cases in countries where the virus is not circulating; +3. provide epidemiological information to conduct risk assessments at the national, regional and global level; and +4. provide epidemiological information to guide preparedness and response measures. + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## System Design Summary { #system-design-summary } + +This package is designed as a DHIS2 [Event Program](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#about_event_program). **The Event Program is not designed to capture all data variables contained in the [WHO case reporting template](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx)**. To capture a complete set of WHO case reporting variables, please refer to the DHIS2 COVID-19 Case-based Surveillance Tracker. Rather, the event program is a simplified program that captures a subset of minimum critical data points to facilitate high data quality when the number of caseloads or burden of reporting exceeds capacity for successfully completing the full line-list for suspected COVID-19 cases. For implementers who wish to capture the complete WHO line-listing, please refer to the COVID-19 Case-based Surveillance Tracker Package. + +The COVID-19 Surveillance Event Program data package includes: + +1. Event program and data elements case reporting +2. Core indicators +3. Dashboard + +### Use Case: Simplified line-listing of COVID-19 cases { #use-case-simplified-line-listing-of-covid-19-cases } + +As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The event package is designed to capture the most critical data points in a line-list and analytical capacities for surveillance and response. The event package is designed as a standalone program. However, countries may use the event package in combination with other packages (i.e. event reports and daily aggregate reporting); or, they may shift from tracker to event to aggregate as caseloads and reporting burden increases. **_Countries should plan carefully how they intend to implement these packages in combination, including reporting flows, transitioning from one data model to another, and how to maintain historical data for analysis if transitioning between data models. _** + +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. + +#### Intended users { #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 + +#### Workflow { #workflow } + +Unlike the tracker program, there are limitations to decentralization of the data reporting workflow in an Event program. The most significant limitation is that the Case Outcome (recovery or death) is often not known until days or weeks after the case is reported. The current program design allows for the following workflow options: + +1. Event is created when a suspected case is reported. All known data is entered, but the event is not completed. A user can select an ‘Active Event’ from a working list based on User filters and criteria. When missing data becomes available (i.e. the case outcome), the user can enter the remaining data fields and complete the event. Cases can be identified in the event list by the Case ID data element. See the image below as an example which can be accessed within the Capture App: +![Capture App](resources/images/EVENT_image1.png "Capture App") + +2. Event is created. All case related data is entered retrospectively, including the Outcome. Event is completed. _The limitation is this approach is timeliness of the data reporting, as new suspected cases might not be captured until their outcome which is often too late for decision making._ + +### Program Structure { #program-structure } + +The program is called ‘COVID-19 Cases (events)’ + +|Section|Description| +|--|--| +|Date of report|Event Date
_Countries may re-name the event date to apply to their protocols._| +|Section 1
**Basic Information**|Records basic demographic data.
_Countries may add data elements as desired._
- **Patient ID**
Can be used to filter events in working lists, eg. Active events
- **Sex**
- **Age**| +|Section 2
Case Details|Records information about the case including symptoms, severity, testing, etc.
- **Symptoms**
Options: Yes / No
Specifies whether a case has any symptoms at time of notification

- **Date of symptoms onset**
Only appears if symptoms are present;
Date of symptoms onset, if available, will replace “Date of Report” in data analytics and reporting.

- **Case Severity (at time of notification)**
Options: Mild / Moderate / Severe / Critical
- **Laboratory tested?**
Options: Yes / No/ Unknown
Specifies whether a case has been laboratory tested for COVID-19

- **Test Result**
Only appears if the case was laboratory tested
Options: Inconclusive / Positive / Negative / Unknown
The program is designed to capture only the final test result. Results for each individual test (if available) and the total number of tests performed are not captured.
- **Case Classification**
Options: Suspected case / Probable case / Laboratory confirmed case
Automatically assigned values
The values are assigned by Program rules in accordance with WHO case definitions
This feature can be useful in filtering active cases in the working lists.| +|Section 3
**Exposures**|- **Has the case traveled in the 14 days prior to symptoms onset?**
Options: Yes / No / Unknown
Specifies travel history of the case.

- **Likely Infection Source**
Options: Imported case* / Local Transmission / Exposure unknown
* Imported case option appears only if the case traveled in the 14 days prior to symptoms onset

- **Specify local source**
Only appears if Likely Infection Source is Local Transmission
Options: Community (workplace, public transport, etc.) / Household / Healthcare Facility / Close Contact with Other Infected Individual / Exposure Unknown

- **Case Type**
Options: New index case / Linked to existing cluster / Unknown
Specifies whether the case is connected to an existing cluster or is a new index case| +|Section 4
**Treatment**|- **Hospitalised**
Options: Yes / No

- **Did the case receive care in an intensive care unit (ICU)?**
Only appears if the case is hospitalised
Options: Yes / No| +|Section 5
**Contacts**|- **Total number of contacts followed for this case**
Records number of contacts| +|Section 6
**Outcome**|- **Health outcome**
Options: Recovered / Death| +|Section 7
**Assigned Date of onset of symptoms**|- **Calculated onset date (for Indicators)**
This section is used only to calculate indicators based on report date vs. date of onset of symptoms]
This automatically assigned date is used in program indicators. Initially, it is the report date. If the date of onset of symptoms is available, the date is replaced by the date of onset of symptoms.| +|**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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Currently, only users assigned to the COVID19 data capture group will have access to capture data in the program. Please refer to the installation guidance for more instructions. + +### Program Rules { #program-rules } + +The following program rules have been configured for the program: + +|Program Rule Name|Program Rule Description| +|--|--| +|Assign Empty Value to Class Classification|Automation: Assign Empty Value to Class Classification| +|Assign Event Date|Automation: Assign Event date if to onset date if no Onset date is available| +|Assign 'Laboratory Confirmed Case' to Case Classification|Automation: Assign 'Laboratory Confirmed Case' to Case Classification| +|Assign Onset Date|Automation: Assign Symptoms Onset Date if available| +|Assign 'Probable Case' to Case Classification|Automation: Assign 'Probable Case' to Case Classification| +|Assign 'Suspected Case' to Case Classification|Automation: Assign Suspected Case' to Case Classification| +|Hide Case Classification Field|Hide Case Classification Field until Lab Test question is answered| +|Hide ICU field|Hide ICU field unless Hospitalised| +|Hide 'Imported Case'|Hide 'Imported Case' if not traveled| +|Hide Onset of Symptoms Date|Hide Onset of Symptoms Date if no symptoms| +|Hide Outcome Options|Hide irrelevant Outcome Options| +|Hide 'Specify Local Infection Source'|Hide 'Specify Local Infection Source' unless Local Transmission is selected| +|Hide Test Result Field|Hide Test Result Field until Lab Test question is answered with yes| +|Hide Test Result Options|Hide Irrelevant Test Result Options| +|Hide Unknown Options|Hide Irrelevant Unknown Options| + +You can read more about program rules here: + +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +From the data captured in the COVID-19 line-listing program, we can calculate the following indicators, including those recommended by the WHO for daily and weekly reporting, present them in a dashboard. All COVID-19 program indicators based on the event program are assigned to the Program Indicator Group ‘COVID-19 Events.’ + +||| +|--|--| +|COVID-19 - Cases admitted in intensive care unit (ICU)|COVID-19 Cases admitted in intensive care unit (ICU)| +|COVID-19 - Cases exposed through healthcare facility|Cases where infection is suspected to have occurred in a health care setting| +|COVID-19 - Cases infected by community transmission|Cases where infection is suspected to have occurred through community spread| +|COVID-19 - Cases infected by household transmission|Cases where infection is suspected to have occurred within the household| +|COVID-19 - Cases infected by local transmission|Cases where infection is suspected to have occurred locally, not in another country| +|COVID-19 - Cases infected through other contact with other infected individual|Cases where infection is suspected to have occurred through other close contact with an infected individual (excluding those listed: household, known cluster, HCF)| +|COVID-19 - Cases linked to known cluster|Cases where infection is suspected to have occurred by linkage to a known cluster of cases| +|COVID-19 - Cases with unknown exposure|Cases where source of infection or exposure is unknown| +|COVID-19 - Deaths|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 - Confirmed Hospitalised Cases|Number of confirmed cases that were admitted into hospital| +|COVID-19 - Imported Cases|Cases where likely source of infection is recorded as another country or imported from another country.| +|COVID-19 - Laboratory confirmed cases|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by report date| +|COVID-19 - Laboratory confirmed cases - by onset of symptoms|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by date of onset of symptoms| +|COVID-19 - Laboratory tested cases|Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)| +|COVID-19 - Probable cases|Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date| +|COVID-19 - Probable cases - by onset of symptoms|Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms| +|COVID-19 - Recovered cases|Number of cases that are recovered (By date of onset of symptoms)| +|COVID-19 - Suspected cases|Total number of cases suspected with COVID-19, by report date| +|COVID-19 - Suspected cases - by onset of symptoms|Total number of cases suspected with COVID-19, by date of onset of symptoms| +|COVID-19 - Suspected cases not tested|Total number of suspected cases without a lab result| +|COVID-19 Event - case fatality rate|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19 Deaths by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Confirmed cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19 Suspected cases by sex and age group|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| + +## References { #references } + +* [COVID-19 Surveillance, Response & Vaccine Delivery Toolkit](https://dhis2.org/covid-19) +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form +[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +* WHO Considerations in the investigation of cases and clusters of COVID-19 (last updated 13 March 2020) [https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19](https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19) +* WHO Coronavirus situation reports +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md new file mode 100644 index 00000000..243bc1c0 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md @@ -0,0 +1,13 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Surveillance Events { #covid-19-surveillance-events } + +## Design { #design } + +[Version 0.3.2](#c19-evt-design) + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md new file mode 100644 index 00000000..2d1d5128 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md @@ -0,0 +1,22 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_surveillance-digital_data_package-2022.md" +revision_date: '2023-09-01' +tags: +- Implement +--- + +# COVID-19 Surveillance { #covid-19-surveillance } + +DHIS2 released a digital metadata package to accelerate case detection, situation reporting, active surveillance and response for COVID-19. The design is inspired by the Ministry of Health Sri Lanka’s pioneering use of DHIS2 tracker for COVID-19 case detection and draws on years of collaboration with the World Health Organisation (WHO) to develop information system standards for case-based disease surveillance. The COVID-19 digital data package includes standard metadata aligned with the WHO’s [technical guidance on COVID-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and implementation guidance to enable rapid deployment in countries. + +The design of these modules can be adapted, modified and reused for new and emerging infectious disease threats to strengthen health emergency preparedness and response systems in countries. + +## COVID-19 Surveillance Modules { #covid-19-surveillance-modules } + +DHIS2 supports surveillance workflows and automated analysis for key components of routine and active surveillance: + +* **COVID-19 Case Surveillance tracker**: enrolls & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. +* **Contact Registration & Follow-up tracker**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. +* **Ports of Entry Screening & Follow-up tracker**: enrols travellers who have visited high-risk locations at Ports of Entry for 14-day monitoring and follow-up. +* **COVID-19 Aggregate Situation Reports**: an aggregate reporting dataset that captures minimum necessary data points for daily or weekly reporting and includes key information for generating situation reports. + diff --git a/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..27d88ae2 --- /dev/null +++ b/projects/docs-full-site/si/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implement +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### Overview { #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/zh/.cache_timestamp b/projects/docs-full-site/zh/.cache_timestamp index 33186499..afa852fa 100644 --- a/projects/docs-full-site/zh/.cache_timestamp +++ b/projects/docs-full-site/zh/.cache_timestamp @@ -1 +1 @@ -2024-10-17T21:23:06Z \ No newline at end of file +2024-10-19T21:23:43Z \ 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 3ccf3605..523347c0 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 分析工具 { #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 152c10d0..4e1dad77 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 应用 { #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 304ddeb0..2c77c1be 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 审核 { #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 8a946631..44f12b80 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 数据审批 { #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 4e9166bb..c300274f 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 数据 { #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 a34b502e..9ec3b7cc 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 数据存储 { #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 80248b6b..1496e821 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 数据验证 { #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 bcc1a924..76270f2e 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 电子邮件 { #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 ebcde38d..9cc399c8 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 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 4a3dcfa9..cd93f40f 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 总览 { #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 1884a9b6..a04c75a9 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 保养 { #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 c3a2633b..24f2f40f 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 讯息传递 { #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 1108605e..840c7a4c 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 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 7ae37701..a070868c 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 元数据 { #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 ea105a66..1b239e7d 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 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 89090ceb..c502e570 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 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 38987e32..0d633fe8 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 排程 { #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 42bd8a5d..6bcbd7b2 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 设置和配置 { #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 5de85a0d..0f510d3c 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 分享中 { #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 dc821047..914b673c 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 短信 { #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 0dd44311..1682f295 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 同步化 { #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 81b95cef..30897c24 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 追踪器 { #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 9c3f9a76..a16506a8 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 用户数 { #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 d08eee7c..f12e9ab9 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: -- DHIS core version 2.38 - Develop +- DHIS core version 2.38 --- # 可视化 { #visualizations } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md index 8c614414..46097541 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/analytics.md" revision_date: '2023-12-13' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 分析工具 { #analytics } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md index 4052abbc..66ca1de0 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md index f69c0968..486f792b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 数据审批 { #data-approval } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md index 092866d7..5a928f60 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 数据 { #data } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md index 999bd3e9..a04988a8 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/data-validation.md" revision_date: '2022-06-21' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 数据验证 { #data-validation } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md index d611d164..cd99a463 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # I18n { #i18n } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md index 9ae429db..c4452bdf 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/overview.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 总览 { #webapi } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md index b7bedfec..c7ce5888 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 讯息传递 { #messaging } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md index 0d2e1db9..6d98f30f 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md index 1d153b60..026d4ca3 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/metadata.md" revision_date: '2023-08-03' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 元数据 { #metadata } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md index 337f6a8a..92973761 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/scheduling.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 排程 { #webapi_scheduling } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md index c4a55181..ff027485 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 分享中 { #sharing } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md index 89bd725c..7c7e539c 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 短信 { #sms } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md index 8634785c..b8169891 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 同步化 { #webapi_synchronization } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md index 359417c2..6ee8c4b6 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-239__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.39/src/developer/web-api/visualizations.md" revision_date: '2022-09-13' tags: -- DHIS core version 2.39 - Develop +- DHIS core version 2.39 --- # 可视化 { #visualizations } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md index cafafa7f..53d0f083 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__analytics-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # 分析工具 { #analytics } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md index 3bf3f9b8..7911957e 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__apps-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # 应用 { #apps } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md index 414cf80e..be313a58 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__audit-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/audit.md" revision_date: '2022-08-19' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md index 45a274cf..752cf3c7 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-approval-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-approval.md" revision_date: '2022-02-21' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 数据审批 { #data-approval } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md index 708ff30e..9a3f31cf 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-entry-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-entry.md" revision_date: '2022-10-13' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 数据输入{ #data-entry } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md index eb9e3ee0..fa6e6c44 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data-exchange.md" revision_date: '2023-09-27' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md index 5422b124..23a41ea4 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 数据 { #data } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md index 5c698cf1..d602fcc8 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__data-store-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # 数据存储 { #data-store } 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 a6128aae..13cb220c 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 6a5e9357..694fc736 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__event-hooks-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md index db39a74d..7ce31634 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md index 9e2945c4..c0abf141 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/i18n.md" revision_date: '2022-10-23' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # I18n { #i18n } 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 615f5efe..9b6bbbfc 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__maintenance-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md index e9943f32..1fb01a54 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__maintenance-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # 保养 { #maintenance } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md index b929faa7..767dd3b3 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 讯息传递 { #messaging } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md index cf414547..52d5f351 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata-gist.md" revision_date: '2022-05-12' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md index ed0c68e1..5f1e0416 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/metadata.md" revision_date: '2024-04-26' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 元数据 { #metadata } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md index 40d4192d..67e8b165 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__org-unit-profile-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # Organisation unit profile { #org_unit_profile } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md index 77dd6941..5c8cf6f0 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__route-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # Route { #route } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md index 8b0f8e5f..c6f542c8 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__scheduling-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # 排程 { #webapi_scheduling } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md index 04cde275..aaf41ad1 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__settings-and-configuration-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # 设置和配置 { #settings-and-configuration } 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 b671704c..50c49c15 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__sms-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md index d0ae83a4..80a30d2a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__sms-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # 短信 { #sms } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md index f0b85988..a61d72d5 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/synchronization.md" revision_date: '2022-05-05' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 同步化 { #webapi_synchronization } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md index d5030ff4..d56d723e 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-240__tracker-deprecated-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.40 --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } 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 9a6cba25..7fd12104 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 @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.40/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS core version 2.40 - Develop +- DHIS core version 2.40 --- # 追踪器 { #tracker } 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 5a9d4cb0..7b674ac3 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 9db863ab..c8cff68c 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__analytics-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md index d8f7f646..807d631b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__analytics-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/analytics.md" revision_date: '2024-05-02' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 分析工具 { #analytics } 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 4f26f52b..a65ccbc3 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: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 应用 { #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 0e0c4b88..e355be2a 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: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 审核 { #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 9e7d8fe7..cee8e7f3 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: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 数据审批 { #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 e932dd3e..fa7b458a 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: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md index 59874270..f039f8b9 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-exchange-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-exchange.md" revision_date: '2024-06-26' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md index 290a9ae2..03a275c0 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data.md" revision_date: '2024-05-23' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 数据 { #data } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md index d301e015..e3d46b79 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-store-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-store.md" revision_date: '2024-02-20' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 数据存储 { #data-store } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md index e7f72da0..ae7cdf04 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__data-validation-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/data-validation.md" revision_date: '2024-03-13' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 数据验证 { #data-validation } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md index 1b8057d6..b0bed0bd 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__email-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/email.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 电子邮件 { #email } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md index edc30b59..f80da134 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__event-hooks-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/event-hooks.md" revision_date: '2023-05-03' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md index f8da9639..e9092102 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__i18n-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/i18n.md" revision_date: '2024-05-15' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # I18n { #i18n } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md index 5f400ce0..3e06d65a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__introduction-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/overview.md" revision_date: '2023-02-09' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 总览 { #webapi } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md index 33427694..10c7353b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__maintenance-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/maintenance.md" revision_date: '2024-03-13' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 保养 { #maintenance } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md index 56a1fb82..af04df65 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__messaging-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/messaging.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 讯息传递 { #messaging } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md index 0378eecc..438ec5be 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-gist-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata-gist.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Metadata Gist API { #gist_api } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md index c31f7a58..34b5e9b4 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/metadata.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 元数据 { #metadata } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md index 20308eb0..73823f24 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__org-unit-profile-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/organisation-unit-profile.md" revision_date: '2021-11-19' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Organisation unit profile { #org_unit_profile } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md index d0aa3ae8..7f068a18 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__query-alias-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/query-alias.md" revision_date: '2024-05-15' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md index f5de6e11..0c195bbf 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__route-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/route.md" revision_date: '2024-09-24' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Route { #route } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md index 84297c15..68671c04 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__scheduling-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/scheduling.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 排程 { #webapi_scheduling } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md index 57c2259e..f27208cf 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__settings-and-configuration-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/settings-and-configuration.md" revision_date: '2024-05-21' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 设置和配置 { #settings-and-configuration } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md index 78877a0b..ecfbb73d 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sharing-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/sharing.md" revision_date: '2022-02-04' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 分享中 { #sharing } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md index 892c33d0..52b5ca88 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__sms-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/sms.md" revision_date: '2021-06-14' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 短信 { #sms } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md index 5eb85c4e..7843a87e 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__synchronization-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/synchronization.md" revision_date: '2024-02-09' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 同步化 { #webapi_synchronization } 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 5cae72a0..549ac66a 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: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # Tracker (deprecated APIs) { #tracker-deprecated-apis } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md index 41a7580a..1cc2daf0 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__tracker-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/tracker.md" revision_date: '2024-07-02' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 追踪器 { #tracker } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md index 077757d0..0abaaf43 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__users-md +++ b/projects/docs-full-site/zh/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 - Develop +- DHIS core version 2.41 --- # 用户数 { #users } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md index 83320fc9..0302f3e5 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-241__visualizations-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/2.41/src/developer/web-api/visualizations.md" revision_date: '2024-03-05' tags: -- DHIS core version 2.41 - Develop +- DHIS core version 2.41 --- # 可视化 { #visualizations } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md index 0e5f0a5f..b617d307 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__analytics-md +++ b/projects/docs-full-site/zh/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-07-26' tags: -- Develop - DHIS核心 主版 +- Develop --- # 分析工具 { #analytics } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md index f1978bfd..ceff095d 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__apps-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 应用 { #apps } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md index 2a207aff..ad5ffce2 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md index 30bb9508..8f48a48b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-approval-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 数据审批 { #data-approval } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md index 54f27adc..a2fb6f7b 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-entry-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # Data entry { #data-entry } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md index dac79f07..ef98f465 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-exchange-md +++ b/projects/docs-full-site/zh/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-09-18' tags: -- Develop - DHIS核心 主版 +- Develop --- # Data exchange { #data-exchange } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md index fd0a169a..7e62951e 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 数据 { #data } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md index ebf0ec7e..2a9888f9 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-store-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 数据存储 { #data-store } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md index 2abd525c..71a70371 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__data-validation-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 数据验证 { #data-validation } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md index 0308dfb4..6e1ba9ae 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__event-hooks-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # Event Hooks { #event-hooks } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md index 31044a92..7618939e 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__i18n-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 国际化 { #i18n } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md index 9084edac..dedf9644 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__introduction-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 总览 { #webapi } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md index 71ede553..146dcffa 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__maintenance-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 保养 { #maintenance } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md index 4d78484b..82e244e7 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-gist-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 元数据要点 API { #gist_api } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md index 453a30b6..9a58ea71 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md +++ b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__metadata-md @@ -2,8 +2,8 @@ edit_url: "https://github.com/dhis2/dhis2-docs/blob/master/src/developer/web-api/metadata.md" revision_date: '2024-07-29' tags: -- Develop - DHIS核心 主版 +- Develop --- # Metadata { #webapi_metadata } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md index 3417e861..dec9fa24 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__query-alias-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # Query Alias { #query-alias } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md index f6948bed..9c2e8a99 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__route-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # Route { #route } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md index 841bfef1..5c58b41c 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__scheduling-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 排程 { #webapi_scheduling } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md index af5346bc..0d9ed82a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__settings-and-configuration-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 设置和配置 { #settings-and-configuration } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md index b83bc523..c96c08bb 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sharing-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 分享中 { #sharing } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md index 9ce3ce57..000262d9 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__sms-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 短信 { #sms } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md index 27035e03..f436878a 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__synchronization-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 同步化 { #webapi_synchronization } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md index eef934c4..4fc1ce60 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__users-md +++ b/projects/docs-full-site/zh/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-09-13' tags: -- Develop - DHIS核心 主版 +- Develop --- # 用户数 { #users } diff --git a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md b/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md index 430410f1..ee0ee309 100644 --- a/projects/docs-full-site/zh/DEVELOP__USING-THE-API__DHIS-CORE-VERSION-MASTER__visualizations-md +++ b/projects/docs-full-site/zh/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: -- Develop - DHIS核心 主版 +- Develop --- # 可视化 { #visualizations } diff --git a/projects/docs-full-site/zh/IMPLEMENT__DATA-USE__data-visualization-md b/projects/docs-full-site/zh/IMPLEMENT__DATA-USE__data-visualization-md index 817d33fa..266d359e 100644 --- a/projects/docs-full-site/zh/IMPLEMENT__DATA-USE__data-visualization-md +++ b/projects/docs-full-site/zh/IMPLEMENT__DATA-USE__data-visualization-md @@ -1,6 +1,6 @@ --- edit_url: "https://github.com/dhis2/dhis2-docs-implementation/blob/master/content/data-use/data-visualization.md" -revision_date: '2024-10-17' +revision_date: '2024-10-18' tags: - Implement --- @@ -27,9 +27,9 @@ Understanding these categories is essential to selecting the correct chart type - **Ordinal** - Categories with a meaningful order (e.g., disease status). These categories have a logical sequence. - For example, disease severity might be classified as mild, moderate, and severe, which has an inherent order. -> **Note**: +> **Note** > ->**Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. +> **Binary variables are a subtype of dichotomous variables**, assigned either a 0 or a 1 (e.g., Male (0) and Female (1)). They represent two categories, usually for simple yes/no, true/false conditions. Dichotomous variables can be discrete or continuous, similar to regular discrete and continuous variables. ![Variable categories](resources/images/dataviz_001.png) @@ -46,7 +46,7 @@ What’s the best way to choose the right visualization for the data at hand? [F Another Chart Chooser is mapped in the [Extreme Presentation Method](https://extremepresentation.com/). -![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.png) +![Chart Chooser by Extreme Presentation Method](resources/images/dataviz_002.jpg) The summary below is based on the visualizations available in the core DHIS2 Data Visualizer App. @@ -93,9 +93,9 @@ The summary below is based on the visualizations available in the core DHIS2 Dat ### Specific Visualization Styles { #specific-visualization-styles } ->**Note** +> **Note** > ->**Data speaks louder than words!** +> **Data speaks louder than words!** In data visualization, choosing the right type of chart or graph is crucial for effectively communicating your data. Each visualization style has its strengths and is best suited for specific types of data and analytical purposes. This chapter explores a variety of visualization styles, detailing their applications and best practices. Whether you're looking to show trends over time, compare quantities, highlight correlations, or illustrate parts of a whole, selecting the appropriate visualization method will enhance clarity and insight. By understanding the nuances of each style, you can ensure that your data tells a compelling and accurate story. @@ -103,9 +103,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Correlation { #correlation } ->**Note** +> **Caution** > ->Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. +> Correlation assumes a causal relationship unless specified otherwise. Be cautious in interpreting correlation as causation. - **Scatterplot**: Shows the relationship between two continuous variables, each having its axis. Each point represents an observation's values on the two variables. It's useful for identifying trends, clusters, and outliers. For example, a scatterplot can display the relationship between the number of immunization campaigns conducted in various districts and the resulting immunization coverage rate. @@ -118,9 +118,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Ranking { #ranking } ->**Note** +> **Note** > ->Emphasizes the item's position in an ordered list rather than the absolute value. +> Emphasizes the item's position in an ordered list rather than the absolute value. - **Ordered bars/columns**: Shows ranks of values more easily when sorted. This visualization helps to quickly see the highest and lowest values. An ordered bar column chart can be used to display the number of TB cases in each district, sorted in descending order to highlight the districts with the highest burden. @@ -132,9 +132,9 @@ In data visualization, choosing the right type of chart or graph is crucial for #### Change Over Time { #change-over-time } ->**Note** +> **Note** > ->Keep gaps between columns small to highlight data shape. +> Keep gaps between columns small to highlight data shape. Use markers for irregular data points. - **Column**: Emphasizes changing trends. Columns are used to show discrete data points over time. For example, monthly case figures can be shown as a column chart. @@ -152,9 +152,9 @@ Use markers for irregular data points. #### Magnitude { #magnitude } ->**Note** +> **Note** > ->Small gaps highlight data shape. Best for a single series of data. +> Small gaps highlight data shape. Best for a single series of data. - **Column/Paired column/bar**: Compare sizes, usually numbers rather than rates or percentages. For instance, HIV case figures for different regions can be compared using a bar chart. In this case, it is appropriate to keep the distance between the columns as they represent separate entities rather than variables through time. @@ -168,9 +168,9 @@ Use markers for irregular data points. #### Part-to-Whole { #part-to-whole } ->**Note** +> **Tip** > ->Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** +> Remember colorblind-friendly designs. You can change the style of the graph in the data visualizer app by accessing **Options>Style>Color Set** ![Imrpove the visualization choosing the most suitable colour set](resources/images/dataviz_022.png) @@ -206,9 +206,9 @@ Stacked columns or bar charts **should be avoided when** a detailed comparison o - **Choropleth**: Standard for rates on maps. Uses varying shades of a colour to represent data values for different regions. For example, population density by region can be shown using a choropleth map. ->**Note** +> **Note** > ->**Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. +> **Attention to normalization** - you technically cannot compare raw numbers between regions of distinct size or population. Always use rates. ![Map showing the percentage of PTB-BC cases in a region](resources/images/dataviz_013.png) @@ -287,9 +287,9 @@ A visualization should always have: ![Contextualized graph](resources/images/dataviz_024.png) ->**Note**: +> **Caution** > ->Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. +> Due to the interactive nature of DHIS2 dashboards, including specific timeframes (e.g., "last 12 months") in the titles can lead to confusion if filters are applied, such as changing the period to the last 6 months. This discrepancy between the title and the visualized data can cause misunderstandings. Therefore, it is recommended to avoid specifying the timeframe in the title to maintain clarity and accuracy. #### Pie Chart { #pie-chart } diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md new file mode 100644 index 00000000..80c7611f --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__design-md @@ -0,0 +1,206 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-design.md" +revision_date: '2023-03-31' +tags: +- Implement +--- + +# COVID-19 Surveillance - Aggregate System Design Guide { #c19-agg-design } + +## 目的 { #purpose } + +The COVID-19 Surveillance Aggregate System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## 背景 { #background } + +This aggregate design has been updated to reflect new aggregate reporting requirements from the [Global surveillance of COVID-19: WHO process for reporting aggregated data](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form), last updated on August 7, 2020. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| **Type of Surveillance Package** | **Case-based Surveillance (Tracker)** | **Case surveillance line-listing (Event)** | **Case surveillance (Aggregate)** | +| --- | --- | --- | --- | +| **描述** | Enrolls a case and tracks over time through laboratory confirmation & case outcome | 以行列表格式捕获关键案例详细信息 | Enables weekly reporting of key aggregate data points | +| **Pros** | 高度精细的数据和用于分析的多个时间维度，可以支持分散的工作流，所有事件都与案例相关 | 比汇总更精细，可以捕获关键的时间维度（即报告日期与症状发作）；与跟踪器相比，减少了数据输入的负担，并且几乎没有复杂性 | 低复杂度，易于实施，在案件数量高时最易于管理 | +| **Cons** | 当案件数达到阈值时，数据输入的负担可能会不堪重负；实施的复杂性 | 不支持个案跟进或其他分散式工作流程 | 进行详细分析的粒度较小（即仅根据病例报告日期进行分析，分类范围有限）| + +**This document covers only the design of the aggregate package**; separate system design documents are available for DHIS2 Tracker and Line-listing (event-based) packages. As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The aggregate package is designed to meet the most critical reporting requirements and analytical capacities for surveillance and response. + +COVID-19监视的目标是： + +1. 监测发生人际传播的疾病趋势； +2. 在病毒未传播的国家中迅速发现新病例； +3. 提供流行病学信息以在国家，区域和全球范围内进行风险评估；和 +4. 提供流行病学信息以指导准备和应对措施。 + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated August 7, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## 系统设计摘要 { #system-design-summary } + +In the development of this configuration package, an effort has been made to follow UiO's [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +The aggregate COVID-19 surveillance package includes + +1. Weekly aggregate data set and data elements for key COVID-19 surveillance reporting +2. Categories for data disaggregation +3. Core indicators +4. Dashboard and its items + +The dataset captures a minimum number of data points that meet the current WHO weekly reporting requirements; and generate a core set of indicators and dashboards for national and sub-national decision-makers to rapidly analyze and respond to disease trends. + +| **名称** | **Periodicity** | **Purpose** | +| --- | --- | --- | +| Aggregate Weekly Surveillance | Weekly| Reporting of key COVID-19 surveillance data including cases, tests and deaths. | + +It is recommended that the weekly dataset is assigned to Organisation Units at the lowest level of the health system feasible for reporting data, such as health facilities. + +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). + +### 目标用户 { #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. +- 国家和地方卫生当局：通过仪表板和分析工具监测和分析疾病监测数据，以进行风险评估和计划应对措施；生成区域和全球报告的报告 + +## 数据集 { #datasets } + +This dataset is intended to capture weekly data needed for rapid response to disease transmission. If the burden of reporting becomes too great or when it is no longer considered an emergency situation in the country, the data set may be changed to monthly according to MOH policies. + +### Daily Surveillance Data Elements { #daily-surveillance-data-elements } + +The following lists the data elements and disaggregation (category combinations) included in the data set: + +| **数据元素** | **Category Combinations** | +| --- | --- | +| New Confirmed Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Cases | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Confirmed Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Probable Deaths | Gender (Male/Female/Unknown) and Age (0-4,5-9,10-14,15-19,20-29,30-39,40-49,50-59,60-64,65-69,70-74,75-79,80+,Unknown age) | +| New Hospitalized Cases | 没有 | +| New Discharged Cases | 没有 | +| New Cases Among Health Workers (Confirmed + Probable) | 没有 | +| New Deaths Among Health Workers (Confirmed + Probable) | 没有 | +| Number of Persons Tested for COVID-19 | 没有 | +| Number of persons Tested with PCR Assay | 没有 | +| Transmission Classification | 没有 | + +### Weekly Surveillance Data Entry Form { #weekly-surveillance-data-entry-form } + +- **Section 1: New confirmed and probable Cases** + +Data should be entered for all new confirmed and probable cases reported during the reporting period. Confirmed cases refer to laboratory confirmed cases per WHO guidance; probable cases are defined by WHO as cases where laboratory test result is inconclusive; however countries may apply their own case definitions. The total column is automatically summed during data entry. +![Picture1](resources/images/AGG_Picture1.png) + +- **Section 2: New confirmed and probable deaths** + +Data should be entered for new confirmed and probable deaths reported during the reporting period. The total column is automatically summed during data entry. + +![Picture2](resources/images/AGG_Picture2.png) + +- **Section 3: Health worker infection and death** + +This section captures data for health workers' new confirmed and probable cases including deaths reported during the reporting period. + +![Picture3](resources/images/AGG_Picture3.png) + +- **Section 4: Hospitalisation and discharges** + +This section captures data for new hospitalisation and discharges during the reporting period. + +![Picture4](resources/images/AGG_Picture4.png) + +- **Section 5: Tests conducted** + +This section captures data for tests conducted with additional requirement to report tests conducted using PCR during the reporting period + +![Picture5](resources/images/AGG_Picture5.png) + +- **Section 6: Transmission Classification** + +This section summarizes the major form of transmission classification experienced by the reporting unit. + +![Picture7](resources/images/AGG_Picture6.png) + +### Customizing Data Entry Forms { #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) + +## Data Validation { #data-validation } + +The following data validation rules have been configured. These validation rules do not run in the data entry form itself as it is anticipated that the urgent reporting of data where events occur in different time frames (e.g. one week can see only 3 new cases but 5 deaths). + +| **名称** | **Operator** | **Instruction** | **Left side description** | **Right side description** | +| --- | --- | --- | --- | --- | +| COVID19 - PCR tests \<= tested | less\_than\_or\_equal\_to | Tested with PCR should be less than or equal to total tests conducted | Tested with PCR | Tested conducted | +| COVID19 - New Cases hospitalised \<= All New Cases | less\_than\_or\_equal\_to | New Cases hospitalised should be less than or equal to all new cases | New Cases hospitalised | All New Cases | +| COVID19 - New confirmed deaths \<= New confirmed cases | less\_than\_or\_equal\_to | New confirmed deaths should be less than or equal to New confirmed cases | New confirmed deaths | New confirmed cases | +| COVID19 - Probable deaths \<= New probable cases | less\_than\_or\_equal\_to | Probable deaths should be less than or equal to New probable cases | Probable deaths | New probable cases | +| COVID19 - New deaths among HW (confirmed + probable) \<= All deaths reported | less\_than\_or\_equal\_to | New deaths among HW (confirmed + probable) should be less than or equal to All deaths reported | New deaths among HW (confirmed + probable) | All deaths reported | +| 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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Please refer to the [installation guidance](covid-19-aggregate-installation.html) for more information. + +## 指标 { #indicators } + +From the data captured, we can calculate at least the following indicators, many of which are recommended by the WHO for [weekly reporting](https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf) and present them in a dashboard. All COVID-19 program indicators are assigned to the Indicator Group 'COVID19'. + +| **name** | **description** | +| --- | --- | +| COVID19 - New Confirmed Deaths | Number of new confirmed deaths | +| COVID19 - New Cases Among HW (Confirmed + Probable) | Number of New Cases Among HW (Confirmed + Probable) | +| COVID19 - Proportion of HW amongst reported cases (%) | Proportion of HW amongst reported cases (%) | +| COVID19 - Active cases | Number of of active cases | +| COVID19 - Closed cases | Number of closed cases | +| COVID19 - New Confirmed cases | Number of new Confirmed cases | +| COVID19 - Recovery rate (%) | Recovery rate of confirmed cases | +| COVID19 - Case fatality rate among HW (%) | Case fatality rate among HW | +| COVID19 - New Hospitalized Cases | New Hospitalized Cases | +| COVID19 - Tested | Total number of tests conducted | +| COVID19 - Tested with PCR Assay | Tested with PCR assay | +| COVID19 - Positivity rate (%) | Positivity rate | +| COVID19 - New Probable Cases | Number of new probable cases | +| COVID19 - New Discharged Cases | Number of new discharged cases | +| COVID19 - New Deaths Among HW (Confirmed + Probable) | Number of new deaths among HW (Confirmed + Probable) | +| COVID19 - Proportion of PCR tests (%) | Proportion of PCR tests conducted | +| COVID19 - All cases (Confirmed + Probable) | Number of all cases (Confirmed + Probable) | +| COVID19 - New Probable Deaths | Number of new probable deaths | +| COVID19 - Case fatality rate (%) | Case fatality rate among confirmed cases | + +## 仪表板 { #dashboards } + +Key analytic items have been configured and added onto the dashboard “COVID19 - Aggregate Weekly Surveillance”. These items include; pivot tables, charts and a map designed to provide data visualization for some of the data captured based on the indicators. In the process of adopting this package, users can modify or create additional items as suits their analytical needs and equally make the necessary adjustments to the dashboard. + +| **name**|**type**| +| --- | --- | +|COVID19 - Tested, tests with PCR and positivity rate by subnational level this year |数据透视表| +|COVID19 - HW amongst reported cases this year |Chart| +|COVID19 - Fatality rate amongst HW.|Chart| +|COVID19 - New confirmed cases and deaths in the last 12 weeks|Chart| +|COVID19 - Cumulative tests conducted, cases reported, hospitalised, discharged and deaths|Chart| +|COVID19 - Cumulative confirmed cases by subnational|Map| +|COVID19 - Deaths by age groups last weeks|Chart| +|COVID19 - Confirmed cases by sex in the last 14 weeks|Chart| +|COVID19 - Closed and active cases at subnational last months|Chart| +|COVID19 - Case recovery and fatality rates last 12 weeks|Chart| +|COVID19 - Active and Closed Cases last 12 weeks|Chart| + +## 引用 { #references } + +- Installation guidance: [https://www.dhis2.org/covid-19](covid-19-aggregate-installation.html) +- WHO Interim guidelines on nCoV-19 surveillance & case definitions (last updated March 20, 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions>]() +- WHO COVID-19 surveillance data dictionary (v6) +[https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98\_2](https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2) +- WHO Laboratory testing for 2019 novel coronavirus (2019-nCoV) in suspected human cases (last updated 2 March 2020) + [https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117](https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117) +- WHO Coronavirus situation reports + [https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports>]() +- Global surveillance of COVID-19: WHO process for reporting aggregated data +[https://www.who.int/publications/i/item/aggregated-weekly-reporting-form](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md new file mode 100644 index 00000000..b7149345 --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__installation-md @@ -0,0 +1,194 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/c19_agg-installation.md" +revision_date: '2022-11-07' +tags: +- Implement +--- + +# Aggregate Package Installation Guide { #c19-agg-installation } + +## 总览 { #overview } + +本文档旨在指导管理员完成为DHIS2安装COVID-19标准配置软件包的过程，以进行汇总报告。需要对DHIS2有充分的了解。 + +DHIS2的配置包由[JSON]（https://en.wikipedia.org/wiki/JSON）格式的元数据文件组成，可以将其导入DHIS2实例以及随附的文档。该软件包根据WHO的建议提供了预定义的标准内容。本文档涉及完整的软件包，其中包括数据收集的配置（数据集，数据元素，验证规则）以及分析和仪表板（图表，地图和数据透视表收藏夹）。此功能适用于在DHIS2中未配置任何数据收集的情况，或者用于替换/修订现有内容以符合WHO建议的情况。 + +配置包包含4个主要组件： + +* 具有数据元素的数据集； +* 一套指标； +* 分析输出（数据透视表，数据可视化工具和GIS收藏夹）；和 +* 一组仪表板。 + +这些组件都链接在一起，即指标基于所包含的数据元素，分析输出基于所包含的指标，而仪表板则由所包含的分析输出组成。 + +## 安装 { #installation } + +模块的安装包括两个步骤： + +1. [准备]（＃preparing-the-metadata-file）具有DHIS2元数据的元数据文件。 +2. 将元数据文件[导入]（＃importing-a-metadata-file-to-dhis2）到DHIS2中。 +3. [配置]（＃additional-configuration）导入的元数据。 +4. [执行]（＃examples-of-other-modifications）特定于程序包的修改。 + +This section deals with the first two steps of preparing and importing the metadata file into DHIS2, whilst the configuration procedure is discussed in the next section. It is recommended to first read through both sections before starting the installation and configuration process in DHIS2. In addition to the general steps described here, some of the configuration packages have annexes to the installation guide, describing particular issues. These are listed in the appropriate section [here](https://dhis2.org/who-package-downloads). + +在重复或转移到DHIS2的生产实例之前，应在测试/分阶段环境中测试本文档中概述的过程。 + +多个配置包 + +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 } + +为了安装配置包，需要使用DHIS2中的管理员用户帐户，并具有添加/编辑（公共）元数据对象的权限，包括（但不限于）： + +* 数据元素（包括类别） +* 数据集 +* 指标 +* 指标类型 +* 仪表板 +* 数据可视化器，数据透视表和GIS收藏夹 + +可以在特定配置包的元数据参考文档中找到模块中包含的对象的完整列表（管理员需要管理员对其进行管理）。 + +如果需要修改配置包的.json元数据文件[（请参见下文）]（https://who.dhis2.org/documentation/installation_guide_complete.html#preparing-the_metadata-file），请使用[文本编辑器]（https://en.wikipedia.org/wiki/Text_editor）-这些修改不应使用文字处理程序（例如Microsoft Word）来完成。 + +The configuration package can be installed in DHIS2 through the DHIS2 Health App, or manually through a .json file with DHIS2 metadata using the [Import/Export](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/maintaining-the-system/importexport-app.html) app of DHIS2. The procedure described in the rest of this section applies to the process of manually importing metadata. + +[Configuration]（https://who.dhis2.org/documentation/installation_guide_complete.html#configuration）部分适用于两种方法。 + +## 准备元数据文件 { #preparing-the-metadata-file } + +**注意**：如果要将软件包安装在DHIS2的新实例上，则可以跳过“准备元数据文件”部分，然后立即移至“ [将元数据文件导入DHIS2]（＃importing-将元数据文件放入DHIS2）。” + +尽管并非总是必要，但在将元数据文件导入DHIS2之前对其进行某些修改通常可能是有利的。 + +## 默认数据维度 { #default-data-dimension } + +在早期版本的DHIS2中，默认数据维的UID是自动生成的。因此，尽管所有DHIS2实例都具有默认类别选项，数据元素类别，类别组合和类别选项组合，但这些默认的UID可以不同。 DHIS2的更高版本具有用于默认维度的硬编码UID，并且这些UID在配置包中使用。 + +为避免在导入元数据时发生冲突，建议搜索并替换整个.json文件以查找所有这些默认对象，并将.json文件的UID替换为将导入文件的数据库的UID。表1显示了应替换的UID以及用于标识现有UID的API端点。 + +|目的|用户标识|API endpoint| +|--|--|--| +|类别|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|类别选项|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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 } + +指标类型是另一种可能导致导入冲突的对象，因为在不同的DHIS2数据库中使用了某些名称（例如“百分比”）。由于指标类型仅由其因子以及是否为无分母的简单数字定义，因此它们是明确的，可以通过搜索和替换UID进行替换。这样可以避免潜在的导入冲突，并避免创建重复的指标类型。表2显示了可以替换的UID以及用于标识现有UID的API端点。 + +|目的|用户标识|API endpoint| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|百分比|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| + +**注1 **：通过按照所述替换UID并导入.json文件，相关指标类型的名称（包括所有翻译）将更新为配置包中包含的指标类型。 + +**注2 **：重用现有指标类型的另一种方法是导入配置包中包含的那些，并删除重叠的现有指标。这将要求在删除指标类型之前，将所有使用这些现有指标类型的指标更新为新导入的指标类型。 + +## 将元数据文件导入DHIS2 { #importing-a-metadata-file-into-dhis2 } + +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 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. + +如果“试运行” /“验证”导入正常进行，请尝试导入元数据。如果导入成功并且没有任何错误，则可以继续[配置]（https://who.dhis2.org/documentation/installation_guide_complete.html#configuration）模块。在某些情况下，“空运行”期间不会显示导入冲突或问题，而是在尝试实际导入时出现。在这种情况下，导入摘要将列出需要解决的所有错误。 + +### 处理导入冲突 { #handling-import-conflicts } + +**注意**如果要导入到新的DHIS2实例中，则不必担心导入冲突，因为要导入的数据库中没有与之冲突的内容。按照说明导入元数据，然后继续进行“ [附加配置]（＃additional-configuration）”部分。 + +可能会发生许多不同的冲突，尽管最常见的是配置包中有目标数据库中已经存在名称，简称和/或代码的元数据对象。对于这些问题，有两种替代解决方案，具有不同的优缺点。哪一个更合适将取决于例如发生冲突的对象的类型。 + +#### 备选方案1 { #alternative-1 } + +重命名存在冲突的现有对象。这种方法的优点是无需修改.json文件，因为更改是通过DHIS2的用户界面完成的。这很可能不太容易出错。这也意味着配置包将保留原样，例如在使用基于配置包的培训材料和文档时，这可能是一个优势。 + +#### 备选方案2 { #alternative-2 } + +重命名.json文件中存在冲突的对象。这种方法的优点是现有的DHIS2元数据保持不变。当存在培训材料或文档（例如链接到所讨论对象的数据字典的SOP）时，这可能是一个因素，并且不存在通过修改用户熟悉的元数据而使用户感到困惑的风险。同时，修改.json文件的对象意味着使用相关的文档和培训资料可能会变得更加复杂。 + +请注意，对于备选项1和2，修改可以简单到在名称中添加一个小的前缀/后缀，以最大程度地减少混乱的风险。 + +#### 备选3 { #alternative-3 } + +第三种也是更复杂的方法是修改.json文件以重新使用现有的元数据。例如，在已经存在用于某个概念的指标（例如“ ANC 1覆盖范围”）的情况下，可以将该指标从.json文件中删除，并将其UID的所有引用替换为数据库中已经存在的相应指标。这样做的最大优点（不限于直接导入冲突的情况）是避免在数据库中创建重复的元数据。但是，出于以下几个原因，通常不建议这样做： + +* 它需要有关DHIS2的详细元数据结构的专业知识 +* 该方法不适用于所有类型的对象。特别地，某些类型的对象具有依赖关系，这种依赖关系以这种方式难以解决，例如与分解有关。 +* 与备选方案2一样，这意味着安装结果并不完全符合标准配置，因此，未经修改可能无法使用针对该配置开发的培训材料和文档。 +* 将来对配置包的更新将很复杂。 + +## 附加配置 { #additional-configuration } + +一旦成功导入所有元数据，该模块就应该可以使用，只需进行少量的其他调整即可。另外，完全取决于已将模块导入到的DHIS2实例，可能需要或有利于进行一些其他配置和修改。本节将首先介绍必要的配置步骤，然后提及其他可能相关的其他类型的修改或配置。 + +## 必需的配置 { #required-configuration } + +在将配置包用于数据收集之前，需要执行两个步骤。 + +* 将数据集分配给适当的组织单位 +* 与适当的用户组共享数据集 +* 将您的用户添加到适当的用户组 + +数据集应分配给期望报告该特定数据集的组织单位（机构）。 + +数据集和类别选项也应该与负责为这些数据集进行数据输入的人员的相关用户组共享。 + +### 分享中 { #sharing } + +首先，您将必须使用DHIS2的*共享*功能来配置哪些用户（用户组）应查看与程序关联的元数据和数据，以及谁可以在程序中注册/输入数据。应该为以下配置共享： + +* 数据元素/数据元素组 +* 指标/指标组 +* 数据集 +* 仪表板 + +软件包随附三个用户组： + +* COVID19访问 +* COVID19管理员 +* COVID 19数据捕获 + +我们建议以下访问 + +|目的|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| +|_Indicators/Indicator group_|Metadata : can view
Data: can view|Metadata : can edit and view
Data: can view|Metadata : can view
Data: can view| +|_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 } + +即使成功导入了元数据而没有任何导入冲突，元数据中也可能存在重复项-无论是图表，指标，数据元素还是已经存在的数据元素类别。正如上面有关解决冲突的部分所述，要记住的重要问题是，在DHIS2中更改元数据的决定还需要考虑与现有元数据有不同关联的其他文档和资源。 ，以及通过配置包导入的元数据。因此，解决重复项不仅是“清理数据库”的问题，而且还应确保做到这一点，例如，不破坏与其他系统的集成，使用培训材料的可能性，破坏SOP等。取决于上下文。 + +要记住的重要一件事是DHIS2具有可以隐藏元数据中潜在重复项的某些复杂性的工具。例如，在存在重复的数据元素类别的情况下，可以通过类别选项组集合将这些重复项对最终用户隐藏，或者可以通过共享为用户组隐藏某些元数据对象。 + +即使已经存在相同的指标，也建议不要删除或替换配置包中包含的指标，以便可以保留分析输出（仅基于指标）。这将允许重复使用基于配置包的培训材料。 + +## 其他修改示例 { #examples-of-other-modifications } + +除了所需的配置外，还取决于具体情况，还有许多其他可能涉及的修改和配置。不可能提供涵盖所有不同情况的指导和建议，但此处对一些常见问题进行了简要讨论。 + +### 翻译 { #translations } + +如果需要其他语言，则可能需要添加其他翻译。 + +### 添加其他变量 { #adding-additional-variables } + +配置包包括推荐的关键数据元素和指标。但是，在某些情况下，可能有必要添加其他变量来满足特定国家/地区的信息需求。这些可以添加到包含的数据集中。 + +### 更新报告表格的布局 { #updating-layout-of-reporting-forms } + +为了方便在DHIS2中进行数据输入的人员的工作，有时需要添加自定义数据输入表格，该表格与在初级级别使用的纸质表格的格式相匹配。 + +## 保养 { #maintenance } + +由于配置程序包由标准DHIS2元数据对象组成，因此无需特别维护。但是，在升级到DHIS2的新版本之前，重要的是，通常在升级系统的任何生产实例之前，在登台/测试服务器上测试系统的所有功能。 + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md new file mode 100644 index 00000000..bdd2ca6b --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/overview.md" +revision_date: '2023-03-07' +tags: +- Implement +--- + +# COVID-19 Aggregate Surveillance { #covid-19-aggregate-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-agg-release-note) + +## Design { #design } + +- [Version 2.0.0](#c19-agg-design) + +## 安装 { #installation } + +- [Installation Guide](#c19-agg-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 2.0.0](https://packages.dhis2.org/en/C19_AGG/2.0.0/DHIS2.39/C19_AGG_COMPLETE_2.0.0_DHIS2.39.xlsx) + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md new file mode 100644 index 00000000..f10d3d99 --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-AGGREGATE__release-note-md @@ -0,0 +1,26 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_AGG/blob/master/docs/release_note.md" +revision_date: '2022-11-07' +tags: +- Implement +--- + +# Release Note { #c19-agg-release-note } + +To see additional details of the metadata objects mentioned below, refer to the metadata reference documentation of the relevant version. + +## 2.0.0 { #200 } + +* The changes leading to this version were based on the revised [WHO Global surveillance of COVID-19 Weekly Aggregate Report ](https://www.who.int/publications/i/item/aggregated-weekly-reporting-form) +* The major were made on the age disaggregations with 5 year age bands used for <20 years and 60+ years spanning upto 80+years. +* Unknown age and Unknown sex were also introduced in the disaggregations to cater data that cannot be categorized with the options provided. +* Data elements for cases and deaths among health workers (Confirmed + Probable), tests with PCR assay, deaths amongst probable cases and health workers were introduced in this version. +* Data elements for logistics and cases by transmission classifications were removed. +* Considering these changes, all the core metadata objects; data elements, indicators, dashboard and its items, dataSets, indicator groups and data elements groups were newly created. +* This version now has only one dataSet designed for weekly reporting unlike in the previous version that had 2 dataSets reported weekly and daily basis. +* All the core metadata objects have been coded in support for international standard for aggregate data exchange (ADX). + +## 1.0.0 { #100 } + +Initial release of COVID-19 Aggregate Surveillance package + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md new file mode 100644 index 00000000..a0e9e80f --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__design-md @@ -0,0 +1,291 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-design.md" +revision_date: '2022-09-13' +tags: +- Implement +--- + +# COVID-19 Case Surveillance & Contact Tracing Design { #c19-cs-design } + +Demo: [https://demos.dhis2.org/covid-19](https://demos.dhis2.org/covid-19) + +## 目的 { #purpose } + +COVID-19监视系统设计文档概述了用于在DHIS2中配置COVID-19数字数据包的概念设计。 COVID-19软件包的开发是为了响应各国明确表示的需要，即迅速适应用于管理COVID-19数据的解决方案。本文档供DHIS2实施者在国家和地区级别使用，以支持该软件包的实施和本地化。 COVID-19元数据包可以适应本地需求和国家准则。特别是，在本地化和采用此软件包中包含的程序时，应考虑当地的工作流程和国家准则。 + +## 背景 { #background } + +**This design has been updated to reflect new aggregate reporting requirements from the [WHO interim surveillance guidelines updated March 20, 2020][1]**. The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +| 监控套餐类型 | Case Surveillance (Tracker) | 监视（事件） | 监视（总计） | +|---|---|---|---| +| ***描述*** | 登记病例并通过实验室确认和病例结果跟踪时间 | 以行列表格式捕获关键案例详细信息 | 启用每日或每周的关键汇总数据点报告 | +| ***优点*** | 高度精细的数据和用于分析的多个时间维度，可以支持分散的工作流，所有事件都与案例相关 | 比汇总更精细，可以捕获关键的时间维度（即报告日期与症状发作）；与跟踪器相比，减少了数据输入的负担，并且几乎没有复杂性 | 低复杂度，易于实施，在案件数量高时最易于管理 | +| ***缺点*** | 当案件数达到阈值时，数据输入的负担可能会不堪重负；实施的复杂性 | 不支持个案跟进或其他分散式工作流程 | 进行详细分析的粒度较小（即仅根据病例报告日期进行分析，分类范围有限） | + +**本文件仅涵盖监视跟踪器程序包的设计**； DHIS2事件和聚合程序包可使用单独的系统设计文档。 + +世卫组织“敦促所有国家通过准备应急系统来为COVID-19的潜在到来做准备；提高发现和照顾病人的能力；确保医院有足够的空间，物资和必要的人员；并开发挽救生命的医疗干预措施。” + +COVID-19监视的目标是： + +1. 监测发生人际传播的疾病趋势； +2. 在病毒未传播的国家中迅速发现新病例； +3. 提供流行病学信息以在国家，区域和全球范围内进行风险评估；和 +4. 提供流行病学信息以指导准备和应对措施。 + +The system design builds upon existing case disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 surveillance package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions][2], updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## 系统设计摘要 { #system-design-summary } + +The DHIS2 case surveillance tracker metadata was based on the **[WHO COVID-19 case reporting template][3]** and the mapping of data dictionaries can be accessed at: [DHIS2 CBS tracker metadata WHO line-list data dictionary][4]. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles][5] and a common [naming convention][6]. + +COVID-19数字数据包支持监视工作流程以及对常规监视和主动监视的关键组件的自动分析。该软件包包括案例监视跟踪器和联系人注册与跟踪跟踪器，它们一起安装在同一元数据包中。跟踪器程序经过优化，可与其他COVID-19监视程序包一起安装，包括入口点筛选跟踪器和每日汇总监视数据集。 + +1. **[Use Case 1: COVID-19 Case surveillance tracker][7]**: enrols & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. Metadata for the case surveillance tracker is aligned with the WHO [COVID-19 surveillance data dictionary][8] + + > n.b. The COVID-19 case tracker can be implemented either as a ‘standalone’ program for COVID-19 specific disease surveillance as described here; or, COVID-19 concepts can be integrated into an existing case surveillance tracker program if one already exists in-country. Please refer to installation and implementation guidance for more details. + +1. **[Use Case 2: Contact registration & follow-up][9]**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. + +Digital data packages are optimized for Android data collection with the DHIS2 Capture App, free to download on the [Google Play store][10]. + +## Use Case 1: COVID-19 Case surveillance tracker { #use-case-1-covid-19-case-surveillance-tracker } + +The COVID-19 case surveillance tracker can be adapted and used by countries to supplement existing national disease surveillance programs. The basic case surveillance program is designed to: + +1. Enroll suspected\* COVID-19 cases (*generally appearing at a health facility, but may be enrolled at other places*) +2. 捕获有关可疑病例的关键信息，包括人口统计信息和暴露情况，例如症状，与先前确认的病例联系以及出差历史 +3. 生成实验室请求 +4. 记录实验室诊断 +5. 记录已确认\ * \ *或可能的\ * \ * \ *案例的联系人以进行跟进 +6. 记录案例结果 +7. 促进案件通知和国家/地区/全球案件报告 +8. 生成仪表板和分析工具，以监控疾病趋势和计划响应工作 + +The design of the case tracker program assumes that [WHO case definitions][1] are followed in the use case; its use can be adapted to local case definitions as needed. The WHO case definitions were updated on March 20, 2020 and noted below. + +> \* Suspected case: A) a patient with acute respiratory illness (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness of breath), AND with no other aetiology that fully explains the clinical presentation AND a history of travel to or residence in a country/area or territory reporting local transmission of COVID-19 disease during the 14 days prior to symptom onset; **OR**, B) A patient with any acute respiratory illness AND having been in contact with a confirmed or probable COVID-19 case (see definition of contact) in the last 14 days prior to onset of symptoms; **OR,** C) A patient with severe acute respiratory infection (fever and at least one sign/symptom of respiratory disease (e.g., cough, shortness breath) AND requiring hospitalization AND with no other aetiology that fully explains the clinical presentation. +> +>\*\* Probable case: A) a suspect case for whom testing for COVID-19 is inconclusive (inconclusive being the result of the test reported by the laboratory) **OR,** B) a suspect case for whom testing could not be performed for any reason. +> +>\*\*\* Confirmed case: A person with laboratory confirmation of COVID-19 infection, irrespective of clinical signs and symptoms. + +### Intended Users { #intended-users } + +* 卫生机构用户：捕获并记录有关可疑病例的详细信息，包括临床症状和暴露；跟踪实验室结果；记录案例结果 +* 实验室用户：接收实验室要求并记录特定可疑病例的实验室结果 +* 国家和地方卫生当局：通过仪表板和分析工具监测和分析疾病监测数据，以进行风险评估和计划应对措施；生成区域和全球报告的报告 + +### Workflow: COVID-19 Case Surveillance Tracker { #workflow-covid-19-case-surveillance-tracker } + +![Workflow of the DHIS2 COVID-19 Case Surveillance Tracker](resources/images/sdd-tracker-v3-case1-workflow.png) + +### 结构：COVID-19案例监视跟踪程序 { #structure-covid-19-case-surveillance-tracker-program } + +![Structure of the COVID-19 Case Surveillance Tracker Program](resources/images/sdd-tracker-v3-case1-structure-v2.png) + +#### 程序说明：COVID-19病例测试，诊断和结果 { #program-description-covid-19-case-testing-diagnosis-outcome } + +| 阶段 | 描述 | +|---|---| +| **注册详细信息&属性** | The Tracked Entity is the case, which is represented by a Tracked Entity Type of ‘person.’ The *Enrollment date* is the date of registration of the case. The Related programs is *COVID-19 Contact registration & follow-up*. The attributes include the following basic personal information and unique case identifiers: *System Generated Case ID*, *Local Case ID*, *Age*, *First Name*, *Surname*, *Sex*, *Case phone number*, *First Name (parent or care)*, *Surname (parent or carer)*, *Home Address*, *Workplace/school physical address*, *Country of Residence*, *Facility contact number*| +| **第一阶段：临床检查和暴露** | 此阶段记录可疑病例的临床症状和暴露，包括：*症状*，*怀孕和基础状况*，*住院和隔离*，*症状出现前14天的暴露*，*出行历史*，*与确诊病例接触* 。检查后，您可以记录该病例是否已住院或隔离，以及有关此情况的信息。 | +| **阶段2：实验要求[可重复] ** | 实验室请求会记录测试原因以及实验室处理样品并测试其COVID19所需的其他信息。当资源有限时，此处提供的信息可帮助实验室人员确定实验室测试的优先级。输入此数据的人可以是注册可疑病例并记录患者的临床检查和暴露的同一人；或者可能是负责实验室要求的其他人员。 | +| **阶段3：实验结果[可重复] ** | “实验室结果”阶段记录了实验室测试的类型和结果。它可以直接在实验室完成，也可以作为辅助数据输入。此阶段是可重复的，因为可以对给定案例的样本进行多次测试（即，在实验室结果不确定的情况下，可以进行新的实验室测试并记录结果）。 | +| **第4阶段：健康结果** | 健康结果记录了该病例的最终结果：（恢复，未恢复，死亡或未知），包括出院或死亡日期（如适用）。 | + +#### Enrollment Stage { #enrollment-stage } + +![Enrollment](resources/images/sdd-tracker-v3-case1-enrollment.png) + +#### 计划第1阶段-临床检查和诊断 { #program-stage-1-clinical-examination-diagnosis } + +##### 第1节-临床体征和症状 { #section-1-clinical-signs-and-symptoms } + +在数据元素中选择“是”，“是否有迹象或症状？”将显示其余选项。 + +![Section 1](resources/images/sdd-tracker-v3-case1-stage1-section1.png) + +##### 第2节-怀孕详细信息 { #section-2-pregnancy-details } + +除非选择性别作为“女性”，否则此部分是隐藏的。 + +![Section 2](resources/images/sdd-tracker-v3-case1-stage1-section2.png) + +##### 第3节-基本条件/合并症 { #section-3-underlying-conditionscomorbidity } + +The details of this section are hidden unless “Any underlying conditions” is marked as “Yes”. + +![Section 3](resources/images/sdd-tracker-v3-case1-stage1-section3.png) + +##### 第4节-住院 { #section-4-hospitalisation } + +The details of this section is hidden unless “Hospitalised” is marked as “Yes”. + +![Section 4](resources/images/sdd-tracker-v3-case1-stage1-section4.png) + +##### 第5部分-暴露风险 { #section-5-exposure-risk } + +This section is used to record exposures + + 1. The fields ***country, city and facility*** are hidden by program rules if the case is not a health care worker; + 2. The fields for contact IDs are hidden by program rules if the case has not had contact with a confirmed case in 14 days. + +A suspected case’s exposure to a *previously confirmed* case is distinct from prospective contact tracing in Program Stage 5. + +![Section 5](resources/images/sdd-tracker-v3-case1-stage1-section5.png) + +##### 第6节-旅行历史 { #section-6-travel-history } + +![Section 6](resources/images/sdd-tracker-v3-case1-stage1-section6.png) + +#### 计划阶段2：实验请求 { #program-stage-2-lab-request } + +![Stage 2](resources/images/sdd-tracker-v3-case1-stage2.png) + +#### 第3阶段：实验室结果 { #stage-3-lab-results } + +![Stage 3](resources/images/sdd-tracker-v3-case1-stage3.png) + +#### 阶段4：健康成效 { #stage-4-health-outcomes } + +![Stage 4](resources/images/sdd-tracker-v3-case1-stage4.png) + +### 计划规则：COVID19案例监视跟踪器 { #program-rules-covid19-case-surveillance-tracker } + +The following program rules have been configured. If a country has an existing case surveillance program and wishes to incorporate elements of the COVID-19 case tracker into their existing program, special attention must be paid to the configuration of program rules. + +| 程序规则名称 | 程序规则说明 | +|---|---| +| Assign Enrollment Date | This assigns the enrollment date if there is no onset date available to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators. | +| Assign Onset Date| This assigns the onset date to the variable calculated onset date (for indicators). This variable is used as a custom parameter in some of the program indicators.| +| 计算并分配患者年龄（以年为单位） | 根据DOB计算并分配以年为单位的患者年龄 | +| 显示患者年龄，以年+天为单位 | 显示患者年龄，以年+天为单位 | +| Hide Date of Death | Hide the Date of Death unless Death is the health outcome | +| Hide Date of Discharge | Hide Date of Discharge if no outcome or if the outcome is death | +| Hide Measured Temperature field | Hide Measured Temperature field until Fever is selected | +| Hide confirmed case ID's if no contact with other confirmed cases| Hides any contact ID's if the case has not been in any contact with other confirmed cases | +| 如果不是医护人员，则隐藏医护人员的详细信息 | 如果不是医护人员，则隐藏医护人员的详细信息 | +| 如果健康结果不是其他，则隐藏健康结果说明 | 如果健康结果不是其他，则隐藏健康结果说明 | +| 如果没有住院或未知住院，则隐藏住院详细信息 | 如果没有住院或未知住院，则隐藏住院详细信息 | +| 如果案件不是隔离的，则隐藏隔离日期 | 如果案件不是隔离的，则隐藏隔离日期 | +| 隐藏未怀孕女性的怀孕详细信息 | 隐藏未怀孕女性的怀孕详细信息 | +| 如果性别是男性，则隐藏怀孕详细信息部分 | 如果性别是男性，则隐藏怀孕详细信息部分 | +| 如果选择了选项，则隐藏测试说明的原因 | 如果选择了选项，则隐藏测试说明的原因 | +| 如果症状发作前14天没有旅行，则隐藏旅行历史记录详细信息 | 如果症状发作前14天没有旅行，则隐藏旅行历史记录详细信息 | +| 如果案件没有任何内容，请隐藏基本条件 | 如果案件没有任何内容，请隐藏基本条件 | +| 如果活动日期晚于注册日期，则显示警告 | 如果活动日期早于注册日期，则在活动结束时显示警告 | + +You can read more about program rules here: [https://docs.dhis2.org/master/en/user/html/configure\_program\_rule.html][11] + +### 计划指标 { #program-indicators } + +根据COVID-19病例监测计划中捕获的数据，我们至少可以计算以下指标，包括WHO推荐的每日和每周汇总报告的指标，并将其显示在仪表板中： + +| 指标名称 | 描述 | +|---|---| +| COVID-19-经机械通气或ECMO治疗或进入重症监护病房（ICU）的病例 | *经机械通气或ECMO治疗或进入重症监护病房（ICU）的病例* | +| COVID-19联系人 | *计算与案例TEI相关联的关系（“已经联系过”）的数量* | +| COVID-19-死亡（所有可疑病例） | *与COVID-19相关的死亡（在所有可疑病例中均记录有死亡）* | +| COVID-19-死亡（确诊病例） | *与COVID-19相关的死亡（在确诊病例中记录有死亡）* | +| COVID-19-死亡（可能的病例） | *与COVID-19相关的死亡（在所有可能的病例中均记录有死亡）* | +| COVID-19-确诊住院病例 | *确诊病例数* | +| COVID-19-进口病例 | *可能感染源记录为另一个国家或从另一个国家进口的情况。* | +| COVID-19-实验室确诊病例 | *通过实验室测试确认的可疑病例（可以进行多次实验室测试；该指标假设最后的测试结果为*“阳性” *）；按报告日期显示* | +| COVID-19-实验室确诊病例-症状发作 | *通过实验室测试确认的可疑病例（可以进行多次实验室测试；该指标假设最后的测试结果为*“阳性” *）；按症状发作日期显示* | +| COVID-19-经过实验室测试的案例 | *接受实验室测试的可疑病例数（包括不确定的实验室测试结果）* | +| COVID-19-本地传播案例 | *本地传播的可疑病例数（过去14天没有旅行*） | +| COVID-19-可能的情况 | *截至报告日期，实验室结果不确定或由于任何原因未进行测试的疑似病例* | +| COVID-19-可能的病例-症状发作 | *截至症状出现之日，实验室结果不确定或由于任何原因未经测试的可疑病例* | +| COVID-19-已确诊的病例 | *实验室确认的病例数，结果已恢复*| +| COVID-19-疑似病例 | *截至报告日期怀疑有COVID-19的病例总数* | +| COVID-19-疑似病例-症状发作 | *按症状发作日期可疑的COVID-19病例总数* | +| COVID-19-疑似病例没有阳性检测结果 | *没有阳性实验室结果的可疑病例总数* | +| COVID-19进行的实验室测试总数 | *进行的实验室测试总数（测试数，而非案例数）* | +| COVID-19阳性检测总数 | *返回阳性结果的实验室测试总数（测试数量，而不是案例*） | +| COVID-19按性别和年龄段划分的死亡人数 | ***男性**：0-4、5-14、15-24、25-34、35-44、45-54、55-64、65-74、75-84、85 +＆＃124; **女性**：0-4、5-14、15-24、25-34、35-44、45-54、55-64、65-74、75-84、85 + * | +| COVID-19按性别和年龄段分类的确诊病例 | ***男性**：0-4、5-14、15-24、25-34、35-44、45-54、55-64、65-74、75-84、85 +＆＃124; **女性**：0-4、5-14、15-24、25-34、35-44、45-54、55-64、65-74、75-84、85 + * | +| 按性别和年龄段划分的COVID-19疑似病例 | ***男性**：0-4、5-14、15-24、25-34、35-44、45-54、55-64、65-74、75-84、85 +＆＃124; **女性**：0-4、5-14、15-24、25-34、35-44、45-54、55-64、65-74、75-84、85 + * | + +## 用例2：COVID-19联系人注册和后续操作 { #use-case-2-covid-19-contact-registration-follow-up } + +This program can be used in addition to the case surveillance tracker to facilitate the registration and follow-up of contacts of a confirmed case. In this scenario, it is assumed that if any contacts of a confirmed case meet criteria for suspected case and are referred for testing, the case will be enrolled into the COVID-19 Case Surveillance tracker program. + +联系人注册和跟进程序将案例的每个联系人（如COVID-19案例监视用例中所述）注册为新的跟踪实体实例（人员），并通过以下方式将其链接到COVID-19案例监视程序中的案例一个“关系”，它具有一个简单的可重复的随访阶段，可以记录症状和进行的任何随访。 + +### 工作流程：联系人注册和后续操作 { #workflow-contact-registration-follow-up } + +![Worflow of the Contact registration & follow-up](resources/images/sdd-tracker-v3-case2-workflow.png) + +### 程序说明：联系人注册和后续操作 { #program-description-contact-registration-follow-up } + +| 阶段 | 描述 | +|---|---| +| **注册详细信息&属性** | 跟踪实体以“人”的跟踪实体类型表示。相关程序是*基于COVID-19案例的监视*。这些属性包括以下基本个人信息和唯一的案例标识符：*系统生成的案例ID *，*本地案例ID *，*名字*，*姓氏*，*出生日期*，*年龄*，*性别*，*电话号码（本地）*，*家庭住址*，*居住国家* | +| **第1阶段：跟进[不可重复] ** | 假定已经确定了联系人，则此阶段旨在记录与联系人跟踪跟进有关的信息。它分为两个部分：* 1。与案例的关系*，* 2。暴露评估* | +| **阶段2：症状[可重复] ** | 此阶段旨在记录案件的症状。可以重复进行随访以检查接触者的症状，直到完成随访期为止（例如，在14天后或根据国家指南）。随访期结束后，可以“完成注册”。* 1。症状*| + +使用案例监视程序中的“关系”菜单将联系人添加到索引案例： + +![Profile](resources/images/sdd-tracker-v3-case2-profile.png) + +从关系框中选择“添加”后，就可以选择关系和程序，并使用出现的注册阶段选择现有人员或注册新联系人。这会将联系人注册到联系人注册和后续操作中 +程序。 + +![Add a relationship](resources/images/sdd-tracker-v3-case2-add-relationship.png) + +然后，添加的联系人将在关系中的案例跟踪器仪表板上列出 +小部件 + +![Relationships widget](resources/images/sdd-tracker-v3-case2-relationships-widget.png) + +您也可以将它们分别注册到程序中。注册后，您将可以根据需要找到它们以进行后续操作。 + +#### 注册 { #enrollment } + +![iEnrollment in the use case 2](resources/images/sdd-tracker-v3-case2-enrollment-case2.png) + +#### 计划阶段1：后续行动 { #program-stage-1-follow-up } + +![Case 2 Stage 1](resources/images/sdd-tracker-v3-case2-stage1.png) + +#### 程序阶段2：症状 { #program-stage-2-symptoms } + +![Case 2 Stage 2](resources/images/sdd-tracker-v3-case2-stage2.png) + +### 计划指标：联系人注册 { #program-indicators-contact-registration } + +| 计划指标名称 | 描述 | +|---|---| +| 筛选出19位COVID旅客 | 从POE筛选并加入筛选程序的旅行者总数 | +| COEID-19旅客在POE出关 | 进行POE筛查后清除的旅客人数（无需跟进） | +| 有POE症状的COVID-19旅客 | 在POE筛查期间出现症状的旅行者人数 | +| 监测14天后，COVID-19旅客被放行 | 14天随访后被疏散的旅行者数量（14天之内没有症状发作） | +| COVID-19旅客转往医疗机构 | 在14天的随访期间中任何时间被转介到医疗机构的旅行者数量 | +| COVID-19旅客参加了14天的随访 | 在POE筛查中未出现症状且在POE筛查中未清除的旅行者数量 | +| 目前正在跟踪COVID-19 | 尚未通关或转诊至医疗机构的旅客人数 | +| COVID-19旅行者在随访期间出现症状 | 随访期间出现症状的旅行者人数（不包括在POE筛查过程中出现症状的旅行者） | + +## 引用 { #references } + +* 世卫组织关于COVID-19监测和病例定义的技术指南（最新更新为2020年3月20日） ]（https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions） +* WHO COVID-19病例报告表数据字典[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-zh.xlsx ]（https：// www .who.int / docs / default-source / coronaviruse / 2020-02-27-data-dictionary-en.xlsx） +* 世卫组织在可疑人类病例中对2019年新型冠状病毒（2019-nCoV）进行的实验室测试（最新更新为2020年3月2日） in-suspected-human-cases 20200117]（https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117） +* 世卫组织在调查COVID-19的病例和群中的考虑因素（最新更新于2020年3月13日） -clusters-covid-19]（https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19） +* 世卫组织冠状病毒情况报告[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/情况报告） + +[1]: https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf +[2]: https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions +[3]: https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx +[4]: https://drive.google.com/open?id=1vigXHkP7L2hJ2lrZpdf9u4csQtppMH16 +[5]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html +[6]: https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html +[7]: #use-case-1-covid-19-case-surveillance-tracker +[8]: https://www.who.int/docs/default-source/coronaviruse/data-dictionary-covid-crf-v6.xlsx?sfvrsn=a7d4ef98_2 +[9]: #use-case-2-covid-19-Contact-registration-follow-up +[10]: https://play.google.com/store/apps/details?id=com.dhis2&hl=en +[11]: https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md new file mode 100644 index 00000000..e8658ea1 --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__installation-md @@ -0,0 +1,166 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_cs-installation.md" +revision_date: '2022-09-13' +tags: +- Implement +--- + +# COVID-19 Surveillance - Installation Guide { #c19-cs-installation } + +## 总览 { #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: + +1. COVID-19基于案例的监视跟踪程序和COVID-19联系人注册与跟进程序 +2. 入口点筛选跟踪程序 + +您将必须完全遵循所安装的每个单独软件包的说明。 + +## 安装 { #installation } + +模块的安装包括以下几个步骤： + +1. [准备]（＃preparing-the-metadata-file）具有DHIS2元数据的元数据文件。 +2. 将元数据文件[导入]（＃importing-metadata）到DHIS2中。 +3. [配置]（＃additional-configuration）导入的元数据。 +4. 导入后[Adapting]（＃adapting-the-tracker-program）程序 + +建议在开始DHIS2中的安装和配置过程之前先通读每个部分。根据要导入到新的DHIS2实例还是具有元数据的DHIS2实例，已识别出不适用的节。在重复或转移到DHIS2的生产实例之前，应在测试/分阶段环境中测试本文档中概述的过程。 + +## 要求 { #requirements } + +为了安装该模块，需要DHIS2上的管理员用户帐户。在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 } + +**注意**：如果要将软件包安装在DHIS2的新实例上，则可以跳过“准备元数据文件”部分，然后立即移至“ [将元数据文件导入DHIS2]（＃importing-元数据）。” + +尽管并非总是必要，但在将元数据文件导入DHIS2之前对其进行某些修改通常可能是有利的。 + +### 默认数据维度 { #default-data-dimension } + +在早期版本的DHIS2中，默认数据维的UID是自动生成的。因此，尽管所有DHIS2实例都具有默认类别选项，数据元素类别，类别组合和类别选项组合，但这些默认的UID可以不同。 DHIS2的更高版本具有用于默认维度的硬编码UID，并且这些UID在配置包中使用。 + +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 + +|目的|用户标识|API endpoint| +|--|--|--| +|类别|GLevLNI9wkl|../api/categories.json?filter=name:eq:default| +|类别选项|xYerKDKCefk|../api/categoryOptions.json?filter=name:eq:default| +|Category combination|bjDvmb4bfuf|../api/categoryCombos.json?filter=name:eq:default| +|Category option combination|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. + +然后，您可以在.json文件中搜索所有出现的HllvX50cXC0并将其替换为bRowv6yZOF2，因为这是您要导入的系统中的默认ID。 ***请注意，此搜索和替换操作必须使用纯文本编辑器***，而不是像Microsoft Word这样的字处理器。 + +### 指标类型 { #indicator-types } + +指标类型是另一种可能导致导入冲突的对象，因为在不同的DHIS2数据库中使用了某些名称（例如“百分比”）。由于指标类型仅由其因子以及是否为无分母的简单数字定义，因此它们是明确的，可以通过搜索和替换UID进行替换。这样可以避免潜在的导入冲突，并避免创建重复的指标类型。表2显示了可以替换的UID以及用于标识现有UID的API端点 + +|目的|用户标识|API endpoint| +|--|--|--| +|Numerator only (number)|kHy61PbChXr|../api/indicatorTypes.json?filter=number:eq:true&filter=factor:eq:1| +|百分比|hmSnCXmLYwt|../api/indicatorTypes.json?filter=number:eq:false&filter=factor:eq:100| + +#### 追踪实体类型 { #tracked-entity-type } + +像指示器类型一样，您的DHIS2数据库中可能已经存在跟踪的实体类型。对跟踪实体类型的引用应该更改以反映系统中的内容，因此您不会创建重复项。表3显示了可以替换的UID以及用于标识现有UID的API端点 + +|目的|用户标识|API endpoint| +|--|--|--| +|Person|MCPQUTHX1Ze|../api/trackedEntityTypes.json?filter=name:eq:Person| + +## 导入元数据 { #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 } + +***注意***：如果要导入到新的DHIS2实例中，则不必担心导入冲突，因为要导入的数据库中没有与之冲突的内容。按照说明导入元数据，然后继续进行“ [附加配置]（＃additional-configuration）”部分。 + +可能会发生许多不同的冲突，尽管最常见的是配置包中有目标数据库中已经存在名称，简称和/或代码的元数据对象。对于这些问题，有两种替代解决方案，具有不同的优缺点。哪一个更合适将取决于例如发生冲突的对象的类型。 + +#### 备选方案1 { #alternative-1 } + +重命名DHIS2数据库中存在冲突的现有对象。这种方法的优点是无需修改.json文件，因为更改是通过DHIS2的用户界面完成的。这很可能不太容易出错。这也意味着配置包将保留原样，例如在使用基于配置包的培训材料和文档时，这可能是一个优势。 + +#### 备选方案2 { #alternative-2 } + +重命名.json文件中存在冲突的对象。这种方法的优点是现有的DHIS2元数据保持不变。当存在培训材料或文档（例如链接到所讨论对象的数据字典的SOP）时，这可能是一个因素，并且不存在通过修改用户熟悉的元数据而使用户感到困惑的风险。 + +请注意，对于备选项1和2，修改可以简单到在名称中添加一个小的前缀/后缀，以最大程度地减少混乱的风险。 + +#### 备选3 { #alternative-3 } + +第三种也是更复杂的方法是修改.json文件以重新使用现有的元数据。例如，在某个概念的某个选项集已经存在的情况下（例如“性别”），可以从.json文件中删除该选项集，并且对其UID的所有引用都将替换为数据库中已经存在的相应选项集。这样做的最大优点（不限于直接导入冲突的情况）是避免在数据库中创建重复的元数据。执行这种类型的修改时，需要考虑一些关键因素： + +* 它需要有关DHIS2详细元数据结构的专业知识 +* 该方法不适用于所有类型的对象。特别地，某些类型的对象具有依赖关系，这种依赖关系以这种方式难以解决，例如与分解有关。 +* 将来对配置包的更新将很复杂。 + +## 附加配置 { #additional-configuration } + +成功导入所有元数据后，需要执行一些步骤，模块才能正常运行。 + +### 分享中 { #sharing } + +首先，您将必须使用DHIS2的*共享*功能来配置哪些用户（用户组）应查看与程序关联的元数据和数据，以及谁可以在程序中注册/输入数据。默认情况下，已为以下配置共享： + +* 追踪实体类型 +* 程序 +* 计划阶段 +* 仪表板 + +软件包随附三个用户组： + +* COVID19访问 +* COVID19管理员 +* COVID 19数据捕获 + +默认情况下，将以下内容分配给这些用户组 + +|目的|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| +|_*Program*_|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| +|_*Dashboards*_|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 } + +用户将需要用户角色才能参与DHIS2中的各种应用程序。建议以下最低角色： + +1. 跟踪器数据分析：可以查看事件分析并访问仪表板，事件报告，事件可视化器，数据可视化器，数据透视表，报告和地图。 +2. 跟踪器数据捕获：可以添加数据值，更新跟踪的实体，跨组织单位搜索跟踪的实体以及访问跟踪器捕获 + +Refer to the [DHIS2 Documentation](https://docs.dhis2.org) for more information on configuring user roles. + +### 组织单位 { #organisation-units } + +您必须将程序分配给自己的层次结构中的组织单位，以便能够在跟踪器捕获中查看程序。 + +### 重复的元数据 { #duplicated-metadata } + +**注意**：仅当您要导入已经存在元数据的DHIS2数据库时，此部分才适用。如果您使用的是新的DHIS2实例，请跳过本节，然后转到[调整跟踪程序]（＃adapting-the-tracker-program）。” + +即使成功导入了元数据而没有任何导入冲突，元数据中也可能存在重复项-数据元素，跟踪的实体属性或已存在的选项集。正如上面有关解决冲突的部分所述，要牢记的一个重要问题是，在DHIS2中更改元数据的决定还需要考虑与现有元数据有不同关联的其他文档和资源。 ，以及通过配置包导入的元数据。因此，解决重复项不仅是“清理数据库”的问题，而且还要确保做到这一点，例如，不破坏与其他系统的集成，使用培训材料的可能性，破坏SOP等。这将非常很大程度上取决于上下文。 + +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). + +## 调整跟踪器程序 { #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: + +* 向表单添加其他变量。 +* 根据国家惯例修改数据元素/选项名称。 +* 向变量和/或数据输入表单添加翻译。 +* 根据本地案例定义修改程序指标 + +但是，如果您决定更改或删除任何包含的表格/元数据，强烈建议格外小心。修改可能会破坏功能，例如程序规则和程序指示器。 + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md new file mode 100644 index 00000000..4a095d5d --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__overview-md @@ -0,0 +1,29 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/overview.md" +revision_date: '2022-11-22' +tags: +- Implement +--- + +# COVID-19 Case Surveillance { #covid-19-case-surveillance } + +## Release Note { #release-note } + +- [Release Note](#c19-cs-release-note) + +## Design { #design } + +- [Version 1.0.2](#c19-cs-design) + +## 安装 { #installation } + +- [Installation Guide](#c19-cs-installation) + +## Metadata Reference { #metadata-reference } + +- [Version 1.0.2](https://packages.dhis2.org/en/C19_CS/1.0.2/C19_CS_COMPLETE_1.0.2_DHIS2.37.xlsx) + +## Training Material { #training-material } + +- [COVID-19 Training Material](https://dhis2.org/covid-training-material) + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-CASE-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..1cfdac6a --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implement +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### 总览 { #overview } + +我们对现有软件包进行了一些更新以与新的COVID-19 [WHO于2020年3月20日发布的监视准则]保持一致（https://www.who.int/emergencies/diseases/novel-coronavirus-2019/技术指导/监视和案例定义），并在整个支持包中引入了新组件。如有任何疑问，请在此处查看注释，并在[实践社区]（https://community.dhis2.org/c/implementation/covid-19/）中的COVID-19讨论板上与我们联系。 + +**可以从[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. + +新版本包括： + +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. 更新元数据代码以使其与[WHO基于病例的报告数据字典]保持一致（https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx） +2. 更新了计划指标以反映世卫组织针对可能病例的新病例定义（请参考2020年3月20日更新的临时监测指南中的更新病例定义[世卫组织2020年3月20日更新的临时监测指南]（https://apps.who.int/ iris / bitstream / handle / 10665/331506 / WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf）） +3. 更新了年龄传奇，以符合WHO每周报告的新指南 +4. RelationshipType已添加到元数据包 +5. 对元数据进行了较小的修复，以使程序包的安装更加容易（即，indicatorType UID与聚合程序包中包含的指示器类型相匹配） + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. 添加了一个新的程序阶段，以使案例联系人可以重复地进行“跟进”。添加此信息是为了反映在乌干达和多哥实施的工作流，在此过程中，可以在14天内对联系人进行重复监视，以确定是否有症状。 ***计划***基于WHO指南，可在[此处]找到（https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and -clusters-of-covid-19），以及通过[OpenWHO]（https://openwho.org/courses/introduction-to-ncov）网站获得的信息。 +2. 更新了年龄传奇，以符合WHO每周报告的新指南 +3. RelationshipType已添加到元数据包 +4. 对元数据进行了较小的修复，以使软件包安装更加容易 + +### COVID-19总体监视报告 { #covid-19-aggregate-surveillance-reporting } + +进行了以下更新以反映[2020年3月20日更新的WHO指南]中的新指南（https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6- eng.pdf），包括向WHO提交的最新全球汇总报告（每周和每天） + +1. 根据新年龄段更新了年龄类别 +2. 新指标增加了确诊病例中男性比例和确诊死亡中男性比例 +3. 根据更新的世卫组织每周报告指南，新的每周数据集可捕获一级国家以下水平的传播分类（即省级-可以根据国家/地区分配给任何二级国家以下水平） +4. 对元数据进行了较小的修复，以使软件包安装更加容易 + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +入境点跟踪程序计划用例旨在支持对有国家/地区/领地旅行历史或居住地的国家/地区报告COVID-19本地传播的旅行者进行注册，并可能需要对其进行跟进确保没有症状出现。它基于HISP斯里兰卡实施的设计，通过少量更改来支持斯里兰卡卫生部，以使该程序在全球范围内更通用，并与COVID-19软件包中的其他跟踪程序保持一致。该一揽子计划支持世卫组织[入境处疾病管理技术指南]中详细介绍的入境点干预措施（https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidedance /进入和聚集的点数）。 + +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/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md new file mode 100644 index 00000000..8bcbd2ff --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__design-md @@ -0,0 +1,136 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/c19_poe-design.md" +revision_date: '2022-07-05' +tags: +- Implement +--- + +# COVID-19 Points of Entry Tracker Design { #c19-poe-design } + +Demo: [https://covid19.dhis2.org/](https://covid19.dhis2.org/demo) + +## 目的 { #purpose } + +The COVID-19 Points of Entry (POE) Screening System Design document provides an overview of the conceptual design used to configure a COVID-19 digital data package in DHIS2. The COVID-19 package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## 背景 { #background } + +The Points of Entry Screening Tracker is inspired by the pioneering design implemented by HISP Sri Lanka to support the Sri Lanka Ministry of Health. In January 2020, the Sri Lanka MOH implemented screening measures at ports of entry like airports to identify travelers who may have been exposed to nCoV-19. DHIS2 tracker was to enroll travelers entering Sri Lanka who had visited countries impacted by COVID-19. DHIS2 tracker enabled follow-up with travelers at field level for 14 days to ensure no symptoms developed. If symptoms developed, travelers would be referred to a health facility for clinical examination and testing. The POE tracker can be used in combination with other COVID-19 digital data packages that include case surveillance and contact tracing. + +The World Health Organisation (WHO) has published [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). Points of entry (POE) include international airports, seaports and land crossings. POE measures include 1) detection of ill travellers; 2) interview of ill travellers for COVID-19; 3) reporting of alerts of ill travellers with suspected COVID-19 infection and 4) isolation, initial case management and referral of ill travellers with suspected COVID-19 infection. These guidelines should be consulted, in addition to national protocols for points of entry. + +## 系统设计摘要 { #system-design-summary } + +### Use Case { #use-case } + +The POE tracker program use case was designed to support the registration of travelers 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. For this use case, it is assumed that a traveler may be 1) screened and cleared immediately with no follow-up needed; 2) screened and followed up for 14 days [with or without isolation measures] to ensure no symptoms develop; or 3) screened and referred for testing and/or initial case management. The current design proposes that a traveler meeting the country’s definition of a suspected case would be enrolled into the complementary DHIS2 COVID-19 Case-Based Surveillance (CBS) Tracker. For example, a traveler enrolled in this program who later meets the definition of a suspected case during follow-up (i.e. an asymptomatic traveler from a country with known transmission is registered at the POE and later develops symptoms) is enrolled as a suspected case into the COVID-19 CBS program to capture all clinical details, exposures and follow the case through laboratory diagnosis and case outcome. + +In the development of this configuration package, an effort has been made to follow UiO’s [general design principles](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/general-design-principles-for-who-metadata-packages.html) and a common [naming convention](https://docs.dhis2.org/en/topics/metadata/dhis2-who-digital-health-data-toolkit/naming-conventions.html). + +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). + +### 目标用户 { #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. +* National and local health authorities: monitor and analyse data through dashboards and analytics tools to conduct risk assessments and plan response measures. + +### 工作流程 { #workflow } + +The Points of Entry program workflow is based on the following scenario + +![Scenario](resources/images/POE_image01.png "Scenario") + +In this design, it is assumed a traveler would complete their enrollment in the POE under the following scenarios: + +1. Traveler is marked as ‘cleared’ during initial screening or after 14 day follow-up +2. Traveler is referred to health facility at any point during follow-up + +**A traveler that is referred to a health facility is expected to be enrolled in the COVID-19 Case-based Surveillance Tracker as a suspected case** (according to national guidelines). Details about a suspected case including clinical exam, exposures, laboratory results and case outcome would be recorded in the CBS program. + +### Structure: Points of Entry Screening Tracker Program { #structure-points-of-entry-screening-tracker-program } + +![Structure](resources/images/POE_image02.png "Structure") + +#### Consideration for Organisation Units & Geography { #consideration-for-organisation-units-geography } + +This program design assumes that Points of Entry such as airports, seaports or land crossings will be created as organisation units included in the OU hierarchy. The program would be assigned to the POE org units. Primary analysis is based on the enrolling Org Unit (the port of entry). + +Additional geographical components are also captured as other dimensions: + +1. TEI coordinates: It is possible to capture TEI coordinates when registering the traveler as TEI. These can be displayed in the maps app. Local protocols may choose what coordinates to enter, for example the TEI’s local residence where he/she may be self-quarantined for 14 days. +2. Event coordinates: for screening and follow-up stages, coordinates can be captured on the event and displayed in a map. For example, the user may capture a traveler’s location each time they are followed up (i.e. in the case of tourists or others not in home quarantine). + +#### Program Description { #program-description } + +|阶段|描述| +|--|--| +|**Registration**|The Tracked Entity is the traveler, which is represented by the Tracked Entity Type of ‘person.’ The TEI is configured to collect a geographic ‘point’ during registration. These can be analyzed in a map.| +|**Enrollment details**|Enrollment date
The first Program Stage is configured to appear on the Registration page so that a user does not need to click through to add the first event.| +|**属性**|Attributes include basic personal information and unique case identifiers
- Passport number
- Local Case ID
- Age
- First Name
- Surname
- Country of residence
- Sex
- Date of birth
- Local address
- Home address
- Telephone (local)
- Telephone (foreign)
- Emergency contact
- Emergency contact phone
- Email| +|**Stage 1**
**Screening at POE**
**(non-repeatable)**|This stage records:
- Traveler details (countries visited, flight number, date of departure, etc)
- Examination: recorded temperature
- Symptoms: this list includes symptoms typically checked for both COVID-19 symptoms and symptoms of other potential notifiable diseases
- Case clearance

If the traveler is marked as ‘cleared’, no further follow up is required; the enrollment may be closed. If the traveler requires follow-up, an event can be scheduled for follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 2:**
**Follow-up (within 14 days)**
**(repeatable)**|Data is entered at this stage if any interim follow-up is performed before the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment may be closed if no further monitoring & follow-up is planned in this program.

The data entry form is blocked after completion; no further changes can be made without authorization.| +|**Stage 3:**
**Follow-up (after 14 days)**
**(non-repeatable)**|Data is entered at this stage at the end of 14 days. Event coordinates can be captured (i.e. the current location of the traveler at the time follow-up was completed) to present in a map.
- Symptoms
- Referral (user may select an Organisation Unit in a Data Element configured as type OU, for example to select a health facility where a traveler was referred after reporting symptoms)
- Case clearance

If a traveler has symptoms and is referred to a health facility for testing, the traveler should be enrolled into the Case based Surveillance program. The enrollment should be closed at the completion of 14 day follow-up.

The data entry form is blocked after completion; no further changes can be made without authorization. + +![Enrollment](resources/images/POE_image03.png "Enrollment") + +![Program Stage 1 - Screening at POE](resources/images/POE_image04.png "Program Stage 1 - Screening at POE") + +![Program Stage 1 - Screening at POE](resources/images/POE_image05.png "Program Stage 1 - Screening at POE") + +![Program Stage 2: Follow-up (within 14 days)](resources/images/POE_image06.png "Program Stage 2: Follow-up (within 14 days)") + +![Program Stage 3: Follow up (after 14 days)](resources/images/POE_image07.png "Program Stage 3: Follow up (after 14 days)") + +#### How to refer the TEI to another Organisation Unit { #how-to-refer-the-tei-to-another-organisation-unit } + +Primary analysis is completed on the enrolling organisation unit (the port of entry). Referral facility is captured as a Data Element (type: Organisation Unit) in order to display travelers by referral to health facility in the analytics apps (i.e. Event Report). In some use cases, it may be desirable to refer the TEI (the traveler) to another Org Unit for follow-up. + +A TEI can be ‘referred’ to another org unit such as a health facility for one event or permanently. In this case, health facility user must be able to search TEIs enrolled in the relevant Points of Entry org units. For example, if after screening a traveler at the POE, the traveler may be “referred” to a district health office near the traveler’s local address for follow-up by district health staff. After completing the data entry for Stage 1 (screening), the user would refer the TEI to a District Health Center. Read more about referrals in tracker in [DHIS2 User Documentation](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/tracking-individual-level-data/tracker-capture.html). + +![alt_text](resources/images/POE_image08.png "image_tooltip") + +### Program Relationships { #program-relationships } + +This program has the relationshipType ‘Has been in contact with’. Users can create a relationship between TEIs enrolled in the POE program and TEIs in other COVID-19 tracker programs (Case-based Surveillance, Contact Registration & Follow-up). The relationship can be added at any point in the program stages during data entry. + +### Program Rules { #program-rules } + +The following program rules have been configured. + +|程序规则名称|程序规则说明| +|--|--| +|计算并分配患者年龄（以年为单位）|计算并分配患者年龄（以年为单位）| +|Hide countries if not visited|Hide countries if not visited| +|Hide Follow-Up Stages|Hide Follow-Up Stages if the case is cleared at the port of entry| +|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)|Hide symptoms if no symptoms present (Follow Up at the end of 14 days)| +|Hide symptoms if no symptoms present (Follow Up within 14 days)|Hide symptoms if no symptoms present (Follow Up within 14 days)| +|Hide symptoms if no symptoms present (PoE)|Hide symptoms if no symptoms present (PoE)| + +You can read more about program rules here: +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#create_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +||| +|--|--| +|筛选出19位COVID旅客|从POE筛选并加入筛选程序的旅行者总数| +|COEID-19旅客在POE出关|进行POE筛查后清除的旅客人数（无需跟进）| +|有POE症状的COVID-19旅客|在POE筛查期间出现症状的旅行者人数| +|监测14天后，COVID-19旅客被放行|14天随访后被疏散的旅行者数量（14天之内没有症状发作）| +|COVID-19旅客转往医疗机构|在14天的随访期间中任何时间被转介到医疗机构的旅行者数量| +|COVID-19旅客参加了14天的随访|在POE筛查中未出现症状且在POE筛查中未清除的旅行者数量| +|目前正在跟踪COVID-19|尚未通关或转诊至医疗机构的旅客人数| +|COVID-19旅行者在随访期间出现症状|随访期间出现症状的旅行者人数（不包括在POE筛查过程中出现症状的旅行者）| +|COVID-19 % travelers developed symptoms during 14-day follow-up|Numerator: Number of travelers that developed symptoms during follow-up (exclude travelers presenting with symptoms during POE screening)
Denominator: Number of travelers that did not present with symptoms at POE screening and were not cleared at POE screening| + +Users can also generate an Event Report to see: + +1. Travelers by nationality and/or originating country +2. Referrals to health facility + +## 引用 { #references } + +* DHIS2 COVID-19 [Tracker Package Installation Guide](covid-19-tracker-installation.html) +* World Health Organisation (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) (interim guidance, published 19 March 2020) + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md new file mode 100644 index 00000000..dd260ca4 --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-POINTS-OF-ENTRYDISCONTINUED__overview-md @@ -0,0 +1,25 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_POE/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Points of Entry { #covid-19-points-of-entry } + +## Design { #design } + +[Version 1.0.2](#c19-poe-design) + +## 安装 { #installation } + +[Installation Guide](#c19-poe-installation) + +## Release Note { #release-note } + +[Release Note](#c19-poe-release-note) + +## Metadata Reference { #metadata-reference } + +[Version 1.0.2](https://packages.dhis2.org/en/C19_POE/1.0.2/C19_POE_COMPLETE_1.0.2_DHIS2.37.xlsx) + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md new file mode 100644 index 00000000..1aae6528 --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__design-md @@ -0,0 +1,164 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/c19_evt-design.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Surveillance Line-list Design { #c19-evt-design } + +Demo: [https://covid.dhis2.org](https://covid.dhis2.org/demo) + +## 目的 { #purpose } + +The COVID-19 Surveillance Event Program System Design document provides an overview of the design principles and guidance used to develop the digital data package for aggregate COVID-19 surveillance. This document is intended for use by DHIS2 implementers at country and regional level to be able to support implementation and localisation of the package. The COVID-19 metadata package can be adapted to local needs and national guidelines. In particular, local work flows and national guidelines should be considered in the localization and adoption of the programs included in this package. + +## 背景 { #background } + +The COVID-19 digital data package was developed in response to an expressed need from countries to rapidly adapt a solution for managing COVID-19 data. UiO has developed COVID-19 surveillance packages for three types of data models (tracker, event-based aggregate) to enable countries to select the model that is most appropriate for their context given the burden of disease and available resources. These models and their relative benefits/limitations are summarized below: + +|监控套餐类型|基于案例的监视（跟踪器）|监视（事件）|监视（总计）| +|--|--|--|--| +|_Description_|Enrolls a case and tracks over time through laboratory confirmation & case outcome|以行列表格式捕获关键案例详细信息|启用每日或每周的关键汇总数据点报告| +|_Pros_|高度精细的数据和用于分析的多个时间维度，可以支持分散的工作流，所有事件都与案例相关|比汇总更精细，可以捕获关键的时间维度（即报告日期与症状发作）；与跟踪器相比，减少了数据输入的负担，并且几乎没有复杂性|低复杂度，易于实施，在案件数量高时最易于管理| +|_Cons_|当案件数达到阈值时，数据输入的负担可能会不堪重负；实施的复杂性|不支持个案跟进或其他分散式工作流程|进行详细分析的粒度较小（即仅根据病例报告日期进行分析，分类范围有限） + +**This document covers only the design of the surveillance event program package**; separate system design documents are available for DHIS2 Tracker and aggregate packages. + +世卫组织“敦促所有国家通过准备应急系统来为COVID-19的潜在到来做准备；提高发现和照顾病人的能力；确保医院有足够的空间，物资和必要的人员；并开发挽救生命的医疗干预措施。” + +COVID-19监视的目标是： + +1. 监测发生人际传播的疾病趋势； +2. 在病毒未传播的国家中迅速发现新病例； +3. 提供流行病学信息以在国家，区域和全球范围内进行风险评估；和 +4. 提供流行病学信息以指导准备和应对措施。 + +The system design builds upon existing disease surveillance principles and information system requirements that have been developed collaboratively between the WHO and UiO since 2017. The COVID-19 package was developed with the intent to align to [WHO technical guidance on nCoV-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions), last updated March 20, 2020. Note that this design may not necessarily reflect the latest available interim global guidance developed by WHO as updates may be released rapidly. National guidelines and policies may vary and it is recommended to adapt this package to local context. + +## 系统设计摘要 { #system-design-summary } + +This package is designed as a DHIS2 [Event Program](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#about_event_program). **The Event Program is not designed to capture all data variables contained in the [WHO case reporting template](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx)**. To capture a complete set of WHO case reporting variables, please refer to the DHIS2 COVID-19 Case-based Surveillance Tracker. Rather, the event program is a simplified program that captures a subset of minimum critical data points to facilitate high data quality when the number of caseloads or burden of reporting exceeds capacity for successfully completing the full line-list for suspected COVID-19 cases. For implementers who wish to capture the complete WHO line-listing, please refer to the COVID-19 Case-based Surveillance Tracker Package. + +The COVID-19 Surveillance Event Program data package includes: + +1. Event program and data elements case reporting +2. Core indicators +3. 仪表板 + +### Use Case: Simplified line-listing of COVID-19 cases { #use-case-simplified-line-listing-of-covid-19-cases } + +As cases increase rapidly, some countries may struggle with case-based reporting as the burden becomes too high. The event package is designed to capture the most critical data points in a line-list and analytical capacities for surveillance and response. The event package is designed as a standalone program. However, countries may use the event package in combination with other packages (i.e. event reports and daily aggregate reporting); or, they may shift from tracker to event to aggregate as caseloads and reporting burden increases. **_Countries should plan carefully how they intend to implement these packages in combination, including reporting flows, transitioning from one data model to another, and how to maintain historical data for analysis if transitioning between data models. _** + +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. + +#### 目标用户 { #intended-users } + +* Health facility users: capture and report key data on COVID-19 cases and deaths presenting at the health facility +* 国家和地方卫生当局：通过仪表板和分析工具监测和分析疾病监测数据，以进行风险评估和计划应对措施；生成区域和全球报告的报告 + +#### 工作流程 { #workflow } + +Unlike the tracker program, there are limitations to decentralization of the data reporting workflow in an Event program. The most significant limitation is that the Case Outcome (recovery or death) is often not known until days or weeks after the case is reported. The current program design allows for the following workflow options: + +1. Event is created when a suspected case is reported. All known data is entered, but the event is not completed. A user can select an ‘Active Event’ from a working list based on User filters and criteria. When missing data becomes available (i.e. the case outcome), the user can enter the remaining data fields and complete the event. Cases can be identified in the event list by the Case ID data element. See the image below as an example which can be accessed within the Capture App: +![Capture App](resources/images/EVENT_image1.png "Capture App") + +2. Event is created. All case related data is entered retrospectively, including the Outcome. Event is completed. _The limitation is this approach is timeliness of the data reporting, as new suspected cases might not be captured until their outcome which is often too late for decision making._ + +### Program Structure { #program-structure } + +The program is called ‘COVID-19 Cases (events)’ + +|Section|描述| +|--|--| +|Date of report|Event Date
_Countries may re-name the event date to apply to their protocols._| +|Section 1
**Basic Information**|Records basic demographic data.
_Countries may add data elements as desired._
- **Patient ID**
Can be used to filter events in working lists, eg. Active events
- **Sex**
- **Age**| +|Section 2
Case Details|Records information about the case including symptoms, severity, testing, etc.
- **Symptoms**
Options: Yes / No
Specifies whether a case has any symptoms at time of notification

- **Date of symptoms onset**
Only appears if symptoms are present;
Date of symptoms onset, if available, will replace “Date of Report” in data analytics and reporting.

- **Case Severity (at time of notification)**
Options: Mild / Moderate / Severe / Critical
- **Laboratory tested?**
Options: Yes / No/ Unknown
Specifies whether a case has been laboratory tested for COVID-19

- **Test Result**
Only appears if the case was laboratory tested
Options: Inconclusive / Positive / Negative / Unknown
The program is designed to capture only the final test result. Results for each individual test (if available) and the total number of tests performed are not captured.
- **Case Classification**
Options: Suspected case / Probable case / Laboratory confirmed case
Automatically assigned values
The values are assigned by Program rules in accordance with WHO case definitions
This feature can be useful in filtering active cases in the working lists.| +|Section 3
**Exposures**|- **Has the case traveled in the 14 days prior to symptoms onset?**
Options: Yes / No / Unknown
Specifies travel history of the case.

- **Likely Infection Source**
Options: Imported case* / Local Transmission / Exposure unknown
* Imported case option appears only if the case traveled in the 14 days prior to symptoms onset

- **Specify local source**
Only appears if Likely Infection Source is Local Transmission
Options: Community (workplace, public transport, etc.) / Household / Healthcare Facility / Close Contact with Other Infected Individual / Exposure Unknown

- **Case Type**
Options: New index case / Linked to existing cluster / Unknown
Specifies whether the case is connected to an existing cluster or is a new index case| +|Section 4
**Treatment**|- **Hospitalised**
Options: Yes / No

- **Did the case receive care in an intensive care unit (ICU)?**
Only appears if the case is hospitalised
Options: Yes / No| +|Section 5
**Contacts**|- **Total number of contacts followed for this case**
Records number of contacts| +|Section 6
**Outcome**|- **Health outcome**
Options: Recovered / Death| +|Section 7
**Assigned Date of onset of symptoms**|- **Calculated onset date (for Indicators)**
This section is used only to calculate indicators based on report date vs. date of onset of symptoms]
This automatically assigned date is used in program indicators. Initially, it is the report date. If the date of onset of symptoms is available, the date is replaced by the date of onset of symptoms.| +|**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 } + +The following user groups are included in the metadata package: + +1. COVID19 admin -- intended for system admins to have metadata edit rights +2. COVID19 data capture -- intended for data entry staff to have access to capture data +3. COVID19 access -- intended for users such as analytics users who should be able to view the data, but not edit metadata. + +Currently, only users assigned to the COVID19 data capture group will have access to capture data in the program. Please refer to the installation guidance for more instructions. + +### Program Rules { #program-rules } + +The following program rules have been configured for the program: + +|程序规则名称|程序规则说明| +|--|--| +|Assign Empty Value to Class Classification|Automation: Assign Empty Value to Class Classification| +|Assign Event Date|Automation: Assign Event date if to onset date if no Onset date is available| +|Assign 'Laboratory Confirmed Case' to Case Classification|Automation: Assign 'Laboratory Confirmed Case' to Case Classification| +|Assign Onset Date|Automation: Assign Symptoms Onset Date if available| +|Assign 'Probable Case' to Case Classification|Automation: Assign 'Probable Case' to Case Classification| +|Assign 'Suspected Case' to Case Classification|Automation: Assign Suspected Case' to Case Classification| +|Hide Case Classification Field|Hide Case Classification Field until Lab Test question is answered| +|Hide ICU field|Hide ICU field unless Hospitalised| +|Hide 'Imported Case'|Hide 'Imported Case' if not traveled| +|Hide Onset of Symptoms Date|Hide Onset of Symptoms Date if no symptoms| +|Hide Outcome Options|Hide irrelevant Outcome Options| +|Hide 'Specify Local Infection Source'|Hide 'Specify Local Infection Source' unless Local Transmission is selected| +|Hide Test Result Field|Hide Test Result Field until Lab Test question is answered with yes| +|Hide Test Result Options|Hide Irrelevant Test Result Options| +|Hide Unknown Options|Hide Irrelevant Unknown Options| + +You can read more about program rules here: + +[https://docs.dhis2.org/master/en/user/html/configure_program_rule.html](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/configuring-the-system/programs.html#configure_program_rule) + +### Indicators and Program Indicators { #indicators-and-program-indicators } + +From the data captured in the COVID-19 line-listing program, we can calculate the following indicators, including those recommended by the WHO for daily and weekly reporting, present them in a dashboard. All COVID-19 program indicators based on the event program are assigned to the Program Indicator Group ‘COVID-19 Events.’ + +||| +|--|--| +|COVID-19 - Cases admitted in intensive care unit (ICU)|COVID-19 Cases admitted in intensive care unit (ICU)| +|COVID-19 - Cases exposed through healthcare facility|Cases where infection is suspected to have occurred in a health care setting| +|COVID-19 - Cases infected by community transmission|Cases where infection is suspected to have occurred through community spread| +|COVID-19 - Cases infected by household transmission|Cases where infection is suspected to have occurred within the household| +|COVID-19 - Cases infected by local transmission|Cases where infection is suspected to have occurred locally, not in another country| +|COVID-19 - Cases infected through other contact with other infected individual|Cases where infection is suspected to have occurred through other close contact with an infected individual (excluding those listed: household, known cluster, HCF)| +|COVID-19 - Cases linked to known cluster|Cases where infection is suspected to have occurred by linkage to a known cluster of cases| +|COVID-19 - Cases with unknown exposure|Cases where source of infection or exposure is unknown| +|COVID-19 - Deaths|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19-确诊住院病例|Number of confirmed cases that were admitted into hospital| +|COVID-19-进口病例|Cases where likely source of infection is recorded as another country or imported from another country.| +|COVID-19-实验室确诊病例|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by report date| +|COVID-19-实验室确诊病例-症状发作|Suspected cases that were confirmed through laboratory testing (multiple lab tests may be conducted; this indicator assumes that the last test result is "Positive"); displayed by date of onset of symptoms| +|COVID-19-经过实验室测试的案例|Number of suspected cases that received a laboratory test (includes inconclusive lab testing results)| +|COVID-19-可能的情况|Suspected cases with inconclusive laboratory results or not tested for any reason, by reported date| +|COVID-19-可能的病例-症状发作|Suspected cases with inconclusive laboratory results or not tested for any reason, by date of onset of symptoms| +|COVID-19 - Recovered cases|Number of cases that are recovered (By date of onset of symptoms)| +|COVID-19-疑似病例|Total number of cases suspected with COVID-19, by report date| +|COVID-19-疑似病例-症状发作|Total number of cases suspected with COVID-19, by date of onset of symptoms| +|COVID-19 - Suspected cases not tested|Total number of suspected cases without a lab result| +|COVID-19 Event - case fatality rate|COVID-19 related deaths (deaths recorded among all suspected cases)| +|COVID-19按性别和年龄段划分的死亡人数|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|COVID-19按性别和年龄段分类的确诊病例|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| +|按性别和年龄段划分的COVID-19疑似病例|Male, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+
Female, 0-4, 5-14, 15-24, 25-34, 35-44, 45-54, 55-64, 65-74, 75-84, 85+| + +## 引用 { #references } + +* [COVID-19 Surveillance, Response & Vaccine Delivery Toolkit](https://dhis2.org/covid-19) +* WHO Technical guidance on COVID-19 surveillance and case definitions (last updated 20 March 2020) +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) +* WHO Data Dictionary for COVID-19 Case Reporting Form +[https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx](https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx) +* 世卫组织在可疑人类病例中对2019年新型冠状病毒（2019-nCoV）进行的实验室测试（最新更新为2020年3月2日） in-suspected-human-cases 20200117]（https://www.who.int/publications-detail/laboratory-testing-for-2019-novel-coronavirus-in-suspected-human-cases-20200117） +* 世卫组织在调查COVID-19的病例和群中的考虑因素（最新更新于2020年3月13日） -clusters-covid-19]（https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and-clusters-of-covid-19） +* WHO Coronavirus situation reports +[https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/situation-reports) + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md new file mode 100644 index 00000000..243bc1c0 --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__COVID-19-SURVEILLANCE-EVENTS-DISCONTINUED__overview-md @@ -0,0 +1,13 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_EVT/blob/master/docs/overview.md" +revision_date: '2022-11-08' +tags: +- Implement +--- + +# COVID-19 Surveillance Events { #covid-19-surveillance-events } + +## Design { #design } + +[Version 0.3.2](#c19-evt-design) + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md new file mode 100644 index 00000000..2d1d5128 --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__overview-md @@ -0,0 +1,22 @@ +--- +edit_url: "https://github.com/dhis2-metadata/C19_CS/blob/master/docs/c19_surveillance-digital_data_package-2022.md" +revision_date: '2023-09-01' +tags: +- Implement +--- + +# COVID-19 Surveillance { #covid-19-surveillance } + +DHIS2 released a digital metadata package to accelerate case detection, situation reporting, active surveillance and response for COVID-19. The design is inspired by the Ministry of Health Sri Lanka’s pioneering use of DHIS2 tracker for COVID-19 case detection and draws on years of collaboration with the World Health Organisation (WHO) to develop information system standards for case-based disease surveillance. The COVID-19 digital data package includes standard metadata aligned with the WHO’s [technical guidance on COVID-19 surveillance and case definitions](https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidance/surveillance-and-case-definitions) and implementation guidance to enable rapid deployment in countries. + +The design of these modules can be adapted, modified and reused for new and emerging infectious disease threats to strengthen health emergency preparedness and response systems in countries. + +## COVID-19 Surveillance Modules { #covid-19-surveillance-modules } + +DHIS2 supports surveillance workflows and automated analysis for key components of routine and active surveillance: + +* **COVID-19 Case Surveillance tracker**: enrolls & tracks suspected cases; captures symptoms, demographics, risk factors & exposures; creates lab requests; links confirmed cases with contacts; and monitors patient outcomes. This package can be installed as a standalone COVID-19 package or can be integrated into a country’s existing integrated disease surveillance & response tracker. +* **Contact Registration & Follow-up tracker**: strengthens active case detection through contact tracing activities, such as identification and follow-up of contacts of a suspected or confirmed COVID-19 case. +* **Ports of Entry Screening & Follow-up tracker**: enrols travellers who have visited high-risk locations at Ports of Entry for 14-day monitoring and follow-up. +* **COVID-19 Aggregate Situation Reports**: an aggregate reporting dataset that captures minimum necessary data points for daily or weekly reporting and includes key information for generating situation reports. + diff --git a/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__COVID-19-SURVEILLANCE__release-note-md new file mode 100644 index 00000000..1cfdac6a --- /dev/null +++ b/projects/docs-full-site/zh/IMPLEMENT__HEALTH__DISEASE-SURVEILLANCE__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: +- Implement +--- + +# Release Note { #c19-cs-release-note } + +## 1.0.2 { #102 } + +### 总览 { #overview } + +我们对现有软件包进行了一些更新以与新的COVID-19 [WHO于2020年3月20日发布的监视准则]保持一致（https://www.who.int/emergencies/diseases/novel-coronavirus-2019/技术指导/监视和案例定义），并在整个支持包中引入了新组件。如有任何疑问，请在此处查看注释，并在[实践社区]（https://community.dhis2.org/c/implementation/covid-19/）中的COVID-19讨论板上与我们联系。 + +**可以从[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. + +新版本包括： + +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. 更新元数据代码以使其与[WHO基于病例的报告数据字典]保持一致（https://www.who.int/docs/default-source/coronaviruse/2020-02-27-data-dictionary-en.xlsx） +2. 更新了计划指标以反映世卫组织针对可能病例的新病例定义（请参考2020年3月20日更新的临时监测指南中的更新病例定义[世卫组织2020年3月20日更新的临时监测指南]（https://apps.who.int/ iris / bitstream / handle / 10665/331506 / WHO-2019-nCoV-SurveillanceGuidance-2020.6-eng.pdf）） +3. 更新了年龄传奇，以符合WHO每周报告的新指南 +4. RelationshipType已添加到元数据包 +5. 对元数据进行了较小的修复，以使程序包的安装更加容易（即，indicatorType UID与聚合程序包中包含的指示器类型相匹配） + +### COVID-19 Contact Registration & Follow-up Tracker { #covid-19-contact-registration-follow-up-tracker } + +1. 添加了一个新的程序阶段，以使案例联系人可以重复地进行“跟进”。添加此信息是为了反映在乌干达和多哥实施的工作流，在此过程中，可以在14天内对联系人进行重复监视，以确定是否有症状。 ***计划***基于WHO指南，可在[此处]找到（https://www.who.int/internal-publications-detail/considerations-in-the-investigation-of-cases-and -clusters-of-covid-19），以及通过[OpenWHO]（https://openwho.org/courses/introduction-to-ncov）网站获得的信息。 +2. 更新了年龄传奇，以符合WHO每周报告的新指南 +3. RelationshipType已添加到元数据包 +4. 对元数据进行了较小的修复，以使软件包安装更加容易 + +### COVID-19总体监视报告 { #covid-19-aggregate-surveillance-reporting } + +进行了以下更新以反映[2020年3月20日更新的WHO指南]中的新指南（https://apps.who.int/iris/bitstream/handle/10665/331506/WHO-2019-nCoV-SurveillanceGuidance-2020.6- eng.pdf），包括向WHO提交的最新全球汇总报告（每周和每天） + +1. 根据新年龄段更新了年龄类别 +2. 新指标增加了确诊病例中男性比例和确诊死亡中男性比例 +3. 根据更新的世卫组织每周报告指南，新的每周数据集可捕获一级国家以下水平的传播分类（即省级-可以根据国家/地区分配给任何二级国家以下水平） +4. 对元数据进行了较小的修复，以使软件包安装更加容易 + +### Points of Entry Tracker [***DISCONTINUED***] { #points-of-entry-tracker-discontinued } + +入境点跟踪程序计划用例旨在支持对有国家/地区/领地旅行历史或居住地的国家/地区报告COVID-19本地传播的旅行者进行注册，并可能需要对其进行跟进确保没有症状出现。它基于HISP斯里兰卡实施的设计，通过少量更改来支持斯里兰卡卫生部，以使该程序在全球范围内更通用，并与COVID-19软件包中的其他跟踪程序保持一致。该一揽子计划支持世卫组织[入境处疾病管理技术指南]中详细介绍的入境点干预措施（https://www.who.int/emergencies/diseases/novel-coronavirus-2019/technical-guidedance /进入和聚集的点数）。 + +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/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md index 164b36b4..067d694f 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__audit-md +++ b/projects/docs-full-site/zh/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: -- Manage - DHIS核心 主版 +- Manage --- # 审核 { #audit } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md index c846b969..2733718f 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__debugging-as-another-user-md +++ b/projects/docs-full-site/zh/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: -- Manage - DHIS核心 主版 +- Manage --- # 使用 DHIS2 中的用户模拟功能{ #user_impersonation } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md index cd5b2270..9297c6c5 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__installation-md +++ b/projects/docs-full-site/zh/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: -- Manage - DHIS核心 主版 +- Manage --- # 安装 { #installation } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md index fff94635..a1c3fccf 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__monitoring-md +++ b/projects/docs-full-site/zh/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: -- Manage - DHIS核心 主版 +- Manage --- # 监控 { #monitoring } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md index 504c71fb..0ba0a2fd 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__upgrading-md +++ b/projects/docs-full-site/zh/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: -- Manage - DHIS核心 主版 +- Manage --- # 正在升级 { #upgrading-dhis2 } diff --git a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md b/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md index af161168..6b8ad986 100644 --- a/projects/docs-full-site/zh/MANAGE__PERFORMING-SYSTEM-ADMINISTRATION__DHIS-CORE-VERSION-MASTER__using-gateways-for-sms-reporting-md +++ b/projects/docs-full-site/zh/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: -- Manage - DHIS核心 主版 +- Manage --- # 使用网关进行SMS报告 { #sms_report_sending } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md index cea2cda8..a17352f1 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__browsing-md +++ b/projects/docs-full-site/zh/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: -- App version 1.0 - 使用 +- App version 1.0 --- ## 浏览动作跟踪器 { #browsing-the-action-tracker } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md index 0c8dd174..4f8f1490 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__DASHBOARD-AND-DEMO-SERVER__introduction-md +++ b/projects/docs-full-site/zh/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: -- App version 1.0 - 使用 +- App version 1.0 --- # 链接的Action Tracker仪表板和演示服务器 { #linked-action-tracker-dashboard-and-demo-server } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md index 177730fc..4eff7449 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__MAINTENANCE-AND-SUPPORT__maintenance-md +++ b/projects/docs-full-site/zh/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: -- App version 1.0 - 使用 +- App version 1.0 --- # Action Tracker应用维护 { #action-tracker-app-maintenance } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md index eab47661..46007180 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-planning-md +++ b/projects/docs-full-site/zh/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: -- App version 1.0 - 使用 +- App version 1.0 --- # 动作跟踪器中的动作计划 { #action-planning-in-action-tracker } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md index f36c3d5b..f16d01e6 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__ACTION-TRACKER-APP__APP-VERSION-10__PLANNING-TRACKING-AND-ANALYZING-ACTIONS__action-tracking-md +++ b/projects/docs-full-site/zh/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: -- App version 1.0 - 使用 +- App version 1.0 --- # 动作跟踪器中的动作跟踪 { #action-tracking-in-action-tracker } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md index 98c70a5a..5f59c66f 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__installation-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 安装BNA应用程序 { #installing-the-bna-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md index 2166f381..57c171f4 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INSTALLATION-AND-CONFIGURATION__maintenance-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # BNA 应用程序维护 { #bna-app-maintenance } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md index 2606928e..bcc1538f 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__analysis-and-interpretation-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # BNA 分析和解释 { #bna-analysis-and-interpretation } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md index ab4883f9..2f2d89aa 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__app-architecture-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # BNA 应用架构 { #bna-app-architecture } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md index daf588de..6bf76278 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__dashboard-and-demo-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 瓶颈分析仪表板和演示服务器{ #bottleneck-analysis-dashboard-and-demo-server } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md index 58b3f6f2..f3b930d9 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__navigating-the-app-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # BNA 应用干预配置{ #bna-app-interventions-configurations } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md index d3e664f1..f8be9d38 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__INTRODUCTION-AND-USAGE__visualization-operations-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 可视化操作{ #visualization-operations } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md index cf2c9010..10d360f4 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__adopting-the-bna-app-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 采用 BNA 应用程序{ #adopting-the-use-of-the-bna-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md index db5e6ac4..be993e1e 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__capacity-building-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 能力建设 { #capacity-building } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md index d5b646d4..070c3cae 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__end-user-training-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 最终用户培训 { #end-user-training } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md index 6e4e25ef..a7499dd9 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__implementation-overview-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # BNA 应用实施指南 { #guide-to-bna-app-implementation } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md index c641cf7b..ef5ae93f 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__integration-concepts-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # BNA 应用程序的集成概念。 { #integration-concepts-for-the-bna-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md index 94ae825d..c8e2a7da 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__opportunities-and-challenges-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 机遇与挑战{ #opportunities-and-challenges } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md index 20231ea3..de4ef37f 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__planning-and-organising-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 规划和组织{ #planning-and-organising } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md index 7aef100e..65789eb2 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__setting-up-the-app-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 设置新的 BNA 应用{ #setting-up-a-new-bna-app } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md index 4e460bac..3b9d9306 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__support-and-scale-up-md +++ b/projects/docs-full-site/zh/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: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # BNA 应用程序支持和扩展{ #bna-app-support-and-scale-up } diff --git a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md b/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md index dde12d03..9c5212a1 100644 --- a/projects/docs-full-site/zh/USE__OPTIONAL-APPS__BOTTLENECK-ANALYSIS-APP__APP-VERSION-122__USER-IMPLEMENTATION__sustainability-md +++ b/projects/docs-full-site/zh/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: '2021-09-09' tags: -- App version 1.2.2 - 使用 +- App version 1.2.2 --- # 扩大规模和可持续性{ #scale-up-and-sustainability }