Hi everyone !!
I have a scenario where i am facing a issue related to compliance.
so the scenario is this i have a health Facility which was open for 3 months lets say from Jan to Feb and its compliance was okay . but then it was non functional for 2 months. and now it will be functional again . but the case is that when it will be open and assigned to the dataset it will show compliance also for the 2 months that in which it was inactive. now i want that it should only show compliance for the 3 months it was active and then skip the inactive period and then show again from now on .what can i do to achieve this .
Are these HF opening and closing at random times (unexpected times), or do you have a specific time for when they open and close? Is this only for specific OUs? If this is common across all the similar HFs that use the dataset you might want to consider the ‘Data input periods’ in the Dataset metadata configuration
If I understand your situation correctly, you are looking for a way to “pause” the expected reporting for some OUs for a certain months rather than having one opening/closing date? As I mentioned above, this is available if you use the ‘data input periods’ in the dataset configuration; however, it will apply for all the OUs that the dataset is assigned to.
We might need to create a feature request for this, you’re welcome to create the idea and link to this discussion topic, please see ideas for detailed instructions.
I have a workaround in mind but I’d like you to consider first the official (standard) way for handling this so please wait and see if we receive a better suggestion.
The unofficial way that I have in mind is that to create sub-OUs for these HFs where each sub-OU has a specific opening/closing date; therefore, when checking the analytics reporting rate, you will check for the HF and it will not consider any month as ‘skipped’.
For instance, your HF could have two second level OUs, one which has opening date for the 3 months it was active and closing date before the 2 months it became inactive; on the other hand, the other OU will have the opening date after those 2 months. Now when you check the reporting rate at the HF level, it will check for the two OUs without considering the two months in-between since those two months no OU was open.
I hope this suggestion helps, but either way, I’ll ask and triage to the team to see what are the available options and how this situation could be handled. Please do feel free to create the feature request.
Hi @Tahir_Zaman
There is really not a great way to achieve this I think currently with DHIS2. In some countries, certain health facilities are only open certain times of the year. So in this case you really do not expect any activity to occur in such a facility when it is closed. There is currently really no way to say that a facility has closed temporarily in DHIS2.
What I might suggest you do is to consider to introduce a special data element like:
”Was this facility temporarily closed during the reporting period?” (Yes only)
For facilities that might be temporarily closed for whatever reason, they should eventually be able to report that they did not offer any services that month by ticking “Yes” to that question, and then completing the data set. The would not need to fill in anything else. Maybe a higher level district officer might also complete this on their behalf if they are unable. For facilities which are active, the usual answer here would be “No” and they would simply ignore the question and report their data.
This way at least you know the facility still exists, but that no services were offered. I am not sure this would solve your compliance issue, but this is an approach which we have used in other places which face this challenge.
Here is another suggestion, but again I am not sure if this will solve the problem. In the 1st DE on the form, insert a Zero, with the comment that the facility is closed. Also assign that DE to Keep the Zero. It keeps the facility ‘open’ but records that it did not function.
