dhis2-devs team mailing list archive

[Neranga <neranga.liyanaarachchi@xxxxxxxxx>]

Hi,

My main concern at this moment is on implementing name-based datasets in
DHIS2.
I have been through a real "hectic" process to come up with a Minimum
clinical dataset for cancer screening....
In my view, practically it is better for our generic software to
accommodate needed functions rather than redesigning the form form the
point where it is declared "essential" by the progremme officials....And I
think the aggregate side forms and patient side forms are functionally
different. For example, branching logic is quite handy in name-based forms.

Lars: Thanks for the docs.I will try it out and comeback to you if needed.
And I like your idea on section forms.

Neranga


On 23 July 2014 12:06, Lars Helge Øverland <larshelge@xxxxxxxxx> wrote:

>
> Hi there,
>
> thanks for the input. I don't think we will implement custom forms in
> section forms in the near future. When you have a form which is super-wide
> with mostly unused fields then that's usually a sign that the form itself
> should be re-designed.
>
> I have been thinking of a function for using the section form HTML as
> basis for custom forms - ie. you could get the section form layout as a
> starting point and then go on to modify the parts you need.
>
> Neranga: If you need tabs also for custom forms we have jquery ui included
> in the page and its pretty simple to set up the "tabs" widget with a little
> bit of HTML/javascript, see docs here <http://api.jqueryui.com/tabs/>.
>
> best regards,
>
> Lars
>
>
>
>
> On Wed, Jul 23, 2014 at 7:02 AM, Neranga <neranga.liyanaarachchi@xxxxxxxxx
> > wrote:
>
>> Hi,
>>
>> I faced a similar issue when I was customizing DHIS2 tracked instance to
>> collect patient-based data for the cancer screening clinic in Sri Lanka.
>> (DHIS2.15)
>> In our case, client details are collected for registration and then for
>> the visit clinical history, examination, investigations and follow up
>> details are recorded. As you understand there are elements which are very
>> specific to females and males, however it was difficult to implement the
>> "hiding fields" according to the value given to the sex attribute. I
>> couldn't find a way to implement that logic. Instead we designed 2 separate
>> programs for males and females, and it was not too bad to do so.
>> On the other hand I also found the "sections" in the program stages quite
>> useful too. But I had to give up the custom designed forms and go ahead
>> with the auto generated forms, because when I designed the form, the
>> section tab was no longer available.
>> I think these experiences will help developers to make future changes.
>> Thanks.
>>
>>
>> *L.A. Neranga Prabhath*
>> *Trainee - MSc in Medical Informatics*
>> *Postgraduate Institute of Medicine*
>> *University of Colombo-Sri Lanka.*
>> *Telephone: +94772531559 <%2B94772531559>*
>>
>>
>>
>> On 23 July 2014 10:12, Knut Staring <knutst@xxxxxxxxx> wrote:
>>
>>> Related to this, we have a big form where most sections are very simple
>>> and broken down only by gender, but one is also broken down by A LOT of age
>>> groupings, so the auto-generated form becomes extremely wide and the users
>>> have to scroll a lot horizontally. This also means it is very easy for them
>>> to lose track of where they are, though of course they do have the little
>>> box in the upper right corner which is meant to help with exactly those
>>> cases.
>>>
>>> So, in general we are very happy with the autogenerated form (and it is
>>> huge, with 10 sections), but would like to be able to customize the layout
>>> for this particular section (actually, the IDEAL option would be to be able
>>> to specify the width of the cells - as we could well have cells only a
>>> third of the automatic width).
>>>
>>> I suppose the best solution for now is to separate out this particular
>>> section into a separate form, but are we planning to support custom forms
>>> for sections?
>>>
>>> Knut
>>>
>>>
>>>
>>>
>>> On Wed, Jul 23, 2014 at 6:23 AM, <rin.channara@xxxxxxxxx> wrote:
>>>
>>>>  Hi all developers,
>>>> *MY SUGGESTION:*
>>>> In “section grey field management” of combo category options. Has
>>>> only “Disable field” for disable entry value. But I think it is
>>>> important, we should have “Hide field” to hide some combo category. Because
>>>> it effect on showing in Data Entry, if we has many combo category option
>>>> cross with data element.
>>>>
>>>> thank you
>>>> CHANNARA
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Knut Staring
>>> Dept. of Informatics, University of Oslo
>>> +4791880522
>>> http://dhis2.org
>>>
>>> _______________________________________________
>>> 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
>>
>>
>