Hi all,
I would like views on what I perceive to be a bug in DHIS2 that Data
Approval Workflow does not respect/adhere to Dataset/Orgunit assignment.
I'll paint the scenario:
An integrated HIS reporting system where different facility types report on
data elements applicable to them so the Orgunit and Dataset assigned could
look something like this:
Country
Dataset assigned
Workflow period
Region 1
District 1
Clinic A
PHC dataset
Monthly
Community Health Centre B
PHC dataset + Delivery dataset
Monthly
Hospital C
Hospital dataset
Monthly
Community outreach D
Community Dataset
Monthly
Emergency Service E
EMS dataset
Monthly
If you set up a workflow for e.g. PHC dataset - Monthly you have to let the
Manager of not only Clinic A and Community Health Centre B approve that
dataset BUT also Hospital C, Community Outreach D and Emergency Service E
while they DON'T REPORT and are not assigned to that dataset. If they don't
all approve the same workflow then District 1 cannot approve the dataset.
Yes, it is possible to create one overall dataset which everyone then
approves but it looks very "dirty" because most of the signoff report is
elements they should not report on thus blank and it is not easy for them to
identify the REAL GAPS which they should have reported on if >50% of the
form is blank and it is too long.
What would it take to attach the data approval to the Dataset>Orgunit
Assignment that is done for data entry thus only requiring approval at lower
level if that orgunit is assigned to the dataset. If that is done then only
Clinic A and Community Health Centre B would be assigned to the workflow and
be required to approve before District 1 can approve. I would appreciate
some feedback and prepared to write a blueprint for it if required.
Regards,
Elmarie Claasen
Hisp logo
Project Manager
Health Information Systems Program
Tel: 041-367 1027
Cell: 082 374 2209
E-mail: <mailto:elma...@hisp.org> elma...@hisp.org
Skype: elmarie.claasen52
This message and any attachments are subject to a disclaimer published at
<http://www.hisp.org/policies.html#comms_disclaimer>
http://www.hisp.org/policies.html#comms_disclaimer . Please read the
disclaimer before opening any attachment or taking any other action in terms
of this electronic transmission.
If you cannot access the disclaimer, kindly send an email to
<mailto:disclai...@hisp.org> disclai...@hisp.org and a copy will be provided
to you. By replying to this e-mail or opening any attachment you agree to be
bound by the provisions of the disclaimer.
--
*This message and any attachments are subject to a disclaimer published at
http://www.hisp.org/policies.html#comms_disclaimer
<http://www.hisp.org/policies.html#comms_disclaimer>. Please read the
disclaimer before opening any attachment or taking any other action in
terms of this electronic transmission. If you cannot access the
disclaimer, kindly send an email to disclai...@hisp.org
<disclai...@hisp.org> and a copy will be provided to you. By replying to
this e-mail or opening any attachment you agree to be bound by the
provisions of the disclaimer.*
_______________________________________________
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
