Trainer’s Guide to Program Indicator Analysis¶

What is this guide?¶

This guide is a support document for DHIS2 Academy trainers for the session “Program Indicator Analysis.” This session follows the standard Academy training approach with

1. a live demo session where the trainer demonstrate and explain the features, and

2. praktické sezení se cvičeními, kde si účastníci procvičí stejné funkce.

This guide will help the trainer​ prepare​​ for the live demo session. The “Live Demo step by step” section has a detailed walkthrough of all the steps to demonstrate with explanations and screenshots that should be easy to follow.

K dispozici je také Rychlý průvodce, který uvádí kroky velmi stručně a je míněn jako průvodce vyhledáváním nebo „cheatsheet“ BĚHEM dema, aby si trenér zapamatoval všechny kroky a průběh dema.

Learning objectives for this session¶

1. Popište, co je indikátor programu
2. Describe how program indicators are calculated
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
6. Understand the limitations behind using program indicators

Time Requirements¶

• Live Demo: 3 demos, ~10 mins each
• Hands-on Exercises: 3 exercises, ~10mins each
• Assignment: 30 mins multiple choice

Pozadí¶

Program Indicators offer a flexible way of interacting with tracker data and allow for a number, of advanced functionality as it relates to aggregating or summarizing individual tracker data. This session will focus on how program indicators can be used in data visualizer, maps and event reports to both display information related to a single tracked entity as well as summarize data for many tracked entities based on the org unit and period you are working with.

Preparations¶

This session will see you creating a number of visualizations. Ensure that you have run analytics in the demo database you are using and that all the data is being populated correctly. If you find that data is not present for the correct period or year, please contact the training content team so we can advise how to move the data correctly.

Před prezentací byste měli zvážit, jak si celé demo projít. Poté byste si měli vzít stručnou příručku a doplnit ji o další poznámky, které jste si udělali během procházení ukázky. Pokud zjistíte jakékoli změny, které mohou být vyžadovány, nebo dodatečné vysvětlení, které by mohlo být užitečné v rámci relace, uveďte prosím obsah týmu školení, abychom mohli vyhodnotit, jak nejlépe začlenit tuto zpětnou vazbu do materiálu.

Každá vizualizace, o jejíž vytvoření budete požádáni, byla uložena a měla by být sdílena pro veřejné zobrazení. Pokud si nejste jisti obsahem některého z vizualizací, můžete si každou otevřít a zkontrolovat, jak byla vytvořena.

Also, the learner's guide and session summary are the main material that will be provided to the learner's with both detailed steps for ungraded exercises as well as the key messages from the session. Review these as well to ensure you are able to discuss these key points during your demonstration.

Best Practices¶

Před zahájením demonstrace mějte prosím na paměti, že nejdůležitější je, aby je publikum sledovalo, takže nezapomeňte publiku položit otázky, abyste si ověřili, že je sledují. Pokud je něco nejasné, vraťte se a projděte si to pomalu. Pokud nemáte čas na všechny kroky, je lepší některé kroky zkrátit, než jít rychle, zatímco nikdo nerozumí.

V online prostředí budete pravidelně dělat přestávky, abyste jim umožnili provádět různá neklasifikovaná cvičení, abyste udrželi pozornost.

In an in-person setting, the participants may be doing the demo with you at the same time. In this scenario, it is ideal if there are other trainer's moving around the room to support participant's as it will be difficult for the trainer leading the session to answer many individual questions during the demonstrations.

Quick Guide¶

1. In data visualizer, create a pivot table using an event program indicator from Malaria case notification program
2. Typ vizualizace: Kontingenční tabulka
3. Data
4. Typ dat: Indikátor programu
5. Program : Malaria case notification,investigation and response
6. Program Indicator : MAL- CS - Cases detected through PCD
7. Období: Posledních 6 měsíců

8. Org Unit : User sub-units

9. Create a chart using program indicators from different program stages from Malaria case notification program

10. Typ vizualizace: Spojnicový graf
11. Data
12. Typ dat: Indikátor programu
13. Program : Malaria case notification program
14. Program Indicators :
    • MAL-CS- Confirmed malaria cases
    • MAL-CS- Indigenous (Local)
15. Období: Tento rok

16. Org Unit : User sub-units

17. Explain the visualization and where the data is coming from. Note that this type of chart can not be made in event visualizer.

18. Convert the chart to a pivot table. Note that this type of table can not be made in event reports.
19. Convert the table to a map. Note that you are now using the thematic layer to display your data, which has different options available compared to the event and TEI layer.

STOP! Have them perform Exercise 1 in the learner's guide.

1. Vytvořte mapu pomocí tematické vrstvy s následujícími vstupy:
2. Layer Type : Thematic
3. Data:
4. Item Type : Program Indicators
5. Program : Malaris case notification program
6. Program Indicator : MAL-CS-Female
7. Leave the aggregation type as default
8. Period:
9. Period Type : Relative
10. Období: Posledních 6 měsíců
11. Display Periods : Timeline
12. Org Units : User sub-units
13. Filter : None
14. Style : Bubble Map, Single Color Legend

