Re: [Dhis2-devs] [Dhis2-users] Filtering indicators by OU

[Calle Hedberg]

Hi,

I agree 100% with Marta's points. The practice of ensuring that all
catcombos (and attributecombos) are discrete break-downs of the DE is
generally advicable both because it is easier to avoid analytical mistakes
and because it's conceptually easier to explain and "internalise" for users.

That said, HISP-SA had been forced to create a number of exeptions to this
general rule:
- in order to generate stacked graphs for 90-90-90 monitoring, we had to
create derived data elements with non-discrete catcombos (so basically a
hack because of limitations in current DHIS2 reporting apps)
- for audit purposes, where facilities are revisited and the same data
collated & captured again, we also ended up using non-discrete catcombos
(original data, audit data, discrepancy between the two)
but those are special cases.

A common mistake related to attributeoptioncombos are when
attrributeoptioncombos are used to capture data from different partners for
the same orgunit - so e.g. the Ministry, MSF, PSI, and Red Cross are all
supporting the same facility. Then it is critical to ensure that the
different partners do not collate data for the same events/patients (aka
several partners "claim" the same patients because they do provide SOME
part of the total service delivery). So multiple partners provide services
to the same patients, it might be necessary to represent that using
different DEs, otherwise you end up doubling or tripling data (you do
remember the case for Botswana discovered by the New York Times a few years
ago, where PEPFAR claimed they supported ~16,000 ART patients in Botswana -
whereas they had actually only supported some workshops for the Ministry
staff providing ART services...)

