dhis2-users team mailing list archive

[Abyot Asalefew Gizaw <abyot@xxxxxxxxx>]

Hi,

I like the idea of outlining concrete usecase scenarios first...

The issue is not at all about UI - rather on the output side. Do we need to
aggregate or not.

Where aggregation is not required:

- may be introduce new value type something like "MULTI_TEXT" together with
option set (*Note*: we already have valueType TEXT together with option set
where aggregation/counting is possible)

Where aggregation is required:

- introduce a special data model, multiSelectProgramStageDataElementGroup.
This group belongs to a program stage. A program stage can have multiple of
this group - we might have multiple multi-select choices. Each group
contains list of yes only value type data elements.

--
Abyot A. Gizaw.
Senior Engineer, DHIS2
University of Oslo
http://www.dhis2.org

On Wed, Sep 28, 2016 at 2:58 PM, Calle Hedberg <calle.hedberg@xxxxxxxxx>
wrote:

> Hi
>
> I'm running a training/discussion workshop with public health &
> surveillance officers tomorrow on the South African pilot Integrated
> Disease Surveillance Reporting system, and both symptoms and treatments
> have been included on the SA notification form - BUT it was initially
> decided to simply limit the number of symptoms to 4 and treatments to 3
> (each being a text field). it's not ideal, though, both because there might
> be more relevant symptoms/treatments, and also because we will have to use
> 4 or 3 separate option sets to ensure that the same symptoms are put into
> the same data element every time (if analytics results are important, that
> is).
>
> So I will raise the issue there and get their take on the primary use of
> such data.
>
> Regards
> Calle
>
> On 28 September 2016 at 14:51, Calle Hedberg <calle.hedberg@xxxxxxxxx>
> wrote:
>
>> Alex,
>>
>> You might have considerably more than 30 symptoms - it all depends on how
>> "specialised" you want them  (re ICD-9 used to be around 10,000 codes - now
>> I believe ICD-10 have something like 60-70,000....).
>>
>> The same logic applies to treatments - assuming 30-100 notifiable
>> diseases being tracked, you might have a few hundred treatment options....
>>
>> I think we need to unpack the main USAGE scenarios for this type of data
>> - are we looking for analytics results, or will the data mainly be used to
>> provide a "rich picture" for e.g. clinicians, lab engineers, surveillance
>> officers, or various specialists to determine e.g. what lab tests to run
>>  or what public health actions to take?
>>
>> Regards
>> Calle
>>
>> On 28 September 2016 at 14:34, Alex Tumwesigye <atumwesigye@xxxxxxxxx>
>> wrote:
>>
>>> Jason and Prosper,
>>>
>>> Thanks for sharing the idea of how it can be implemented. However, this
>>> works for a few options. In IDSR implementation I have encountered more
>>> than 30 symptoms. I think, we need to figure out how this can be achieved.
>>>
>>> Thanks.
>>>
>>> Alex
>>>
>>> On Wed, Sep 28, 2016 at 3:00 PM, Jason Pickering <
>>> jason.p.pickering@xxxxxxxxx> wrote:
>>>
>>>> The reason is has to be separate data elements is because of analytics.
>>>> If you have a single data element with multiple choices, there is currently
>>>> not a way to aggregate all of these. So lets say you have a question like
>>>>
>>>> What symptoms does the patient have?
>>>> a) Headache
>>>> b) Fever
>>>> c) Fatigue
>>>>
>>>> If there was some sort of UI component like you are talking about with
>>>> a single data element, we would need to record something like
>>>> Headache; Fever; Fatigue
>>>> in a single row in the database. When we aggregate it, well, it would
>>>> not be really clear how we would do this. We would need to parse out all of
>>>> the options and then somehow transform them into
>>>>
>>>> Headache = 2
>>>> Fever = 4
>>>> Fatigue = 5
>>>>
>>>> The of course you have more complicated situations like patients who
>>>> have both Fever and Fatigue.
>>>>
>>>> So, the way it has to be implemented now in DHIS2, is through a boolean
>>>> data element.
>>>>
>>>> Does the patient have a headache?
>>>> Does the patient have a fever?
>>>> Does the patient have fatigue?
>>>>
>>>> Aggregation becomes just a matter of counting how many of these are
>>>> true.
>>>>
>>>> So, you could implement some sort of custom control do to this, but in
>>>> the end, you would need completely separate data elements, but maybe this
>>>> was not really your question, since you were asking about a UI component?
>>>>
>>>> Currently, its not there, but has been asked for several times.
>>>>
>>>> Regards,
>>>> Jason
>>>>
>>>>
>>>> On Wed, Sep 28, 2016 at 1:00 PM, Prosper BT <ptb3000@xxxxxxxxx> wrote:
>>>>
>>>>> Dear Paul,
>>>>>
>>>>> Thanks for sharing this, its some blue print being discussed not yet
>>>>> implemented, we hope it can come soon especially for IDSR - symptoms. The
>>>>> work around right now is to design all the different options are either
>>>>> attributes or data elements depending on where they are going to be used
>>>>> with data type Yes Only
>>>>>
>>>>>
>>>>> [image: Inline image 1]
>>>>>
>>>>> ​Or if you are using a custom form, you can implement it your way
>>>>>
>>>>> Regards
>>>>>
>>>>> ​
>>>>>
>>>>> On Wed, Sep 28, 2016 at 1:24 PM, Arun Paul <paul.arun@xxxxxxxxx>
>>>>> wrote:
>>>>>
>>>>>> Hello everyone,
>>>>>>
>>>>>> I am configuring a program using Tracker Capture. It requires data
>>>>>> input using a multi-select dropdown or multi-select checkbox. Example for
>>>>>> such a field is "Symptoms" or "Drugs given for treatment". For these
>>>>>> fields, I need to select more than one option as answers.
>>>>>>
>>>>>> Is this UI component already supported?
>>>>>>
>>>>>> Else, how can I support this through some work around or
>>>>>> code-customization ?
>>>>>>
>>>>>> Please let me know.
>>>>>>
>>>>>> ​Thanks in advance
>>>>>> ,
>>>>>> - Arun Paul
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Prosper Behumbiize, MPH
>>>>> Global DHIS2 Implementation| HISP Uganda/University Of Oslo
>>>>> +256 752 751 776 | +256 776 139 139
>>>>> prosper@xxxxxxxxxxxxxx <ptb3000@xxxxxxxxx> | prosper@xxxxxxxxx | Skype:
>>>>> prospertb
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Jason P. Pickering
>>>> email: jason.p.pickering@xxxxxxxxx
>>>> tel:+46764147049
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Alex Tumwesigye
>>>
>>> Technical Advisor - DHIS2 (Consultant),
>>> Ministry of Health/AFENET  | HISP Uganda
>>> Kampala
>>> Uganda
>>> +256 774149 775, + 256 759 800161
>>> Skype ID: talexie
>>>
>>> IT Consultant (Servers, Networks and Security, Health Information
>>> Systems - DHIS2, Disease Outbreak & Surveillance Systems) & Solar Consultant
>>>
>>>
>>> "I don't want to be anything other than what I have been - one tree hill
>>> "
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>>
>>
>> --
>>
>> *******************************************
>>
>> Calle Hedberg
>>
>> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>>
>> Tel/fax (home): +27-21-685-6472
>>
>> Cell: +27-82-853-5352
>>
>> Iridium SatPhone: +8816-315-19119
>>
>> Email: calle.hedberg@xxxxxxxxx
>>
>> Skype: calle_hedberg
>>
>> *******************************************
>>
>>
>
>
> --
>
> *******************************************
>
> Calle Hedberg
>
> 46D Alma Road, 7700 Rosebank, SOUTH AFRICA
>
> Tel/fax (home): +27-21-685-6472
>
> Cell: +27-82-853-5352
>
> Iridium SatPhone: +8816-315-19119
>
> Email: calle.hedberg@xxxxxxxxx
>
> Skype: calle_hedberg
>
> *******************************************
>
>
> _______________________________________________
> 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
>
>