We are currently reviewing our community-level coverage approach.
Here are the options we are considering:
Adding one or two methods for sorting households and/or household members, based on the data collected (for example, indicators related to maternal health or immunization).
Modifying the icon and number currently used to represent visits (UHC) to display an icon and a value calculated from the data collected within the household (again, related to maternal health or immunization).
Achieving these objectives would significantly strengthen maternal health and immunization monitoring activities in our communities.
However, several technical questions remain:
Is it possible, via configuration, to add new filters for households and their members, based on the data collected?
Can we replace the existing UHC icons and counters for households with icons and values ​​derived from the data collected?
Can all of these modifications be carried out without modifying the CHT code?
Thank you so much for sharing this — these are really valuable use cases for community-level health monitoring, and these are exactly the kinds of improvements that can make a real difference for health workers and the families they serve.
To give you a straightforward answer: currently, none of the three items you described can be achieved through configuration. Custom household/member filters based on collected data, replacing UHC icons with calculated values, and doing so without code changes are all outside what the platform supports today.
However, this is a great opportunity. The needs you’ve outlined are concrete and clearly tied to real workflows. I’d love to see this turned into a feature request or a collaborative proposal — there may well be other partners and community members with similar needs, and working together we can build a strong case for prioritizing this work.
Hello @diana ,
Thank you very much for this clear and encouraging feedback.
It’s great to hear that these use cases are recognized as valuable
We would be glad to contribute to a feature request or collaborative proposal. Could you please let us know what the next steps would be, or how we can best support the process?
We are fully open to working together to help move this forward.
Thank you for your willingness to contribute — that’s exactly the kind of engagement that moves things forward.
I believe there are two distinct features to define here:
Household/member filters based on collected data
Configurable UHC icons that reflect calculated values from collected data
To shape these into defined feature requests, it would help a lot if you could provide concrete examples for each. For instance: what specific filters would be most useful for health workers in their daily workflow? And which collected data points should drive the UHC icon and value?
The more explicit the use cases, the easier it will be to define a clear deliverable. From there, the likely next steps would be to submit feature requests in the CHT and gauge community interest, with the goal of forming a squad to carry the work forward.
As requested, here are two concrete examples that illustrate the types of features we are hoping to support in the field:
1. Example of a household/member filter
A useful filter for CHWs would be one that sorts households based on the number of pregnant women.
This information would come from the pregnancy and planning forms.
Such a filter would help CHWs quickly identify households with the highest maternal‑health needs.
2. Example related to configurable UHC icons
For UHC icons, one relevant use case would be highlighting households that have children of eligible age requiring vaccination checks.
We could display a specific icon next to these households and show the corresponding number.
The underlying data would rely on the the vaccination‑verification form for each eligible child.