Inactive Organisation Unit

Hi,

Someone know how to set an organisational unit as inactive without delete it?

Thanks,

Best Regards,

Marcos António.

Hi Marcos,

There are a couple of options, but I’m not sure how they interact with different DHIS-2 functions.

  1.    You can set the closed date = I think that is used when a facility closes but you want to keep all of the historical records.  In theory, if a facility is closed you should not be able to enter new data for it (but you may also have to remove it from the dataset) and it should not appear in the list of facilities that should report after the closing date.
    
  2.   You could set registers data to No – I’m not sure what that does with historical data – but at least it is an attribute that you can query on easily.
    
  3.    You could create a custom yes/no attribute for organization units:  Active.  This will display in the orgunit edit screen, but you may not see it if you want to use it to select data through the regular data analytics tools.
    

Randy

···

From: Dhis2-users [mailto:dhis2-users-bounces+rwilson=msh.org@lists.launchpad.net] On Behalf Of Marcos Antonio

Sent: Friday, April 04, 2014 10:43 AM

To: dhis2-users@lists.launchpad.net; dhis2-devs@lists.launchpad.net

Subject: [Dhis2-users] Inactive Organisation Unit

Hi,

Someone know how to set an organisational unit as inactive without delete it?

Thanks,

Best Regards,

Marcos António.

Bottom of Form

4. Remove all associations between the org unit and data sets.

I sort of agree with all of this, but the issue for us has been historical reporting completeness rates. AFAIK, the analytics process does not respect the “Closed date”, but I could be wrong, and there is no history in the dataset to remember when a facility was reporting, and when it stopped reporting. As an example, maybe there are 11 facilities in a district during 2013. If 11 reports come in during this period, then the reporting completeness is 100%. If a facility closes in 2014, and deallocate this inactive facility, then the current reporting completeness will be OK, but the historical reporting completeness (i.e. for 2013) will now be calculated as 11/10, or greater than 100%. It seems rather complex, so I can see why it has not been implemented. However my suggestion would be that

  1. Leave an inactive facility in the dataset.

  2. The analytics process should respect the “Opening” and “Closed” dates when calculating reporting completenes. If the facility is still allocated to a dataset but inactive, you should not be able to enter data for it, but it SHOULD be counted for reporting completeness for the time period for which it was open.

I think that is a rather superficial analysis and I am sure it would need to be developed better, but hope it helps to illustrate what the challenge is when removing a closed facility from a dataset.

Regards,

Jason

···

On Fri, Apr 4, 2014 at 11:38 AM, Lars Helge Øverland larshelge@gmail.com wrote:


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

  1. Remove all associations between the org unit and data sets.

Fully agree with that - its just a matter of getting time to implement it.

Lars

Tricky issue – Discussed before. The problem is that the OU attributes that should control this seem to conflict each other. For instance even if the closed date is set / Registers Data set to No and datasets are allocated to the OU – data will still be captured against this OU.

Lars, we may need to review the functionality of closing date for OUs and also other relevant metadata like dataelements and indicators.

Regards,

Dapo Adejumo

+2348033683677

skype : dapojorge

···

From: Dhis2-users [mailto:dhis2-users-bounces+dapo_adejumo=yahoo.com@lists.launchpad.net] On Behalf Of Lars Helge Øverland
Sent: 04 April 2014 10:38
To: Wilson,Randy
Cc: dhis2-users@lists.launchpad.net; dhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-users] [Dhis2-devs] Inactive Organisation Unit

  1. Remove all associations between the org unit and data sets.

Hi Dapo,

I have put my comments on issue

  1. Remove all associations between the org unit and data sets.

Please see the trail mail for the reference. hope this will help you.

Regards

Brajesh Murari

P please consider the environment before printing this email

···

On Friday, 4 April 2014 4:24 PM, Dapo Adejumo dapo_adejumo@yahoo.com wrote:

Tricky issue – Discussed before. The problem is that the OU attributes that should control this seem to conflict each other. For instance even if the closed date is set / Registers Data set to No and datasets are allocated to the OU – data will still be captured against this OU.

Lars, we may need to review the functionality of closing date for OUs and also other relevant metadata like dataelements and indicators.

Regards,

Dapo Adejumo

+2348033683677

skype : dapojorge

From: Dhis2-users [mailto:dhis2-users-bounces+dapo_adejumo=yahoo.com@lists.launchpad.net] On Behalf Of Lars Helge Øverland
Sent: 04 April 2014 10:38
To: Wilson,Randy
Cc: dhis2-users@lists.launchpad.net; dhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-users] [Dhis2-devs] Inactive Organisation Unit

  1. Remove all associations between the org unit and data sets.

I think
association is one of the most oldest inherent feature provided in DHIS development since DHIS 1,

Perhaps, in OOP methodology, association is week relationship and composition is strong,

