Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

HNQIS 2 (H2) has been redeveloped using the DHIS2 tracker data model, and uses DHIS2 standard Android app, in contrast to H1, which required the use of a custom Android App. Additionally, H2 can now use either the web-based tracker capture app or the standard DHIS2 android app. Optionally, a for of DHIS2 android app add functionality for providing the feedback functionality.

Use of DHIS2 tracker data model

Doesn’t use event - why?

details of the model

Org Units: Facilities vs Providers

Most DHIS2 server already have their Org Unit structures defined to the facility level. Only some used a further level to register the actual provider (the health

Option 1: Provider as the OU (default, recommended)

Sub-National (OU)
|__ Facility (OU)
           |__  Provider (OU)
|__ Assessment Cycle (TEI): Start/ End, Scoring data.
|__ Feedback (Managed events - future)
|__ Actions (Repeatable event)

Main advantages

  • UX: each TEI is single assessment, with related required set of actions and feedback.

  • Compatible with UiO’s future managed events design to address the feedback functionality - each failed question creates one managed event, which results in multiple entries.

  • Allows assignment of specific checklists to each provider (as they are OUs)

  • Analytics: fully fledge, at provider level

Disadvantages

  • It requires the provider to be set as an org unit before the assessment can be conducted.

Option 2: Facility as the OU / Provider as TEA

This is a variation of Option 1, which introduces the use of a TEA (Tracked Entity Attribute) that allows to record the provider name (free text).

Sub-National (OU)
|__ Facility (OU) 
|__ 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

Main advantages

  • It is rare to have a full list of providers available in advance to set up as OUs. Using TEI to enrol a provider during the visit is more realistic for on-the-ground implementation.

Disadvantages

  • Analytics can only be generated by facility, NOT by provider (provider shows only at line-listing level)

  • FEEDBACK sharing is at the Org Unit level, not at the provider level.

Option 3: Facility as the OU / Provider as TEI: NOT RECOMMENDED

Note: you will need to modify PSI’s provided metadata packages for this option.

Sub-National (OU)
|__ Facility (OU)
|__  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.

Main advantages

  • It is rare to have a full list of providers available in advance to set up as OUs. Using TEI to enrol a provider during the visit is more realistic for on-the-ground implementation.

Disadvantages:

  • Mixes assessment/ actions and feedback events (manged events for feedback)

  • No labels