Přeskočit obsah
For the complete DHIS2 documentation index, see llms.txt.

Learner's Guide to Program Indicator Analysis

What is this guide?

This guide contains all exercises and detailed steps to perform them related to program indicator analysis session for the academy. Please perform each of the exercises when prompted to by your instructors.

Learning objectives for this session

  1. Popište, co je indikátor programu
  2. Popište, jak se odvozují indikátory programu
  3. Popište rozdíl mezi indikátory programu události a zápisu
  4. Pochopte, jak mohou programové indikátory vyplnit mezery v analýze dat trasovače, které se vyskytují v jiných vizualizačních nástrojích
  5. Vytvářejte vizualizace pomocí programových indikátorů odvozených z dat trasovače

Exercise 1

Create a pivot table in data visualizer using a program indicator from the Malaria case notification,investigation and response program

Create a simple pivot table using a single program indicator in data visualizer. It will have the following inputs:

  • Typ vizualizace: Kontingenční tabulka
  • Data
  • Typ dat: Indikátor programu
  • Program : Malaria case notification,investigation and response
  • Program Indicator : MAL- CS - Cases detected through PCD
  • Období: Posledních 6 měsíců
  • Org Unit : User sub-units

Rozložení může vypadat takto

table1_layout

The table should look like this (the months shown may differ as its relative to the current date)

underlying_conditions

This is a program indicator that is pulling its information from the data element "Detection setting." This data element consist of an option set. This program indicator is therefore aggregating the events which meet the criteria for PCD.

Create a chart using event indicators from different program stages from the Malaria Case notification program

Create a line chart with the following inputs:

  • Typ vizualizace: Spojnicový graf
  • Data
  • Data Type : Program Indicators
  • Program : Malaria case notification program
  • Program Indicators :
    • MAL-CS- Confirmed malaria cases
    • MAL-CS- Indigenous (Local)
  • Období: Tento rok
  • Org Unit : User sub-units

Chcete-li vytvořit tento graf, ujistěte se, že vaše rozložení vypadá takto:

chart2_layout

The chart should look like this

chart2

This chart uses event type indicators, including combining data from Stage 1 (Diagnostic and Treatment), where it gets the data on whether or not a confirmed Malaria case, and Stage 4(Case outcome), where it gets the information on whether the case is Indigenous (local).

It is not possible to create this type of output using event visualizer (you can not pull data from multiple stages using event visualizer).

You can convert this chart to a pivot table so they can see that you can also create a pivot table using data from multiple stages, an option not possible in event visualizer/reports.

table2

Nakonec můžete tuto tabulku otevřít jako mapu a ukázat, že nyní můžete používat tematickou vrstvu. Tematická vrstva otevírá řadu dalších možností při práci s vašimi daty (příklad, kdy vytvoříme mapu od nuly pomocí programového indikátoru v tematické vrstvě, si projdeme v další části tohoto sezení).

To provedete výběrem možnosti „Otevřít jako mapu“ z výběru vizualizace.

table2_conversion

When you open this as a map, you will have to select one of the data items used in the chart/table as your primary layer (you can select all but since they are all displaying data at the same OU level, you will in effect only see data from the top layer). Select one of the event indicators (MAL-CS-Confirmed malaria cases) using data from multiple stages to demonstrate that this type of data can be mapped.

map2_select_data

map2_select_data

Exercise 2

Create a map using a program indicator from the Case-Based Surveillance program

Vytvořte mapu pomocí tematické vrstvy s následujícími vstupy:

  • Layer Type : Thematic
  • Data:
  • Item Type : Program Indicators
  • Program : Malaris case notification program
  • Program Indicator : MAL-CS-Female
  • Leave the aggregation type as default
  • Period:
  • Period Type : Relative
  • Období: Posledních 6 měsíců
  • Display Periods : Timeline
  • Org Units : User sub-units
  • Filter : None
  • Style : Bubble Map, Single Color Legend

Data Tab

map5_data

Period Tab

map5_period

