we experience some > 100% figures in data completeness figures in the Senegal database in the data visualizer. For example, it can show 102% for a region, then we identify one of its districts as having 108%, but then at facility level there are only max 100% values (and some 0%). In the dataset completeness reports, we don't find this problem. I'm unable to track down what is wrong. Any suggestions? It's dhis 2.16
Dearr Johan,
We have the same problem, I think you have to define you denominator if it
is indicator.
Regards,
Chansaly
···
-----Original Message-----
From: Dhis2-users
[mailto:dhis2-users-bounces+hsipchansaly=etllao.com@lists.launchpad.net] On
Behalf Of Johan Ivar Sæbø
Sent: Wednesday, April 22, 2015 5:54 PM
To: dhis2-users@lists.launchpad.net; bdndoye@gmail.com; okaldiallo@gmail.com
Subject: [Dhis2-users] Strange behaviour of completeness data
Hi,
we experience some > 100% figures in data completeness figures in the
Senegal database in the data visualizer. For example, it can show 102% for a
region, then we identify one of its districts as having 108%, but then at
facility level there are only max 100% values (and some 0%). In the dataset
completeness reports, we don't find this problem. I'm unable to track down
what is wrong. Any suggestions? It's dhis 2.16
It always Happen when you put Period in Months in Filter, this means that the system counts the number of period. It works well when in your Table layout, Category has org. unit, data or Period. And Filter works well when period is not desegregated in Months…
we experience some > 100% figures in data completeness figures in the
Senegal database in the data visualizer. For example, it can show 102% for a
region, then we identify one of its districts as having 108%, but then at
facility level there are only max 100% values (and some 0%). In the dataset
completeness reports, we don’t find this problem. I’m unable to track down
what is wrong. Any suggestions? It’s dhis 2.16
It is because the dataset used to assign in some organisation units, in this case properly in region and user used to complete data in this region level. And then the dataset was unassigned to that organisation unit. So the completeness percentage is higher than 100%. As the numerator is the actual completeness in data entry and the denominator is the number of org unit dataset assign. This is what I experienced.
What you can do is to reassign dataset to that org unit and incomplete. Then unassigned dataset from that org unit again. Clear caches and generate analytic table.
I hope this can help you.
Và o 22-04-2015 17:54, “Johan Ivar Sæbø” johansa@ifi.uio.no đã viết:
···
Hi,
we experience some > 100% figures in data completeness figures in the Senegal database in the data visualizer. For example, it can show 102% for a region, then we identify one of its districts as having 108%, but then at facility level there are only max 100% values (and some 0%). In the dataset completeness reports, we don’t find this problem. I’m unable to track down what is wrong. Any suggestions? It’s dhis 2.16
The Dataset for which you are trying to measure completeness, does it have some properties like attributes? For examples in the case of HTC report where you can chose points of service such as OPD, TB, etc.
"For God is not unrighteous to forget your work and labour of love..."
···
--------------------------------------------
On Wed, 4/22/15, Johan Ivar Sæbø <johansa@ifi.uio.no> wrote:
Subject: [Dhis2-users] Strange behaviour of completeness data
To: dhis2-users@lists.launchpad.net, bdndoye@gmail.com, okaldiallo@gmail.com
Date: Wednesday, April 22, 2015, 12:54 PM
Hi,
we experience some > 100% figures in data completeness
figures in the
Senegal database in the data visualizer. For example, it can
show 102%
for a region, then we identify one of its districts as
having 108%, but
then at facility level there are only max 100% values (and
some 0%). In
the dataset completeness reports, we don't find this
problem. I'm unable
to track down what is wrong. Any suggestions? It's dhis
2.16
Reporting rates greater than 100% are brought about by conflicts in the Orgunits group sets.
You need to run Integrity checks to catch these conflicts.
Go to Apps ===> Data Administration and click on Data Integrity
Once it has run, check under “Organisation units violating exclusive group sets”
Here you will find a list of Orgunits violating the group sets and resolve them.
What it means is that you have two groups say “Government” and “Private” which are in a group set called “Ownership” and a given facility is assigned to the two groups.
So you will need to remove it from one group.
See what is happening on the demo server (Clinic shouldn’t be both Public Facility and Private clinic, because they belong to the same group set “Facility Ownership”
It is because the dataset used to assign in some organisation units, in this case properly in region and user used to complete data in this region level. And then the dataset was unassigned to that organisation unit. So the completeness percentage is higher than 100%. As the numerator is the actual completeness in data entry and the denominator is the number of org unit dataset assign. This is what I experienced.
What you can do is to reassign dataset to that org unit and incomplete. Then unassigned dataset from that org unit again. Clear caches and generate analytic table.
I hope this can help you.
Và o 22-04-2015 17:54, “Johan Ivar Sæbø” johansa@ifi.uio.no đã viết:
Hi,
we experience some > 100% figures in data completeness figures in the Senegal database in the data visualizer. For example, it can show 102% for a region, then we identify one of its districts as having 108%, but then at facility level there are only max 100% values (and some 0%). In the dataset completeness reports, we don’t find this problem. I’m unable to track down what is wrong. Any suggestions? It’s dhis 2.16
Thank you Prosper, this is probably the reason; the integrity checks gave a a loooong list of violating facilities. It will take some time before I can address them all and see if this will solve the problem though.
Regards,
Johan
···
On 23.04.2015 10:51, Prosper BT wrote:
Hi all,
Reporting rates greater than 100% are brought about by conflicts in the Orgunits group sets.
You need to run Integrity checks to catch these conflicts.
Go to Apps ===> Data Administration and click on Data Integrity
Once it has run, check under " Organisation units violating exclusive group sets"
Here you will find a list of Orgunits violating the group sets and resolve them.
What it means is that you have two groups say "Government" and "Private" which are in a group set called "Ownership" and a given facility is assigned to the two groups.
So you will need to remove it from one group.
See what is happening on the demo server (Clinic shouldn't be both Public Facility and Private clinic, because they belong to the same group set "Facility Ownership"
Regards
On Wed, Apr 22, 2015 at 2:21 PM, Thuy Nguyen <thuy.hispvietnam@gmail.com>
wrote:
Dear Johan
It is because the dataset used to assign in some organisation units, in this case properly in region and user used to complete data in this region level. And then the dataset was unassigned to that organisation unit. So the completeness percentage is higher than 100%. As the numerator is the actual completeness in data entry and the denominator is the number of org unit dataset assign. This is what I experienced.
What you can do is to reassign dataset to that org unit and incomplete. Then unassigned dataset from that org unit again. Clear caches and generate analytic table.
I hope this can help you.
Và o 22-04-2015 17:54, "Johan Ivar Sæbø" <johansa@ifi.uio.no > đã viết:
Hi,
we experience some > 100% figures in data completeness figures in the Senegal database in the data visualizer. For example, it can show 102% for a region, then we identify one of its districts as having 108%, but then at facility level there are only max 100% values (and some 0%). In the dataset completeness reports, we don't find this problem. I'm unable to track down what is wrong. Any suggestions? It's dhis 2.16
Regards,
Johan
_______________________________________________
Mailing list: [https://launchpad.net/~dhis2-users](https://launchpad.net/%7Edhis2-users)
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : [https://launchpad.net/~dhis2-users](https://launchpad.net/%7Edhis2-users)
More help : [https://help.launchpad.net/ListHelp](https://help.launchpad.net/ListHelp)
_______________________________________________
Mailing list: [https://launchpad.net/~dhis2-users](https://launchpad.net/%7Edhis2-users)
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : [https://launchpad.net/~dhis2-users](https://launchpad.net/%7Edhis2-users)
More help : [https://help.launchpad.net/ListHelp](https://help.launchpad.net/ListHelp)