One of the recurring challenges in information system design is collecting large volumes of data that are never meaningfully used. This increases reporting burden and can ultimately affect data quality and use.
In this short video, I briefly explore why indicators matter in DHIS2 and how they help guide more purposeful data collection and decision-making.
Watch here:
This builds on some of the foundational DHIS2 concepts I’ve been exploring recently, including structuring Organisation Units in DHIS2.
I would love to hear how others approach balancing reporting needs with keeping systems simple and usable. Please feel free to comment below.
Finally, for those interested in following the series, you can find the next post here below:
The short video is really fun to watch. I saw the time is only 52 seconds and I told myself, I wish I could explain indicators in 52 seconds.
Well said, indicators are an important aspect of making use of data (though I’ve read about implementations that use 1000s of indicators so if not properly utilized, they too would become a burden).
Looking forward to more!! Thanks for your continuous contribution to the community.
Watch here:
