dhis2-users team mailing list archive

[Prosper BT <ptb3000@xxxxxxxxx>]

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"

[image: Inline image 1]

[image: Inline image 2]

Regards


On Wed, Apr 22, 2015 at 2:21 PM, Thuy Nguyen <thuy.hispvietnam@xxxxxxxxx>
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@xxxxxxxxxx> đã 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
>> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-users
>> More help   : https://help.launchpad.net/ListHelp
>>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Prosper Behumbiize, MPH
Phone:        +256 414 320076
Cell:             +256 772 139037
                     +256 752 751776