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

Version 1 Next »

HNQIS 2.X Building on lessons learned from use of the previous version, HNQIS 2 has been redeveloped using the DHIS2 tracker data model, and has made the need to use of a custom app optional. Instead HNQIS 2 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

Option 1: Provider as the OU (recommended)

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

Main advantages

  • UX: each TEI has a single pre-assessment, assessment and set of actions

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

  • Allows assignment of specific checklists to each provider

  • Analytics: fully fledge, at provider level

Option 2: Facility as the OU / Provider as TEA (alternative)

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

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

  • Dashboard can only be generated by facility, NOT by provider (only line listing)

  • 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 enrollment analytics.

Disadvantages:

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

  • No labels