Acronyms
H2 - HNQIS
...
version 2.0 and newer
OU - Organisational Unit
PCA - Program Configuration App
TEI - Tracked Entity Instance
TEA - Tracked Entity Attribute
For a full list of all acronyms and word, lists click /wiki/spaces/documentation/pages/14024762
| Info |
|---|
H2 has been configured to use the DHIS2 tracker data model |
...
. H2 can be used either on the DHIS2 tracker capture app or with the DHIS2 standard Android app, this is in contrast to H1, which required the use of a custom Android App. |
...
Use of DHIS2 tracker data model
Doesn’t use event - why?
details of the model
Org Units: Facilities vs Providers
...
Optionally, access to the feedback functionality is available by using a PSI’s fork android app. (links, links, links) |
DHIS2 Tracker Data Model and Options
An assessment is formed from multiple types of events (DHIS2 Program Stages).
The actual assessment (A none-repeatable stage), which contains all the questions (this could be hundreds)
Action items (a repeatable stage). Each entry is a corrective action that is agreed upon after the supervision
Feedback program stage, in the form of ‘managed events’. This feature doesn’t exist yet, but it is planned by UiO. It could result in many entries, one per failed question.
Org Units Assignment: Facilities vs Providers
When a H2 Program is created, there are different levels at which you can enable it using the Program Org Unit assignment feature.
Most DHIS2 server already has their Org Unit structures with the facility level as their lowest level.
Only some use a subsequent level to register the actual health provider, by name, allowing the recording and analysis of data specific to the health officer’s performance.
We present below the different ways that you can do the Org Unit assignment of H2 assessment lists, with the advantages and disadvantages.
Option 1: Provider as the OU (
...
recommended)
Sub-National (OU)
...
Facility (OU)
...
Provider (OU)
...
--> Program OU assignment
Assessment Cycle (TEI): Start/ End, Scoring data
...
...
Feedback (Managed events - future)
...
Actions (Repeatable event)
| Tip |
|---|
...
Advantages
|
| Warning |
|---|
Disadvantages
|
Option 2: Facility as the OU / Provider as TEA
This is a variation of Option 1, which introduces the use of a TEA
...
that allows
...
recording the provider name (free text).
Note: you will need to modify PSI’s provided metadata packages for this option. You will need to create a new TEA for the provider, and add it to the TEI assessment.
Sub-National (OU)
...
Facility (OU)
...
--> Program OU assignment
Assessment Cycle (TEI): Start/ End, Scoring data.
TEA: PROVIDER
...
Assessment (single events)
...
Feedback (Managed events - future. Could be 100s)
...
Actions (Repeatable event - 1 to 5 per assessment
| Tip |
|---|
...
Advantages
|
...
|
| Warning |
|---|
Disadvantages
|
...
|
...
|
...
|
Option 3: Facility as the OU / Provider as TEI
...
The idea is to ‘enrol’ a provider as a tracked entity, and then conduct all assessments in that Tracked Entity.
Note: you will need to modify PSI’s provided metadata packages for this option. You will need to create a new type of Tracked Entity, and change the PCA.
Sub-National (OU)
...
Facility (OU)
...
--> Program OU Assignment
Provider (TEI)
...
Assessment (Repeatable event, one per assessment)
...
Feedback (Managed events - future. Could be 100s)
...
Actions (Repeatable event - 1 to 5 per assessment
NOTE: we cannot use enrolments as DHIS2 doesn’t yet (2.38) has enrolment analytics.
| Tip |
|---|
Advantages
|
...
|
| Warning |
|---|
Disadvantages:
|
...
|
Option 4: Provider as TEI, Assessment as Enrolment
Not considered - analytics is not possible: we cannot use enrolments as DHIS2 with the current version (2.38) which does not have enrolment analytics.
Previous
Home
Next