dhis2-users team mailing list archive

[Paulo Grácio <pgracio@xxxxxxxxxxxxxxxxxxxx>]

At this moment I’m trying to define an approach to address a requirement
about data set submissions deadlines between levels.

 

Imagine that you have 4 levels of Organization Units, National, Province,
District and Health  Units.

 

-          Health Units send their aggregated data to District using paper
forms till the end of the month for monthly cases.

-          District Operator enters data on DHIS2. Defining expiry days to
5, we have the possibility to enter data till 5 days after the end date of
the selected data entry period. In this case, would be interesting to notify
Operators on day 1, deadline of Health Units, saying that they should enter
data and one day before deadline telling that data submission will be locked
for further entry.

-          Province Operator has to import Data from District till 10 days
after the end date of the selected data entry period. 

-          National Operator has to import Data from Province till 15 days
after the end date of the selected data entry period.

 

We are planning to have a hybrid deployment, this scenario only applies when
District and Province are Offline installations.  Lars suggestion seems to
be flexible enough, my question is what if in some districts I have to use
DHIS2 Live because of hardware limitations?

 

Regards,

Paulo Grácio

 

From: Lars Helge Øverland [mailto:larshelge@xxxxxxxxx] 
Sent: segunda-feira, 13 de Maio de 2013 12:35
To: Ola Hodne Titlestad
Cc: Paulo Grácio; dhis2-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Dhis2-users] Notification - Deadline for data set submission

 

Hi Paulo,

 

sorry not at the moment.

 

However, messaging is exposed through the web API, so you could do something
like this:

 

- create a SQL view which gives you the ids of the users who have not
completed the form this month, using some clever SQL which joins
completedatasetregistration, organisationunit and user.

 

- set up a script which retrieves that sql view as json, parses it and uses
cURL to request the web api to dispatch messages to those user with a
descriptive message.

 

- run that script as a cron job, lets say two days before the dealine every
month.

 

 

See here for messaging api docs:

 

http://dhis2.org/doc/snapshot/en/user/html/ch25s11.html

 

And here for sql view api docs:

 

http://dhis2.org/doc/snapshot/en/user/html/ch25s17.html

 

regards,

 

Lars