Webinar on Tracker Implementation Considerations, Wednesday 28 April - Q&A thread - Add your questions and comments below

Hi Mahmud

Unfortunately there is no way to immediately ASSIGN a value to an TEI Attribute while you are updating a program stage. You would need to again open the registration form with the TEI Attributes.

This is by design: here is an explanation from Markus

Of course there may be workarounds with custom scripts etc to update the TEI attribute via a PUT request, depending on the use case, but there is no built-in solution. Perhaps you could consider a warning box in the program stage to ask the user to update the TEI attribute. There is also the option to ASSIGN the TEI attribute value to a data element when the program rule is executed.

1 Like

The answer to this question really depends on how you transfer data between your Tracker and Aggregate instances.

One simple manual approach might be a program stage notification which would send a message to the data manager when a program stage is completed – they could then re-run analytics tables and re-send data to the aggregate dataset.

If you configure this message to send based on program rules, you could possibly even trigger the message if the event date is within the reporting window, but the current date is X days after the aggregate of reporting window.

Again, custom scripts are on option but it depends on your tracker->aggregate workflow.

1 Like

Hey there @paulyvan
Exporting all the data for a repeating event in one line represents a challenge and can not be done with todays tools - not in the way you describe at least.

For the new line list app being developed, we are considering ways of meeting this challenge and making it possible to line list TEI with columns for data from different events. The mechanism will probably involve making a definition of columns in the line list that defines wether to load data for the first, last or perhaps a differently specified event within the repeating stage. This is a release or two away though, and haven’t got a finished design. It would be useful to know your full use case for the process of designing this feature.

When it comes to workarounds, there is 2 paths I can think of. One would be to create a program indicator and use the d2:count***() functions that @Brian mentions in another post above. The other is using SQL views and producing your report with custom SQL.


1 Like

Hey @paulyvan ,
To help we might need some more details. What endpoint or what app is the data exported from?
Are you sure the program stage that ends with “0dzh” is not a single event program?


1 Like

Good. I think what is actually in customisation will help.

While waiting for that solution, can you please send me the SQL request to do it?

Hi Abdul Rahman

The Tracker Implementation Academy registration is available on Level 2 Academies | DHIS2

It will be held from 25 May to 4 June. Do not hesitate to register!

I used Event report app.
And it is the Program Instance id which end with “0dzh” not the program stage. Look down and see the column of the repeatable program stage.

Dear all

The recording of the webinar is available here.

This webinar marked the start of our 2021 Level 2 Tracker Implementation Academy programme.

Because our goal is to put more emphasis on real-world skills and projects, this training programme will also include a 10-day level 2 Academy on 25 May - 4 June. This Academy is targeting those responsible for implementing Tracker: program managers, training and health leads, decision makers and implementers.

More information and registration available here

1 Like

Academy Overview and Logistics 2021 Q2

Academy overview
Logistics and Agenda Review
Introduction to course purpose and learning objectives

Introduction to Slack
New Badges for the Academy participants
Attendance and certification “Word of the day concept”
Academy resources

Tracker Use Cases Part 1 2021 Q2

Tracker Use Cases Part 2 2021 Q2

Are the certificates for the initial DHIS2 Maps & GIS Workshop ready yet?

Hi Tebogo

We had a bit of a delay so I will make sure to send these next Monday.

Apologies for the delay


1 Like

Thank you Alice

Tracker Reviewing requirements, Android Considerations part 1

Ghana use case at: https://youtu.be/VJc5anXcInc?t=1319 Android Presentation by Jaime: https://youtu.be/VJc5anXcInc?t=3431 Key issues: Defining the indicator requirements Designing a tracker program for data use Joint analysis of tracker and aggregate data Essential vs non-essential data

Tracker Reviewing requirements, Android Considerations part 2

Key Android considerations
Pamod from HISP Sri Lanka presentation

Identifying configuration management and long-term maintenance strategies 2021 Q2

Markus UiO

Dr. Prosper HISP Uganda

Release cycle and upgrades
Modifications and Updates
Access control for system administration

eRegistry and Client Support 2021 Q2

Tracker Implementation Management YouTube playlist

Using Tracker to add individual-level data to your DHIS2 system allows you to enhance your data analysis and potentially streamline processes at the point of care, but it also adds to the complexity of your DHIS2 system. This Academy will help you prepare and plan for your Tracker projects, to give you a better understanding of how to perform internal readiness assessments, navigate legislation and policy concerns, set up and train your core team, and build a long-term implementation plan. The goal for the academy is for each participant to leave with a framework for how to assess and plan their Tracker project.

Themes of this Academy include:

Review Tracker features and real-world use cases
Overview of how to design implementations for high-quality analytics outputs
Discuss strategies for capacity building
Learn frameworks for outlining implementation requirements
Review of security considerations
Review of system assessment frameworks
Develop an implementation / maintenance plan
Prerequisite: This is not a technical “how to” Academy on configuring a Tracker instance. No prior hands-on experience with DHIS2 is required. Rather, participation requires that you have a position of responsibility for planning, overseeing or maintaining a Tracker project – to include project and program managers, tech leads and architects, HMIS managers, DHIS2 development partners, and others with similar responsibilities.