| Info |
|---|
DEFINITIONS: Authorities refers to User Groups refers to User refers to |
(authorities) and User Groups (sharing) and User Setup
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.
| Info |
|---|
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 |
|---|---|
|
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.
...
Metadata Object | Authority |
|---|---|
Dashboard (for H2 Metadata Generation) |
|
Data Element |
|
Legend Set |
|
Map (for H2 Metadata Generation) |
|
Option Set |
|
Program |
|
Program Indicator |
|
Program Rule |
|
Program Stage |
|
ProgramStageSection |
|
Visualization (For H2 Metadata Generation) |
|
Other authorities
App access authority is required to administer H2 programs in a DHIS2 server.
...
App |
|
Tracker |
|
Import/Export |
|
System |
|
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).
...
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.
...
Not all of the authorities listed above are required, some are mainly used by the PCA features.