Org Units Tab

map5_OU

Style Tab

map5_style

The map should look like this (note that the months displayed may be different as the period is relative to the current date)

map5

You can play back the timeline map. You will see over time the monthly values are increasing or decreasing (the map is showing the total number per month, not the cumulative number; cumulative can be shown however the indicator needs to be configured differently).

Exercise 3

In the line listing app, create a line list, enrollment report showing the number of relationships by TEI from the Case-based Surveillance Program

Program indicators can be used in event reports, line listing and event visualizer as well as within data visualizer and maps, depending on how they are defined. This is because one program indicator can work on two levels:

  1. Through creating a summary output for a single TEI
  2. Through creating a summary output for all TEIs within a period/org unit

We will use these principles using two program indicators that use "Average" as the aggregation type.

  1. Contact tracing program
  2. Summarizes the total number of contacts a single TEI has through the relationships that have been created in tracker capture
  3. Summarizes the average number of contacts for all TEIs based on their enrollment date and the specified period and organisation unit
  4. Case based surveillance - days between onset and consultation
  5. Summarizes the total number of days between onset of symptoms and their initial consultation date for single TEI
  6. Summarizes the average number of days between onset of symptoms and initial consultation date for all TEIs based on their enrollment date and the specified period and organisation unit

Create a line list table with the following inputs:

  • Input Type : Enrollment
  • Program Dimesions
  • Program : Case-based Surveillance
  • Program Dimensions
    • Org Unit : 0001 CH Mahosot
    • Time Dimension : Date of notification (this year)
    • Attributes : Given name, Family name
    • Data Element: Other Sign/Symptoms
    • Program Indicator: Contacts

Note : here is the location of the org unit in case you are unfamiliar with this hierarchy (01 Vientiane Capital -> 0101 Chanthabouli -> 0001 CH Mahosot)

chw_mahosot

The table should look like this

table3_contacts

Sort the table by the "Contacts" column. This is showing the number of contacts each person has had as defined through adding relationships via tracker capture.

Add the program indicator "CBS - Days between onset and consultation" to your report and update your line list

From the program dimesions tab, add the PI "CBS - Days between onset and consultation"

days_between

Set the Condition : Days between onset and consultation >= 0

To set the condition select the "Days between onset and consultation" program indicator. From here, you can define the condition.

condition

Update your table.

table3_contacts_days_btwn

We now have an additional program indicator which is showing the number of days between each person's onset of symptoms and their initial consultation.

Create a bar chart showing the average days between onset and consultation across all level 3 OUs in VC

Ve vizualizéru dat vytvořte graf s následujícími vstupy:

  • Typ vizualizace: Sloupcový graf
  • Data
  • Typ dat: Indikátor programu
  • Program : Case-based Surveillance Program
  • Program Indicator : CBS - Days between onset and consultation
  • Období: Tento rok
  • Org Unit : Level 3 (District) OUs within Vientiane Capital

Poznámka : zde je umístění organizační jednotky pro případ, že tuto hierarchii neznáte

chart4_OU_selection

A zde je rozložení, které by mělo být použito pro graf

chart4_layout

You can remove the empty categories to clean up the chart.

Go to options -> data -> hide empty categories -> all

hide_empty_categories

The chart should look like this after you update it.

chart4

Když se podíváme na tento graf, již nevidíme hodnoty, které jsou reprezentativní pro jednu jednotlivou osobu, ale pomocí stejného indikátoru jsme schopni vzít průměr pro všechny jednotlivce v rámci organizačních jednotek a období, které jsme vybrali.

Summary on these two indicators

Z těchto dvou příkladů programových indikátorů můžeme vidět, že programové indikátory mohou mít více funkcí na individuální i agregované úrovni. Tyto různé funkce mohou být docela užitečné v závislosti na tom, jaké informace chcete v systému zkontrolovat. Při použití těchto typů indikátorů je k dispozici mnoho dalších pokročilých možností. Nejlepším zdrojem těchto informací bude dokumentace.