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 4 Next »

In order to keep DHIS2 as clean and organised as possible, User Groups and Roles should be defined to limit access to the features available in DHIS2.

User Roles

Several DHIS2 Authorities are required in order to be able to interact with the H2 Metadata and Data. The authorities will grant the users permission to different DHIS2 configurations and features.

Please Note

If you’re using the PCA, you probably already have the necessary User Roles available in the server. Some are installed as the initial setup of the PCA, while others are installed as part of the HNQIS2 Metadata Package.

For Data Capture (Web and Android App)

A User Role for Data Capture should include the following Authorities:

Web data capture

Android data capture

  • Apps:

    • Browser Cache Cleaner App

    • Dashboard App

    • Tracker Capture App

  • Tracker:

    • Uncomplete events

    • View event analytics

  • Tracker:

    • Uncomplete events

Note: as of DHIS2 Android 2.6.2 a user do not needs any authority to capture DHIS2 tracker data

For Program Administration

Program Administration requires several Authorities depending on the needs of the Administrator. All the recommended Authorities are listed below:

Metadata authorities

Authority required to create edit metadata objects in the DHIS2 server.

*Denote:

The Public access should only be provided for analyses such as Dashbaord. Maps and Visualisation.

Avoid providing Public access for Program-related Metadate, this function is reserved for HNQIS Administrators only.

The use of Public sharing: we normally recommend limiting the use of Public sharing only for analyses (Dashboard, Maps and Visualizations). We do not recommend the use of public sharing for program-related metadata, so editing of it is limited to the official HNQIS administrators.

Metadata Object

Authority

Dashboard (for H2 Metadata Generation)

  • Add/Update Public

  • Add/Update Private

Data Element

  • Add/Update Public*

  • Add/Update Private

Legend Set

  • Add/Update Public*

  • Add/Update Private

Map (for H2 Metadata Generation)

  • Add/Update Public

  • Add/Update Private

Option Set

  • Add/Update Public*

  • Add/Update Private

Program

  • Add/Update Public*

  • Add/Update Private

  • Delete

Program Indicator

  • Add/Update Public*

  • Add/Update Private

  • Delete

Program Rule

  • Add/Update Public*

  • Delete

Program Stage

  • Add/Update Public*

  • Delete

ProgramStageSection

  • Add/Update Public*

  • Delete

Visualization (For H2 Metadata Generation)

  • Add/Update Public

  • Add/Update Private

  • Delete

Other authorities

App access authority is required to administer H2 programs in a DHIS2 server.

App

  • Browser Cache Cleaner App

  • Dashboard App

  • Datastore App (Required if using Program Config App)

  • Maintenance App

  • Tracker Capture App (To check configurations)

  • Program Config App (Recommended)

Tracker

  • Manage program rule

Import/Export

  • Export metadata (Required if using Program Config App)

  • Import metadata (Required if using Program Config App)

System

  • View User (To assign Sharing Settings to other users)

User Groups setup (DHIS2 sharing)

User Groups in H2 are used to define the users that will be able to perform maintenance to the different H2 Programs (referred to as Admins) and the users that will be able to interact with said Programs (referred to simply as Users).

By default, the HNQIS2 Metadata Package includes two User Groups that can be used as templates for other groups: HNQIS2 - Admins and HNQIS2- Users.

Please Note

If you’re using the PCA, the HNQIS2 Metadata Package (that also includes the base User Groups) can be installed/updated easily.

It is recommended to that a pair of Groups for Admins and Users is created for each use case. For instance, it is a common practice to separate Checklists by country, meaning that a group of three countries: Kenya, Zimbabwe and Angola; should have the following sets of User Groups:

Kenya (KE)

Zimbabwe (ZW)

Angola (AO)

  • KE HNIQS2 - Admins

  • KE HNQIS2 - Users

  • ZW HNIQS2 - Admins

  • ZW HNQIS2 - Users

  • AO HNIQS2 - Admins

  • AO HNQIS2 - Users

If your server includes a multi-country setup, it is a good practice to include the ISO code of the country as a prefix for each User Group.

After the User Groups are created, the Sharing Settings of the H2 Programs should include a configuration as follows:

User Group

Metadata Settings

Data Capture Settings

Admins

Can Edit and View

Can Capture and View

Users

Can View only

Can Capture and View

User Setup

A H2 user is normally referred to as Quality Supervisor or Supervisor. This is the person that visits the actual facility/provider and performs the assessments. A supervisor will have a specific number of facilities/providers assigned to her/him, normally between 20 to 50 facilities/providers

set the name, last name, phone, blah, blah, password

Assign User Roles (see above)

Assign Org Units for data capture and data analysis

Data Capture OUs (screenshot)

Web data capture

Android data capture

Data Capture OUs

You can either assign the individual Org Units (normally the facilities and/or providers) that will be evaluated by the supervisor or you can select the parent OUs (like province, district), which will automatically make available all facilities/providers in that district/province

You should always assign the specific providers/facilities that the supervisor will manage. Assigning the parent district/province will not work

Analytic OUs

You can select a provide, district or even the country, depending of the level of access that you want your user to have for analytics only.

This setting only affects analytics on the web, not in android.

Assign User Groups (see above)

Not all of the authorities listed above are required, some are mainly used by the PCA features.

  • No labels