some thing
like indicators indicating performance of services provided by facility associated with

organizationunit represents weak relationship, but composition of dataset for even a very small

new born organizationunit represents a strong relationship, it does’t matter new born organization

unit is still birth or live birth, reporting with attached dataset with reports to their parent
orgnaisationunits

or not but their association with datasets had been always supported by various global health

governing system agencies and health systems in most of the developed and under developed

countries round the
globe. This implies that association is week and composition is strong relationship.

But this does’t implies that we should absolutely focused on compositions only, and loses affirmative and associative services consumptions with other quality functional multi-threaded, multi-cultural aspect oriented services consumption provided by old historical attached organizationunit, may be some where on long distance there would be concept and culture of lion’s loosely coupled and weird but clean relationship, where dataset composition design took-place only after birth of new born organizationunit, and there could be a culture of multiple times datasets association-dissociations with orgaisationunit and datasets and several reforms in datasets hierarchical design.


Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp

Hi Jason,

I followed your suggestion in the bullets 1 and 2 . So my doubt is how to hide the inactive facility in the list of facilities?

Thanks

Regards,

Hugo

···

From: Jason Pickering [mailto:jason.p.pickering@gmail.com]
Sent: sexta-feira, 4 de Abril de 2014 11:50
To: Lars Helge Øverland
Cc: Wilson,Randy; Marcos Antonio; dhis2-users@lists.launchpad.net; dhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-devs] [Dhis2-users] Inactive Organisation Unit

I sort of agree with all of this, but the issue for us has been historical reporting completeness rates. AFAIK, the analytics process does not respect the “Closed date”, but I could be wrong, and there is no history in the dataset to remember when a facility was reporting, and when it stopped reporting. As an example, maybe there are 11 facilities in a district during 2013. If 11 reports come in during this period, then the reporting completeness is 100%. If a facility closes in 2014, and deallocate this inactive facility, then the current reporting completeness will be OK, but the historical reporting completeness (i.e. for 2013) will now be calculated as 11/10, or greater than 100%. It seems rather complex, so I can see why it has not been implemented. However my suggestion would be that

  1. Leave an inactive facility in the dataset.

  2. The analytics process should respect the “Opening” and “Closed” dates when calculating reporting completenes. If the facility is still allocated to a dataset but inactive, you should not be able to enter data for it, but it SHOULD be counted for reporting completeness for the time period for which it was open.

I think that is a rather superficial analysis and I am sure it would need to be developed better, but hope it helps to illustrate what the challenge is when removing a closed facility from a dataset.

Regards,

Jason

On Fri, Apr 4, 2014 at 11:38 AM, Lars Helge Øverland larshelge@gmail.com wrote:

  1. Remove all associations between the org unit and data sets.

Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp

Hi Hugo,
AFAIK, that is not possible, but maybe the devs can advise on this.

Regards,

Jason

···

On Tue, Apr 8, 2014 at 3:21 PM, Marcos Antonio mlantonio@criticalsoftware.co.mz wrote:

Hi Jason,

I followed your suggestion in the bullets 1 and 2 . So my doubt is how to hide the inactive facility in the list of facilities?

Thanks

Regards,

Hugo

From: Jason Pickering [mailto:jason.p.pickering@gmail.com]

Sent: sexta-feira, 4 de Abril de 2014 11:50
To: Lars Helge Øverland
Cc: Wilson,Randy; Marcos Antonio; dhis2-users@lists.launchpad.net; dhis2-devs@lists.launchpad.net

Subject: Re: [Dhis2-devs] [Dhis2-users] Inactive Organisation Unit

I sort of agree with all of this, but the issue for us has been historical reporting completeness rates. AFAIK, the analytics process does not respect the “Closed date”, but I could be wrong, and there is no history in the dataset to remember when a facility was reporting, and when it stopped reporting. As an example, maybe there are 11 facilities in a district during 2013. If 11 reports come in during this period, then the reporting completeness is 100%. If a facility closes in 2014, and deallocate this inactive facility, then the current reporting completeness will be OK, but the historical reporting completeness (i.e. for 2013) will now be calculated as 11/10, or greater than 100%. It seems rather complex, so I can see why it has not been implemented. However my suggestion would be that

  1. Leave an inactive facility in the dataset.
  1. The analytics process should respect the “Opening” and “Closed” dates when calculating reporting completenes. If the facility is still allocated to a dataset but inactive, you should not be able to enter data for it, but it SHOULD be counted for reporting completeness for the time period for which it was open.

I think that is a rather superficial analysis and I am sure it would need to be developed better, but hope it helps to illustrate what the challenge is when removing a closed facility from a dataset.

Regards,

Jason

On Fri, Apr 4, 2014 at 11:38 AM, Lars Helge Øverland larshelge@gmail.com wrote:

  1. Remove all associations between the org unit and data sets.

Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp