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

Setting Up a User

DEFINITIONS:

A User Is a Quality Supervisor or Supervisor, the perosn who completes an Assessment at a facility/provider location in the feild.

Please note Quality Supervisor/Supervisor operate at the Sub-National Level in the Org Unit and are normally assigned between 20-50 facilities/providers.

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 does not require 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.

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)

Please note that not all of the authorities listed above are always required, some are mainly used by the PCA features.


Assign User Roles

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.


(screenshot) set the name, last name, phone, blah, blah, password


  • No labels