dhis2-users team mailing list archive

[Bal Ram Bhui <balram_bhui@xxxxxxxxx>]

Hi Ola and Lars,
Thank you guys for very much for working so hard to meet our requests. I have some observations and suggestions for you; I am not sure if they are covered in DHIS 2.13. I have just talked with Stephen about it and we are going to test it for Liberia.

My observation is on data visualizer. I see that we can use data element as filter but the indicator while taking period as category for the line graph. I think we need to be able to see the indicator graphs by organization unit or and group set. Other observation is that is it possible to give clearly different markers on the lines of graph in addition to the colors which is there now so that they can be distinguishable even when they are printed.

Thanks a million.
Bal Ram Bhui
Monrovia.



On Thursday, October 31, 2013 9:07 AM, Ola Hodne Titlestad <olati@xxxxxxxxxx> wrote:
 
Hi, 
Agree with Lars. I would use orgunits to represent the departments/wards as it gives you more flexibility. It will require more customisation time to get all the orgunit names right in each hospital, but it is worth it, at least if you want to support data analysis and mangement at each hospital. 
Sometimes the hospital prefers to use local names on wards, like Cot ward A. Cot ward B, up/down etc and also have more than one physical ward/room for the same type/category.  A standard naming scheme through data element categories would be difficult to use in this case. 
Typically a hospital would like to do analysis by each physical ward (bed occupancy rates etc) and not always group them together by type of ward.
You can use orgunit groups to apply standard hospital departement names to all those wards,  which can then be used for aggregation when doing analysis above the hospital level or when comparing hospitals. 
Ola
------
On 31 Oct 2013 09:32, "Lars Helge Øverland" <larshelge@xxxxxxxxx> wrote:

Hi Marta,
>
>
>I don't know enough about the use-case to be sure. However my suggestion would be to use the organisation units to represent the departments. It is simply because usually the departments are different across hospitals - some are not always there, some are combined and so on. So you could make a script that creates the initial setup with all departments in all places and then modify it from there. It makes form design easier. The data mart performance penalty mentioned above applied at the time of writing but not anymore with the analytics engine. A problem with using categories is that you get lots of non-applicable fields if you use section forms, and lots of maintenance mess if you go with custom forms.
>
>
>cheers
>
>
>Lars
> 
>_______________________________________________
>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