Highlight the additional options available when using the thematic layer via program indicators

STOP! Have them perform Exercise 2 in the learner's guide.

1. Create a line list showing the number of relationships by TEI from the Case-based Surveillance Program. Create a line list table with the following inputs:

2. Input Type : Enrollment

3. Program Dimesions
4. Program :Case-based Surveillance
5. Data
   • Attributes : Given name, Family name
   • Data Element: Other Sign/Symptoms
   • Program Indicator: Contacts
6. Org Unit : 0001 CH Mahosot

7. Time Dimension : Date of notification (this is the enrollment date)

8. Explain the report and the program indicator you have added to this report

9. Add the program indicator for days between symptoms onset and consultation

10. Add a condition for days between symptoms onset and consultation >= 0

11. In data visualizer, create a bar chart showing the average days between onset and consultation across all level 3 OUs within Vientiane Capital

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

Clean the chart by hiding the empty categories using the options menu.

STOP! Have them perform Exercise 3 in the learner's guide.

1. Review the recap slide
2. Have them perform the assignment

Live Demo step by step¶

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

Open the table "MAL - CS - Cases detected through PCD Last 6 months." This is the table that you will create. The data item is a program indicator that is counting the # of malaria cases that meet said criteria. You can explain the layout to the participants before continuing.

Clear your inputs by going to Favorites -> New.

In the first example, you will 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

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

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¶

A gap that we can address when compared to other methods of working with event/tracker data is creating a pivot table, chart or map using aggregated data from different program stages. We can do this in data visualizer for any of the available visualizations using either event or enrollment type program indicators and is not something we could achieve in either event reports or event visualizer (though we can make line lists using data from different program stages in the line listing app).

Open the chart "MAL - Confirmed malaria cases and Confirmed malaria cases classified as indigenous." This is the chart that you will create.

This chart is showing data from seperate stages together. The diagnosis is confirmed in Stage 1 of this program, while the classification occurs in Stage 4 of this program.

You can explain this to the participants before continuing.

Clear your inputs by going to Favorites -> New.

V tomto příkladu vytvoříme spojnicový graf s následujícími vstupy:

• 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:

The chart should look like this

This chart uses event 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.

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.

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.

STOP! Have them perform Exercise 1 in the learner's guide.¶

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

In the maps session, we had discussed how we can use the event and TEI layer to map raw tracker data (also known as event data items). While we can also use the thematic layer when dealing with tracker data, this is often less useful as the number of numeric data elements in a tracker program may be limited.

Pomocí programových indikátorů jsme však schopni výrazně rozšířit funkcionalitu map o data trasovače, protože můžeme využít plný potenciál tematické vrstvy. To zahrnuje vytváření rozdělených pohledů a map časové osy a používání dostupných možností stylu (jako je vytváření choropletových a bublinových map), které nejsou dostupné při použití událostí a vrstvy TEI jako příkladů.

Open the map "MAL-CS- Female cases, last 6 months." This is the map that you will create. You can explain the layout to the participants before continuing.

Clear your inputs by going to Favorites -> New.

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

Period Tab

Org Units Tab

Style Tab

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

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).

STOP! Have them perform Exercise 2 in the learner's guide.¶

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 demonstrate 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

Open the table "CBS - Contacts by Person." This is the table that you will create. You can explain the layout to the participants before continuing.

Clear your inputs by going to Favorites -> New.

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)

The table should look like this

Emphasize that you are able to select program indicators from the program dimensions tab; however some program indicators may not work as intended or not give you any meaningful output depending on how they have been configured. For example, for a single TEI, any count based indicators within a single, non-repeatable program stage may not be so helpful as the maximum value they can return is 1 for a single TEI.

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.

(note : a likely follow up question may be if we can list the individuals they have relationships with; this is not possible and requires a custom app or report)

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"

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.

Update your table.

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¶

Jak bylo uvedeno výše, tyto typy indikátorů programu mohou fungovat na dvou úrovních. Přezkoumali jsme, jak můžeme používat různé typy indikátorů programu na individuální úrovni, nyní můžeme použít stejný indikátor programu a vytvořit souhrnný výstup.

K tomu použijeme vizualizér dat.

Note: Program indicators are available to select within event visualizer but they often do not result in any output. It is best to use data visualizer to create charts when using program indicators.

Open data visualizer.

Open the chart "CBS - Average days between symptoms onset and consultation, this year." This the chart that you will create. You can explain the layout to the participants before continuing.

Clear your inputs by going to Favorites -> New.

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

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

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

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

The chart should look like this after you update it.

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.

STOP! Have them perform Exercise 3 in the learner's guide.¶

Recap¶

Před provedením úkolu si s nimi na konci sezení prohlédněte rekapitulační snímek

Assignment¶

After you have completed all demos and they have finished the exercises, have them complete the graded assignment for this session. If you find you are running out of time, assign the graded assignment to them and ask them to complete it outside of the live scheduled session.