dhis2-devs team mailing list archive

[Jason Pickering <jason.p.pickering@xxxxxxxxx>]

I was just about to suggest the "graying" out of certain cells. We
have some data elements in Zambia that generally correspond to a
catcombo, but for some reasons, are not actually recorded. For
instance the data element "Hypertension" is only recorded for the age
group "Over 5" although all the other data elements on the form are
collected with "Under 1", and "1-5" age groups. There must be some way
to indicate that these catcombos are not applicable and should not be
included. Another option/workaround, would be to generate the default
grid data entry form, and the just have the form implementer remove
them. However, this would really not be the most ideal solution.

I have not had a chance to read the document yet, but will provide
some more feedback when I get a chance.

Regards,
Jason


On Thu, Jun 10, 2010 at 8:30 PM, Abyot Gizaw <abyota@xxxxxxxxx> wrote:
> Thank you Ola, I got your points.
>
> With the lists I was proposing which one to use .... so you are suggesting
> categorycombo. meaning a section to have only one categorycombo. and also
> public health logic which is effectively number of dataelements ?
>
> yes ... graying out of a cell will also be implemented.
>
> Abyot.
>
> On Thu, Jun 10, 2010 at 5:51 PM, Ola Hodne Titlestad <olatitle@xxxxxxxxx>
> wrote:
>>
>> Hi Abyot,
>>
>> I would like to freely group data elements of a dataset into sections and
>> have these sections be displayed as separate tables on a data entry screen
>> with an optional heading for each of them.
>> I don't think we need to restrict to one or more of your numbered items
>> below. A key restriction for me would be to only allow one catcombo per
>> section, if not you will not be able to auto-generate the tables.
>>
>> To me the main point of this functionality is to as much as possible avoid
>> having to design custom forms, especially when the forms you are dealing
>> with are tabular and somewhat logically built up.
>>
>> Many of the forms we were designing in Sierra Leone recently had multiple
>> tables, some with more than one column, some with only one column. That
>> means some sections would have a catcombo corresponding to many columns,
>> like:
>> | Data Element | < 5, male | < 5, female | > 5, male | <5 female |
>>
>> while other tables were made up of data elements with the default
>> catcombo, on the type:
>> | Data Element | Value |
>>
>> But we would typically have multiple tables (aka sections) which had the
>> default catcombo that were separated due to their public health program or
>> subprogram (ANC, Deliveries, Pregnancy complications etc.), and each of
>> these would have their own heading.
>>
>> So to use your words, the baseline to divide the data entry screen (I
>> assume you mean how to build sections) in our case could not be
>> automatically generated, but in stead the user had to manually create the
>> sections and add data elements to these. What guides the user will then be
>> the various tables on the paper form.
>>
>> In addition to be able to auto generate those tables in the data entry
>> screen I would like to freely set the order of the tables/sections and for
>> each table/section specify which fields that need to be greyed out on the
>> data entry screen.
>>
>> The tables can be listed one by one under each other, at least as the
>> first basic step. Being able to put tables next to each other horizontally
>> would be a bonus, but the vertical order of tables is more important.
>>
>> Hope this helps to clarify the needs.
>>
>> Ola
>> ----------
>>
>>
>>
>>
>> Ola Hodne Titlestad |Technical Officer|
>> Health Metrics Network (HMN) | World Health Organization
>> Avenue Appia 20 |1211 Geneva 27, Switzerland | Email:
>> titlestado@xxxxxxx|Tel: +41 788216897
>> Website: www.healthmetricsnetwork.org
>>
>> Better Information. Better Decisions. Better Health.
>>
>>
>> On 9 June 2010 11:28, Abyot Gizaw <abyota@xxxxxxxxx> wrote:
>>>
>>> Hi Dears,
>>>
>>> Just wanted to have your inputs ...
>>>
>>> Currently I am working on sections - simply dividing dataentry screens
>>> into sections, disabling/enabling dataentry cells (grayed fields) and stuff
>>> like that. I will take off from the existing section code/functionality....
>>> so a question I have is - what is the base line to divide a dataentry
>>> screen:
>>>
>>> number of dataelements - like display area?
>>> categorycombo - for example nice looking uniform table heading?
>>> some kind of public health logic - for example dividing disease
>>> collection form into - airborne, waterborne,.... disease ?
>>> .....
>>>
>>> Thank you
>>> Abyot.
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~dhis2-devs
>>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~dhis2-devs
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>



-- 
--
Jason P. Pickering
email: jason.p.pickering@xxxxxxxxx
tel:+260968395190