I was referred to this list for the below question... Can anyone help? Thanks
Hi all,
we are hoping to use DHIS2 as an analytics backend for our poison
information centre application...
What we are capturing are cases, normally the patient is not well
identified, but we plan to track the case itself as these normally
have a reasonably well defined exposure location and can have a
defined guid. Often they are a single event, but they can become many
events over a period of time. They are very useful for public health
in this form as they can be used to detect poisoning clusters for
investigation (poor restaurant hygiene, heavy metals contamination,
nerve agents etc)
We'd like to push them into DHIS2 as tracker items, but are wondering
how exactly to work around tracker expectation of tracking events
within a program/program stage?
Also for testing and migrations we'd like to be able to bulk load data
via csv, but is it possible to bulk load the tracked entities via csv
as well?
You need to clarify what your organisational hierarchy will be - it is one of the anchor dimensions in the DHIS. What is your “end” or 'leaf" type of orgunit? Health facility or suspected poison site? (restaurant, landfill, etc).
Do you intend to track poison cases over time (multiple events?) on a regular basis? If yes, Tracker will probably fit best even if you have limited tracked entity registration nformation to begin with. If no, I would use Tracker without registration (single event reporting).
Single events can be exported/imported via CSV - tracker data cannot, regrettable. We use Pentaho Kettle for bulk importing of tracker data. With tracker data, you have to populate multiple tables in sequence, with each step returning id values that are used in subsequent tables
the trackedentityinstance table (registration)
the programinstance table (enrollment)
the trackedentityattributevalue table (enrollment details)
the programstageinstance table (stage/event registration)
the trackedentitydatavalue table (stage/event details)
Best regards from Freetown, Sierra Leone
Calle
···
On 14 May 2018 at 11:47, Bret Watson bret@ticm.com wrote:
I was referred to this list for the below question… Can anyone help? Thanks
Subject: tracker question and applicability/hack
Hi all,
we are hoping to use DHIS2 as an analytics backend for our poison
information centre application…
What we are capturing are cases, normally the patient is not well
identified, but we plan to track the case itself as these normally
have a reasonably well defined exposure location and can have a
defined guid. Often they are a single event, but they can become many
events over a period of time. They are very useful for public health
in this form as they can be used to detect poisoning clusters for
investigation (poor restaurant hygiene, heavy metals contamination,
nerve agents etc)
We’d like to push them into DHIS2 as tracker items, but are wondering
how exactly to work around tracker expectation of tracking events
within a program/program stage?
Also for testing and migrations we’d like to be able to bulk load data
via csv, but is it possible to bulk load the tracked entities via csv
Thanks Calle.
1. I was planning on the poison information centre being the leaf, we
have several and they are "territorial" over data, plus they have
service regions. we will rely on the coordinates of the exposure site
for other mapping
2. yes and since a case might have several communication/calls over
time, I figured Tracker was the one...
3. I was afraid of that.. :(..but at least I now know it is possible thanks!
···
On 14 May 2018 at 18:38, Calle Hedberg <calle.hedberg@gmail.com> wrote:
Bret,
A few points;
1.
You need to clarify what your organisational hierarchy will be - it is one
of the anchor dimensions in the DHIS. What is your "end" or 'leaf" type of
orgunit? Health facility or suspected poison site? (restaurant, landfill,
etc).
2.
Do you intend to track poison cases over time (multiple events?) on a
regular basis? If yes, Tracker will probably fit best even if you have
limited tracked entity registration nformation to begin with. If no, I would
use Tracker without registration (single event reporting).
3.
Single events can be exported/imported via CSV - tracker data cannot,
regrettable. We use Pentaho Kettle for bulk importing of tracker data. With
tracker data, you have to populate multiple tables in sequence, with each
step returning id values that are used in subsequent tables
- the trackedentityinstance table (registration)
- the programinstance table (enrollment)
- the trackedentityattributevalue table (enrollment details)
- the programstageinstance table (stage/event registration)
- the trackedentitydatavalue table (stage/event details)
Best regards from Freetown, Sierra Leone
Calle
On 14 May 2018 at 11:47, Bret Watson <bret@ticm.com> wrote:
I was referred to this list for the below question... Can anyone help?
Thanks
Subject: tracker question and applicability/hack
Hi all,
we are hoping to use DHIS2 as an analytics backend for our poison
information centre application...
What we are capturing are cases, normally the patient is not well
identified, but we plan to track the case itself as these normally
have a reasonably well defined exposure location and can have a
defined guid. Often they are a single event, but they can become many
events over a period of time. They are very useful for public health
in this form as they can be used to detect poisoning clusters for
investigation (poor restaurant hygiene, heavy metals contamination,
nerve agents etc)
We'd like to push them into DHIS2 as tracker items, but are wondering
how exactly to work around tracker expectation of tracking events
within a program/program stage?
Also for testing and migrations we'd like to be able to bulk load data
via csv, but is it possible to bulk load the tracked entities via csv
as well?
I think we have somewhere around five tables, how do I carry IDs from
one table to another? I need to link the ingredients of substance to
the caller's substance and then to an individual call within the case
somehow
Thanks
Bret
···
On 14 May 2018 at 18:38, Calle Hedberg <calle.hedberg@gmail.com> wrote:
Bret,
A few points;
1.
You need to clarify what your organisational hierarchy will be - it is one
of the anchor dimensions in the DHIS. What is your "end" or 'leaf" type of
orgunit? Health facility or suspected poison site? (restaurant, landfill,
etc).
2.
Do you intend to track poison cases over time (multiple events?) on a
regular basis? If yes, Tracker will probably fit best even if you have
limited tracked entity registration nformation to begin with. If no, I would
use Tracker without registration (single event reporting).
3.
Single events can be exported/imported via CSV - tracker data cannot,
regrettable. We use Pentaho Kettle for bulk importing of tracker data. With
tracker data, you have to populate multiple tables in sequence, with each
step returning id values that are used in subsequent tables
- the trackedentityinstance table (registration)
- the programinstance table (enrollment)
- the trackedentityattributevalue table (enrollment details)
- the programstageinstance table (stage/event registration)
- the trackedentitydatavalue table (stage/event details)
Best regards from Freetown, Sierra Leone
Calle
On 14 May 2018 at 11:47, Bret Watson <bret@ticm.com> wrote:
I was referred to this list for the below question... Can anyone help?
Thanks
Subject: tracker question and applicability/hack
Hi all,
we are hoping to use DHIS2 as an analytics backend for our poison
information centre application...
What we are capturing are cases, normally the patient is not well
identified, but we plan to track the case itself as these normally
have a reasonably well defined exposure location and can have a
defined guid. Often they are a single event, but they can become many
events over a period of time. They are very useful for public health
in this form as they can be used to detect poisoning clusters for
investigation (poor restaurant hygiene, heavy metals contamination,
nerve agents etc)
We'd like to push them into DHIS2 as tracker items, but are wondering
how exactly to work around tracker expectation of tracking events
within a program/program stage?
Also for testing and migrations we'd like to be able to bulk load data
via csv, but is it possible to bulk load the tracked entities via csv
as well?
For LARGE once-off bulk imports (more than 50K cases), consider using Kettle or similar
For smaller bulk imports that might have to be repeated, I would insert cases one by one using API calls. A bit slow, but you can in general manage 5-10,000 cases per day - depending on server performance etc, of course.
regards
Calle
···
On 14 May 2018 at 13:04, Bret Watson bret@ticm.com wrote:
So to expand on this…
I think we have somewhere around five tables, how do I carry IDs from
one table to another? I need to link the ingredients of substance to
the caller’s substance and then to an individual call within the case
I am new to using DHIS2 tracker and right now I am facing the challenge mentioned above. I understand the solution for bulk importing of data can be done using Pentaho Kettle. Now, me being a novice, is there a guide on going that route?
Can anyone help? Thanks