Temporarily close an org unit

Dear All,

I am looking for a solution for suspending or temporarily closing an org unit and then re-opening it, so that the org unit is not factored into data completeness reporting during the time it is closed.

Is there a way to close a facility for a short period of time, then re-open it, but also have it be included in historical data analysis for the time period that it was open, prior to re-opening it?

If not, has anyone found a workaround?

In addition, is there a way to block data entry for a closed facility after the closing date? Based on documentation, that was my understanding, but when I tested it in version 2.24, I was able to enter data after the Closed date.

Thanks for the help!

Best,

Tamara

Hi Tamara,

We had similar challenges and realized that the close data doesn’t fix this issue. We were told by our consultant that the close date may not make org units unavailable for data entry until version 2.28.

I can only think of either unlinking the data set until you want to reopen the org unit or just training users on not using the org unit for a certain time period.

Best,

Heidi

···

Dear All,

I am looking for a solution for suspending or temporarily closing an org unit and then re-opening it, so that the org unit is not factored into data completeness reporting during the time it is closed.

Is there a way to close a facility for a short period of time, then re-open it, but also have it be included in historical data analysis for the time period that it was open, prior to re-opening it?

If not, has anyone found a workaround?

In addition, is there a way to block data entry for a closed facility after the closing date? Based on documentation, that was my understanding, but when I tested it in version 2.24, I was able to enter data after the Closed date.

Thanks for the help!

Best,

Tamara

Hi Heidi,

Thank you for clarifying the issue with data entry.

Did you also have an issue with temporarily closing org units? The problem that I see is that once and org unit is closed, it has to be re-opened, since the “Closed” date cannot be removed. By moving the Opening Date, you lose the ability to see the historical data from that facility in analytics prior to the Opening Date.

Best,

Tamara

···

On Wed, Jul 12, 2017 at 5:19 PM, Schroffel, Heidi hschroffel@care.org wrote:

Hi Tamara,

We had similar challenges and realized that the close data doesn’t fix this issue. We were told by our consultant that the close date may not make org units unavailable for data entry until version 2.28.

I can only think of either unlinking the data set until you want to reopen the org unit or just training users on not using the org unit for a certain time period.

Best,

Heidi

From: Dhis2-users [mailto:dhis2-users-bounces+hschroffel=care.org@lists.launchpad.net] On Behalf Of Tamara Goldschmidt

Sent: Wednesday, July 12, 2017 10:24 AM

To: dhis2-users@lists.launchpad.net

Subject: [Dhis2-users] Temporarily close an org unit

Dear All,

I am looking for a solution for suspending or temporarily closing an org unit and then re-opening it, so that the org unit is not factored into data completeness reporting during the time it is closed.

Is there a way to close a facility for a short period of time, then re-open it, but also have it be included in historical data analysis for the time period that it was open, prior to re-opening it?

If not, has anyone found a workaround?

In addition, is there a way to block data entry for a closed facility after the closing date? Based on documentation, that was my understanding, but when I tested it in version 2.24, I was able to enter data after the Closed date.

Thanks for the help!

Best,

Tamara

We only closed org units and haven’t had the need to reopen it, so we haven’t encountered this yet. But grateful for that consideration in case we do! Sorry I don’t have more helpful info to offer.

···

Hi Heidi,

Thank you for clarifying the issue with data entry.

Did you also have an issue with temporarily closing org units? The problem that I see is that once and org unit is closed, it has to be re-opened, since the “Closed” date cannot be removed. By moving the Opening Date, you lose the ability to see the historical data from that facility in analytics prior to the Opening Date.

Best,

Tamara

On Wed, Jul 12, 2017 at 5:19 PM, Schroffel, Heidi hschroffel@care.org wrote:

Hi Tamara,

We had similar challenges and realized that the close data doesn’t fix this issue. We were told by our consultant that the close date may not make org units unavailable for data entry until version 2.28.

I can only think of either unlinking the data set until you want to reopen the org unit or just training users on not using the org unit for a certain time period.

Best,

Heidi

From: Dhis2-users [mailto:dhis2-users-bounces+hschroffel=care.org@lists.launchpad.net] On Behalf Of Tamara Goldschmidt

Sent: Wednesday, July 12, 2017 10:24 AM

To: dhis2-users@lists.launchpad.net

Subject: [Dhis2-users] Temporarily close an org unit

Dear All,

I am looking for a solution for suspending or temporarily closing an org unit and then re-opening it, so that the org unit is not factored into data completeness reporting during the time it is closed.

Is there a way to close a facility for a short period of time, then re-open it, but also have it be included in historical data analysis for the time period that it was open, prior to re-opening it?

If not, has anyone found a workaround?

In addition, is there a way to block data entry for a closed facility after the closing date? Based on documentation, that was my understanding, but when I tested it in version 2.24, I was able to enter data after the Closed date.

Thanks for the help!

Best,

Tamara