structuring tracker data elements

Support - Assistance technique
1

Hi All,
We are hoping to use DHIS2 to collect and report on data from poison
information centres..

I'm guessing a lot fo these questions are answered in level one or
above academies, but I'm in Australia and getting to the academies is
pretty hard..

···

__

Tracker seems to be the best option as we want to collect
dis-aggregated data that is connected to a case - I plan to use the
Case as the identifier rather than the patient, as the patient details
are not necessarily being collected in a consistent manner, but I have
a robust case ID against each case.

The challenge I have is in the details :slight_smile:

Enrolling a case seems logical, things like patient details, location
of exposure, exposure details are all one time data elements, which
might be corrected during a case, but are not going to need to be seen
independently.

The fun part starts in two areas
1. A case can consist of 1 or more contacts between the Poison
Information Centre (PIC) and other parties - each contact would record
the caller details and location - this seems like something I can
record as part of the "program" against the case. Is this reasonable?

2. The Symptoms and treatment for a case may be added or modified
during the case, so might be tied to the contact form, but the
symptoms and treatment are very long lists and may contain one or more
items from each list - should I keep these as lots of data boolean
data elements, or as DEs with options?

3. The poisoning substance can be one or more "brand names" eg.
panadol osteo, which actually consist of one or more "Centre
Substances" - that is the actual toxic substance - I have no real idea
how to record these against the program - help?

2

Hi Bret,

Tracker will do that. But for those special cases you listed here, you may consider using a custom form liked to some metadata (sysmptoms, types of poison, etc) defined in datastore.

Alex

···

On Monday, May 14, 2018, Bret Watson bret@ticm.com wrote:

Hi All,

We are hoping to use DHIS2 to collect and report on data from poison

information centres…

I’m guessing a lot fo these questions are answered in level one or

above academies, but I’m in Australia and getting to the academies is

pretty hard…

__

Tracker seems to be the best option as we want to collect

dis-aggregated data that is connected to a case - I plan to use the

Case as the identifier rather than the patient, as the patient details

are not necessarily being collected in a consistent manner, but I have

a robust case ID against each case.

The challenge I have is in the details :slight_smile:

Enrolling a case seems logical, things like patient details, location

of exposure, exposure details are all one time data elements, which

might be corrected during a case, but are not going to need to be seen

independently.

The fun part starts in two areas

  1. A case can consist of 1 or more contacts between the Poison

Information Centre (PIC) and other parties - each contact would record

the caller details and location - this seems like something I can

record as part of the “program” against the case. Is this reasonable?

  1. The Symptoms and treatment for a case may be added or modified

during the case, so might be tied to the contact form, but the

symptoms and treatment are very long lists and may contain one or more

items from each list - should I keep these as lots of data boolean

data elements, or as DEs with options?

  1. The poisoning substance can be one or more “brand names” eg.

panadol osteo, which actually consist of one or more "Centre

Substances" - that is the actual toxic substance - I have no real idea

how to record these against the program - help?

Mailing list: https://launchpad.net/~dhis2-users

Post to : dhis2-users@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-users

More help : https://help.launchpad.net/ListHelp

–
Alex Tumwesigye

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 "

3

Actually since the substances are so many and so complex we have our own app, I wouldn’t want to try and do this in a tracker form :slight_smile:

···

On 15/05/18 02:56, Alex Tumwesigye wrote:

  Hi Bret,

    Tracker will do that. But for those special cases you listed here, you may consider using a custom form liked to some metadata (sysmptoms, types of poison, etc) defined in datastore.

Alex

    On Monday, May 14, 2018, Bret Watson <bret@ticm.com        > wrote:

Hi All,

      We are hoping to use DHIS2 to collect and report on data from poison

      information centres..



      I'm guessing a lot fo these questions are answered in level one or

      above academies, but I'm in Australia and getting to the academies is

      pretty hard..



      __



      Tracker seems to be the best option as we want to collect

      dis-aggregated data that is connected to a case - I plan to use the

      Case as the identifier rather than the patient, as the patient details

      are not necessarily being collected in a consistent manner, but I have

      a robust case ID against each case.



      The challenge I have is in the details :)



      Enrolling a case seems logical, things like patient details, location

      of exposure, exposure details are all one time data elements, which

      might be corrected during a case, but are not going to need to be seen

       independently.



      The fun part starts in two areas

      1. A case can consist of 1 or more contacts between the Poison

      Information Centre (PIC) and other parties - each contact would record

      the caller details and location - this seems like something I can

      record as part of the "program" against the case. Is this reasonable?



      2. The Symptoms and treatment for a case may be added or modified

      during the case, so might be tied to the contact form, but the

      symptoms and treatment are very long lists and may contain one or more

      items from each list  - should I keep these as lots of data boolean

      data elements, or as DEs with options?



      3. The poisoning substance can be one or more "brand names" eg.

      panadol osteo, which actually consist of one or more "Centre

      Substances" - that is the actual toxic substance - I have no real idea

      how to record these against the program - help?



      _______________________________________________

      Mailing list: [https://launchpad.net/~dhis2-users](https://launchpad.net/%7Edhis2-users)

      Post to     : dhis2-users@lists.launchpad.net

      Unsubscribe : [https://launchpad.net/~dhis2-users](https://launchpad.net/%7Edhis2-users)

      More help   : [https://help.launchpad.net/ListHelp](https://help.launchpad.net/ListHelp)

  --
                      Alex Tumwesigye

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 "