The boundary between what's covered in the orghierarchy dimension and what
covered in the fact dimension also depend on what your ou reporting units
are. As an example, let us consider deaths from trauma in a conflict
situation. You might want to differentiate between
- deaths before anybody finds/attends the patient ("Trauma - dead on
site"). Those numbers are useful only for sensitisation etc.
- deaths while under EMRS care ("Trauma - dead on arrival"). Ditto use, but
also relevant to analyse EMRS equipment & staff skills + EMRS effectiveness
(no of ambulances, speed of transport)
- deaths while under the care of health personnel in a health facility
("Trauma - death"). Relevant for general sensitisation like the above, but
also for analysing quality of care, capacity, equipment/blood supplies, and
similar.
How many data elements you need for the above will depend on e.g. if EMRS
ambulances are separate reporting units - if yes, they will presumable
report on the first two types above.

Beyond the basic death due to trauma, you might then use catcombos to break
those down into other discrete categories e.g. Trauma due to gunshots, due
to IEDs, due to bombing, due to physical assault, etc etc. OR you might
want sub-divide deaths into patient characteristics (age, gender,
soldier/civilian, resident/refugee, etc). Most such break-downs can be
handled through catcombos as long as the category options are discrete - if
they are not, I would in general create separate Data elements.

As your DE granularity grows, you should also consider moving to case-based
data collection (possible even a full EMR system) with diagnosis,
procedures, outcomes etc - which enables more detailed data mining. You can
see that the small example above increasingly start looking like a list of
ICD-10 trauma codes.

Regards
Calle


On Thu, 15 Nov 2018 at 14:25, Marta Vila  wrote:

> Hi Damien!
>
> there is no magic formula for all these config decisions, but one pretty
> generic good practice would be that the aggregation of your cat. combo
> options into a data element should be meaningful. As it is the value that
> users will get when they select the DE in data visualizer or pivot table
> without details.
>
> From your example: I would say that using two different data elements for
> Malaria and Malaria (deaths) is correct. If you put them under one unique
> Malaria DE with a category (cases/deaths), the total number will be mixing
> cases and deaths, which is most likely incorrect from an analysis point of
> view and very easy to misinterpret by the users.
>
> Another generic good practice advise is to design your configuration
> thinking of your desired output (analysis).
>
> Hope it helps!
> Marta
>
> On Wed, 14 Nov 2018 at 20:17, Damien Scarlett <
> damien.scarl...@brussels.msf.org> wrote:
>
>> Hi Calle,
>>
>>
>>
>> Thanks for your 2c worth (we say 20c from where I am from J). I may be
>> explaining a different perspective here even still being a part of the
>> wider MSF posse but we (the Brussels office) have some indicators (e.g. %
>> of Morbidity / Mortality) that we have created additional related Data
>> Elements that map to the disease e.g. we have different DEs for ‘
>> *Malaria’* & for ‘*Malaria (death)*’ to use for Mortality-type

Re: [Dhis2-devs] New Android Capture App for DHIS 2 (v1.0.3) - User permissions

[Marta Vila]

Hi Kris,

sharing the answer here as well>

the app follows the same sharing permissions than the web. You need to
configure the sharing settings for each program. If, with the same user,
you see a program in web and not in android, then please report a bug.
If you don-t know how to configure the sharing settings, then please read
this

 documentation.

Best,
Marta

On Mon, 5 Nov 2018 at 14:50, Kristiyan Panayotov <
kristi...@logicaloutcomes.net> wrote:

> Dear DHIS2 experts,
>
>
>
> I came across one small issue with the new android app with DHIS2 version
> 2.29.
>
>
>
> Unless you are a superuser, you cannot see your Programs (looking in the
> Tracker functionalities).
>
> When I assign the “ALL”, only then I can see my data inside. Otherwise,
> log in is successful and I can ses all Org Units.
>
>
>
> Has anyone else, came across this issue? Is I a bug or a configuration
> problem?
>
>
>
> Kind regards,
>
> Kris
> ___
> 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
>
___
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

Re: [Dhis2-devs] [Dhis2-users] [DHIS2 Android] New Release of DHIS2 Android App (1.0.4)

[GUY ROLLAND KOUASSI]

Thanks marta








<< Nos pensées deviennent nos paroles, nos paroles deviennent nos actes,
nos actes deviennent nos coutumes, nos coutumes deviennent nos valeurs et
nos valeurs deviennent notre destinée *>>*



*  Guy Rolland KOUASSI*
*Administrateur Systèmes et Réseaux*


*  Ingénieur Des Systèmes Numériques de Communication

Téléphone : +(225)
44-744-156*


Le jeu. 15 nov. 2018 à 13:42, simon mugisa  a
écrit :

> thanks Marta will going to go through it.
>
>
> *Simon Robert Kununka*
> *DHIS2 implementor, Systems Analyst and Development Consultant*
>
> Uganda-Kampala
> Direct: + <%2B1-703-667-3954>256-777-108-323
> E-mail: nomisrmug...@gmail.com
>
>
> "Don't wish it was easier, wish you were better. Don't wish for less
> problems, wish for more skills. Don't wish for less change , wish for more
> wisdom."
>
> *This message and its attachments are confidential and solely for the
> intended recipients. If received in error, please delete them and notify
> the sender via reply e-mail immediately.*
>
>
>
>
>
>
>
> On Thu, Nov 15, 2018 at 1:57 PM Magoba Bridget 
> wrote:
>
>> Thanks Marta
>>
>> *Bridget Magoba*
>> *M/DHIS2 Implementer *
>>   [image: HISP Uganda]
>> *Health Information Systems Program-Uganda*
>> *www.hispuganda.org/ *
>> *Cell: +256 774659892 / +256703260439  *
>> *Email:* *bridget.mag...@gmail.com *
>> *SkypeId:* *magoba.bridget1*
>>
>>
>> On Thu, Nov 15, 2018 at 1:49 PM Marta Vila  wrote:
>>
>>> Dear DHIS2 Community,
>>>
>>> a new version of the *DHIS2 Android App*  is out today.
>>> You can find all details in the DHIS2 community
>>> .
>>> Have you already joined? All announcements and communications will be moved
>>> there soon!
>>>
>>> 1.0.4 is a bug fixing version, and includes some functional improvements
>>> as well.
>>> There is no new DHIS2 version compatibility (currently 2.29 and 2.30).
>>>
>>> This new version fixes the instability introduced 1.0.3 by the tablet
>>> view. There also fixes on Relationships, Data entry form /value types, TEI
>>> Dashboard/Tracker programs, Program Rules and others like sync and log-in
>>> processes.
>>>
>>> The functional improvements include the possibility to delete local data
>>> without logging out and we have incorporated the consumption of the
>>> back/end rule engine.
>>> *Detailed information:*
>>>
>>>- List of Jira issues 
>>>- Documentation 
>>>
>>>
>>> *Get it on:*
>>>
>>>- Google Play
>>>
>>>- Github
>>>
>>>
>>>
>>> Remember that, if you need to take screenshots or broadcast your screen
>>> for training purposes or demos sessions, there is a  **Training APK**
>>> available in Github
>>> .
>>>
>>> All this information is also available in the Android Section of the DHIS2
>>> web site !
>>>
>>> Best regards,
>>>
>>> on behalf of the Android team,
>>>
>>> Marta
>>>
>> ___
>> 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
>>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
___
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

Re: [Dhis2-devs] [Dhis2-users] Filtering indicators by OU

[Marta Vila]

Hi Damien!

there is no magic formula for all these config decisions, but one pretty
generic good practice would be that the aggregation of your cat. combo
options into a data element should be meaningful. As it is the value that
users will get when they select the DE in data visualizer or pivot table
without details.

>From your example: I would say that using two different data elements for
Malaria and Malaria (deaths) is correct. If you put them under one unique
Malaria DE with a category (cases/deaths), the total number will be mixing
cases and deaths, which is most likely incorrect from an analysis point of
view and very easy to misinterpret by the users.

Another generic good practice advise is to design your configuration
thinking of your desired output (analysis).

Hope it helps!
Marta

On Wed, 14 Nov 2018 at 20:17, Damien Scarlett <
damien.scarl...@brussels.msf.org> wrote:

> Hi Calle,
>
>
>
> Thanks for your 2c worth (we say 20c from where I am from J). I may be
> explaining a different perspective here even still being a part of the
> wider MSF posse but we (the Brussels office) have some indicators (e.g. %
> of Morbidity / Mortality) that we have created additional related Data
> Elements that map to the disease e.g. we have different DEs for ‘
> *Malaria’* & for ‘*Malaria (death)*’ to use for Mortality-type
> indicators. Mind you this is mapping to the aggregate data capture.
>
>
>
> I’m unsure if there are any Best Practices for these types of indicators &
> how to set them up (I would presume they are common) but if there is any we
> would be happy to know them & how organisations have configured these.
>
> From reading the below it may be wise to create Cat. Combos instead of
> additional DE’s but other people may have experience in which is best to
> capture this & easier to manage over the long term.
>
>
>
> Have a good evening,
>
> *Damien *
>
>
>
> *From:* Dhis2-users  brussels.msf@lists.launchpad.net> *On Behalf Of *Calle Hedberg
> *Sent:* Wednesday, 14 November 2018 6:02 PM
> *To:* Jaime Bosque 
> *Cc:* DHIS 2 Users list ; dhis2-devs <
> dhis2-devs@lists.launchpad.net>
> *Subject:* Re: [Dhis2-users] [Dhis2-devs] Filtering indicators by OU
>
>
>
> Jaime and others,
>
>
>
> Using category combos (or attribute combos) are fundamentally/conceptually
> the same as having multiple data elements, because at the end of the day
> you will have the same number of physical records in your database (e.g.
> the datavalue table). Or in other words, the level of "granularity" in your
> data remains the same. (The main advantage in using catcombos is a
> reduction in the amount of meta-data records you maintain: so instead of
> creating and maintaining let us say 300 data elements, you create and
> maintain 50 data elements with 2 gender catoptions and 3 age catoptions (55
> meta-data items) -> 50x2x3=300 dataelement variants.
> (Maintaining 55 items is presumably easier than 300 - although for many
> users it's also more difficult to fully grasp and I have seen a lot of
> databases where the catcombos have become really messy over the years.
> Typical examples are multiple changes in e.g. age groups over time).
>
>
>
> There are situations where you can use for instance orgunit groups to get
> "ou-dependent" indicator values, but I would in general not recommend them
> except when the relation between orgunit(type) and indicator is an inherent
> and stable dimension of every indicator at a particular orgunit level. A
> practical example:
>
> 1.
>
> If you collect data per hospital, and the hospital have 8 different wards
> (1 maternity, 2 medical, 2 surgical, 1 paediatrics, 1 ICU, 1 orthopaedics),
> and you need e.g. Bed Utilisation Rates for each ward type, you would
> typically create one data element & catcombo set for each type:
>
> Inpatient days - maternity, inpatient days - medical, inpatients
> separations - maternity, inpatient separations - medical, inpatient death -
> maternity, inpatient death - medical, etc.
>
> 2.
>
> If you on the other hand collect the same data per hospital ward (i.e.
> expand your orghierarchy to the sub-facility level), and these are grouped
> per ward type, you need only
>
> inpatient days, inpatient separations, inpatient deaths
>
> and you would do analysis per ou group. NOTE, though, that such a model
> means you cannot change a ward's orgunittype without messing up the
> historic data analysis. So if a ward is changed from a medical to a
> surgical ward, you would have to close the medical ou and open a surgical
> ou.
>
>
>
> Another perspective on the same is to say that the higher granularity you
> have in the geographic/administrative dimension (orghierarchy), the less
> granularity tend to be required in the fact dimension (data
> elements/indicators). When implementing something like option 2, though,
> you must also consider aggregation of data - if for instance some of your
> indicators are using higher level data (e.g. district totals) for some
> 

Re: [Dhis2-devs] [DHIS2 Android] New Release of DHIS2 Android App (1.0.4)

[simon mugisa]

thanks Marta will going to go through it.


*Simon Robert Kununka*
*DHIS2 implementor, Systems Analyst and Development Consultant*

Uganda-Kampala
Direct: + <%2B1-703-667-3954>256-777-108-323
E-mail: nomisrmug...@gmail.com


"Don't wish it was easier, wish you were better. Don't wish for less
problems, wish for more skills. Don't wish for less change , wish for more
wisdom."

*This message and its attachments are confidential and solely for the
intended recipients. If received in error, please delete them and notify
the sender via reply e-mail immediately.*







On Thu, Nov 15, 2018 at 1:57 PM Magoba Bridget 
wrote:

> Thanks Marta
>
> *Bridget Magoba*
> *M/DHIS2 Implementer *
>   [image: HISP Uganda]
> *Health Information Systems Program-Uganda*
> *www.hispuganda.org/ *
> *Cell: +256 774659892 / +256703260439  *
> *Email:* *bridget.mag...@gmail.com *
> *SkypeId:* *magoba.bridget1*
>
>
> On Thu, Nov 15, 2018 at 1:49 PM Marta Vila  wrote:
>
>> Dear DHIS2 Community,
>>
>> a new version of the *DHIS2 Android App*  is out today.
>> You can find all details in the DHIS2 community
>> .
>> Have you already joined? All announcements and communications will be moved
>> there soon!
>>
>> 1.0.4 is a bug fixing version, and includes some functional improvements
>> as well.
>> There is no new DHIS2 version compatibility (currently 2.29 and 2.30).
>>
>> This new version fixes the instability introduced 1.0.3 by the tablet
>> view. There also fixes on Relationships, Data entry form /value types, TEI
>> Dashboard/Tracker programs, Program Rules and others like sync and log-in
>> processes.
>>
>> The functional improvements include the possibility to delete local data
>> without logging out and we have incorporated the consumption of the
>> back/end rule engine.
>> *Detailed information:*
>>
>>- List of Jira issues 
>>- Documentation 
>>
>>
>> *Get it on:*
>>
>>- Google Play
>>
>>- Github 
>>
>>
>> Remember that, if you need to take screenshots or broadcast your screen
>> for training purposes or demos sessions, there is a  **Training APK**
>> available in Github
>> .
>>
>> All this information is also available in the Android Section of the DHIS2
>> web site !
>>
>> Best regards,
>>
>> on behalf of the Android team,
>>
>> Marta
>>
> ___
> 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
>
___
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

Re: [Dhis2-devs] [Dhis2-users] security issue - upgrade action required for 2.28 and older versions

[tuzo engelbert]

Noted with thanks

On Thu, Nov 15, 2018 at 3:06 PM Lars Helge Øverland  wrote:

> Hi all,
>
> a potential serious security issue has been discovered with one of the
> libraries used by DHIS 2. The issue can potentially allow attackers to
> write or copy files to disk in arbitrary locations. The attacker needs to
> be logged in to DHIS 2 (authenticated) to do this.
>
> The affected versions are *DHIS 2.28 and older*.
>
> We have patched the following versions: 2.25, 2.26, 2.27, 2.28.
>
> We recommend that you upgrade to the latest build of the mentioned
> releases if you are affected. We won't disclose more info about this issue
> on the public mailing list.
>
>
> best,
>
> Lars
>
>
> --
>
> Lars Helge Øverland
> Technical lead, DHIS 2
> University of Oslo
> l...@dhis2.org
> https://www.dhis2.org
>
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>
___
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

[Dhis2-devs] security issue - upgrade action required for 2.28 and older versions

[Lars Helge Øverland]

Hi all,

a potential serious security issue has been discovered with one of the
libraries used by DHIS 2. The issue can potentially allow attackers to
write or copy files to disk in arbitrary locations. The attacker needs to
be logged in to DHIS 2 (authenticated) to do this.

The affected versions are *DHIS 2.28 and older*.

We have patched the following versions: 2.25, 2.26, 2.27, 2.28.

We recommend that you upgrade to the latest build of the mentioned releases
if you are affected. We won't disclose more info about this issue on the
public mailing list.


best,

Lars


-- 

Lars Helge Øverland
Technical lead, DHIS 2
University of Oslo
l...@dhis2.org
https://www.dhis2.org
___
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

[Dhis2-devs] Help needed: Conflict - Value_not_valid_date error on tablets...

[M.Selvaraaj Prabu]

Hi all,

Kindly note I am getting the below error on my tablet when I try to sync
the data between Tracker App and the DHIS2 database.

   - Conflict - value_not_valid_date

Please note the program has several stages and the error occurs only on a
certain stage. At the same time, this stage works fine on the web
interface.

Kindly assist me in anyways to resolve the issue.

NB: I am using DHIS2 ver 2.29.

Thank you in advance for any assistance.

Regards

MSP
___
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

Re: [Dhis2-devs] [DHIS2 Android] New Release of DHIS2 Android App (1.0.4)

[Magoba Bridget]

Thanks Marta

*Bridget Magoba*
*M/DHIS2 Implementer *
  [image: HISP Uganda]
*Health Information Systems Program-Uganda*
*www.hispuganda.org/ *
*Cell: +256 774659892 / +256703260439  *
*Email:* *bridget.mag...@gmail.com *
*SkypeId:* *magoba.bridget1*


On Thu, Nov 15, 2018 at 1:49 PM Marta Vila  wrote:

> Dear DHIS2 Community,
>
> a new version of the *DHIS2 Android App*  is out today.
> You can find all details in the DHIS2 community
> .
> Have you already joined? All announcements and communications will be moved
> there soon!
>
> 1.0.4 is a bug fixing version, and includes some functional improvements
> as well.
> There is no new DHIS2 version compatibility (currently 2.29 and 2.30).
>
> This new version fixes the instability introduced 1.0.3 by the tablet
> view. There also fixes on Relationships, Data entry form /value types, TEI
> Dashboard/Tracker programs, Program Rules and others like sync and log-in
> processes.
>
> The functional improvements include the possibility to delete local data
> without logging out and we have incorporated the consumption of the
> back/end rule engine.
> *Detailed information:*
>
>- List of Jira issues 
>- Documentation 
>
>
> *Get it on:*
>
>- Google Play 
>- Github 
>
>
> Remember that, if you need to take screenshots or broadcast your screen
> for training purposes or demos sessions, there is a  **Training APK**
> available in Github
> .
>
> All this information is also available in the Android Section of the DHIS2
> web site !
>
> Best regards,
>
> on behalf of the Android team,
>
> Marta
>
___
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

Re: [Dhis2-devs] WHERE TO FIND APPLICATION TITLE SECTION IN DHIS2 2.30

[M.Selvaraaj Prabu]

Hi Stanley.

They are in the Appearance only. But I have seen those parameters appear
only upon selection of the language. Please select the language first and
you will see them.

Regards

MSP

Sent via mobile


On Thu, 15 Nov 2018 07:39 Stanley Kalyati  In later versions,we were able to find under Appearance on systems
> settings,the Application Titles and Introduction where we would describe
> our system.
>
> Where can i find these two areas in DHIS 2.30?
>
> They seem not to be under General Settings.
>
> Thanks
>
> Stanley
> ___
> 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
>
___
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

Re: [Dhis2-devs] [Dhis2-users] Filtering indicators by OU

[Jaime Bosque]

Thanks a lot, Calle, for your detailed response. I will share it with the team 
here.

Best regards,


Jaime Bosque Torrecilla

Applications Technician, eHealth & Operations Applications (‘Apps4OPS’)

Projects & IT Unit
Médecins Sans Frontières (MSF) Spain – Barcelona Office

Fixed: +34 935 213 048 – Skype: msfe-healthdatatech2

Email: 
jaime.bos...@barcelona.msf.org – 
www.msf.org



From: Damien Scarlett
Sent: 14 November 2018 20:16:47
To: calle.hedb...@gmail.com; Jaime Bosque
Cc: DHIS 2 Users list; dhis2-devs
Subject: RE: [Dhis2-users] [Dhis2-devs] Filtering indicators by OU


Hi Calle,



Thanks for your 2c worth (we say 20c from where I am from :)). I may be 
explaining a different perspective here even still being a part of the wider 
MSF posse but we (the Brussels office) have some indicators (e.g. % of 
Morbidity / Mortality) that we have created additional related Data Elements 
that map to the disease e.g. we have different DEs for ‘Malaria’ & for ‘Malaria 
(death)’ to use for Mortality-type indicators. Mind you this is mapping to the 
aggregate data capture.



I’m unsure if there are any Best Practices for these types of indicators & how 
to set them up (I would presume they are common) but if there is any we would 
be happy to know them & how organisations have configured these.

>From reading the below it may be wise to create Cat. Combos instead of 
>additional DE’s but other people may have experience in which is best to 
>capture this & easier to manage over the long term.



Have a good evening,

Damien



From: Dhis2-users 
 On 
Behalf Of Calle Hedberg
Sent: Wednesday, 14 November 2018 6:02 PM
To: Jaime Bosque 
Cc: DHIS 2 Users list ; dhis2-devs 

Subject: Re: [Dhis2-users] [Dhis2-devs] Filtering indicators by OU



Jaime and others,



Using category combos (or attribute combos) are fundamentally/conceptually the 
same as having multiple data elements, because at the end of the day you will 
have the same number of physical records in your database (e.g. the datavalue 
table). Or in other words, the level of "granularity" in your data remains the 
same. (The main advantage in using catcombos is a reduction in the amount of 
meta-data records you maintain: so instead of creating and maintaining let us 
say 300 data elements, you create and maintain 50 data elements with 2 gender 
catoptions and 3 age catoptions (55 meta-data items) -> 50x2x3=300 
dataelement variants. (Maintaining 55 items is presumably 
easier than 300 - although for many users it's also more difficult to fully 
grasp and I have seen a lot of databases where the catcombos have become really 
messy over the years. Typical examples are multiple changes in e.g. age groups 
over time).



There are situations where you can use for instance orgunit groups to get 
"ou-dependent" indicator values, but I would in general not recommend them 
except when the relation between orgunit(type) and indicator is an inherent and 
stable dimension of every indicator at a particular orgunit level. A practical 
example:

1.

If you collect data per hospital, and the hospital have 8 different wards (1 
maternity, 2 medical, 2 surgical, 1 paediatrics, 1 ICU, 1 orthopaedics), and 
you need e.g. Bed Utilisation Rates for each ward type, you would typically 
create one data element & catcombo set for each type:

Inpatient days - maternity, inpatient days - medical, inpatients separations - 
maternity, inpatient separations - medical, inpatient death - maternity, 
inpatient death - medical, etc.

2.

If you on the other hand collect the same data per hospital ward (i.e. expand 
your orghierarchy to the sub-facility level), and these are grouped per ward 
type, you need only

inpatient days, inpatient separations, inpatient deaths

and you would do analysis per ou group. NOTE, though, that such a model means 
you cannot change a ward's orgunittype without messing up the historic data 
analysis. So if a ward is changed from a medical to a surgical ward, you would 
have to close the medical ou and open a surgical ou.



Another perspective on the same is to say that the higher granularity you have 
in the geographic/administrative dimension (orghierarchy), the less granularity 
tend to be required in the fact dimension (data elements/indicators). When 
implementing something like option 2, though, you must also consider 
aggregation of data - if for instance some of your indicators are using higher 
level data (e.g. district totals) for some denominators, you might end up 
struggling to get that.



Jaime do not provide any specifics about exactly what A,B,C is and whether each 
of them are firmly and permanently bonded to specific outypes only so it is 
difficult to know if "transferring" some of the granularity to the orgunit 
dimension is advisable (as indicated above, aggregated analysis needs might 
also play a role). As a general rule, I would only 

Re: [Dhis2-devs] [Dhis2-users] WHERE TO FIND APPLICATION TITLE SECTION IN DHIS2 2.30

[Hendrik de Graaf]

Hello Stanley,

You can find these settings here: 
https://play.dhis2.org/2.30/dhis-web-settings/index.html#/appearance

A note on this: I have recently worked on an issue to make the UI of this form 
a bit clearer. If your build predates this build revision, it could be that you 
are only seeing the “Select language” dropdown at the very top of the form. 
After you select a language in that dropdown, the other fields (e.g. 
application title, etc) become visible.

Best regards,
Hendrik
On 15 Nov 2018, 06:39 +0100, Stanley Kalyati , wrote:
> In later versions,we were able to find under Appearance on systems 
> settings,the Application Titles and Introduction where we would describe our 
> system.
>
> Where can i find these two areas in DHIS 2.30?
>
> They seem not to be under General Settings.
>
> Thanks
>
> Stanley
> ___
> Mailing list: https://launchpad.net/~dhis2-users
> Post to : dhis2-us...@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help : https://help.launchpad.net/ListHelp
___
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