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 conditio
Dear Knut and all,
Very interesting discussion. I would like to share my thought also on how
Sahana DMS included this. We had the concept of 'situation awareness'
-which I think is a well agreed term in surveillance. When counts reach a
certain level, it becomes an outbreak.
So, I think we may not
Hi Randy,
We have customized DHIS2 tracker for National TB Control and Chest Diseases
(NPTCCD) in Sri Lanka.
NPTCCD mainly uses DHIS2 tracker for Asthma, but on experimental basis
tracker is satisfactory for TB as well. We are trying to migrate to DHIS2
from a 'legacy' system.
I am copying this to
Ok, I'll report _categoryoptioncomboname as a bug.
In short it is,
[+] Exception (java.lang.RuntimeException): Failed to get all operands
[+] Caused by (com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException):
Table 'dhis._categoryoptioncomboname' doesn't exist
I'll send all details to launchpad
Hi Knut,
I am using MySQL on Linux with DHIS2. I have 157 tables including
'minmaxdataelement'.
So, I think this is a problem of generating tables than MySQL.
More or less similar behaviour (table does not exist) can be seen with the
use of Datasets >> Edit Compulsory Dataelements. There the error
5 matches
Mail list logo
