dhis2-users team mailing list archive

[wanjala pepela <wanjala2p@xxxxxxxxx>]

Yes, that is right though every disease entity has a threshold level which need be in build into the flacking or trackers for the diseases are at different level of either earmarked for eradication where a single case confirmed is outbreak or elimination and control.

regards
 
PEPELA WANJALA
MINISTRY OF HEALTH HEADQUARTERS
HEALTH INFORMATION SYSTEM
AFYA HOUSE, HIS LG 37
P.O BOX 30016, NAIROBI, KENYA
TEL: +254 (020) 2717077 EXT 45097
CELL: +254 (0) 722375633 or 0202033363
EMAIL: wanjala2p@xxxxxxxxx
            hmis@xxxxxxxxxxxx
 "HealthInformation Management - Making a World of Difference”
 



On Thursday, February 20, 2014 4:15 PM, Roshan Hewapathirana <roshanhewapathirana@xxxxxxxxx> wrote:
 
I agree with the definition. My suggestion was to make the 2 concepts you mentioned 'properties' of (any applicable) data element, instead of data elements themselves.


If we are to create data elements for all conditions need to be under surveillance, we need to create 2 data elements per condition (suspected and outbreak) I think.
However, if suspected (property:under surveillance) is a property of any data element, we don't have to create new data elements and enter data. We can just re-use the data entered and when counts reach the level (property:upper limit to be notified as outbreak), can be visualized and trigger alerts. 

If we do this, we can keep more than one condition dynamically under surveillance easily.



On 20 February 2014 13:39, wanjala pepela <wanjala2p@xxxxxxxxx> wrote:

A disease outbreak is the occurrence of cases of disease in excess of what would normally be expected in a defined community, geographical area or season. an Outbreak is a term used in epidemiology to describe an occurrence of disease greater than would otherwise be expected at a particular time and place. if we are designing a data element, then we should use the term suspected disease or outbreak.
>
>