HNQIS System Admin in DHIS2

The objective of this document is to give an overview of key topics for HNQIS configuration, support and troubleshooting in DHIS2 for HNQIS agents in the Helpdesk.

__________________________________________________________________________________

Checklist configuration process. 1

HNQIS configuration in DHIS2. 1

HNQIS Users. 4

HNQIS OUs 4

HNQIS servers 4

HNQIS demo log-in accounts 5

HNQIS app and language. 5

System Parameter Setting. 5

CSAs responsibilities. 6

Checklist configuration process

• Data Hub is the focal point for checklist development and changes. We use a standard template for the configuration, then send it over through the helpdesk where Data Hub team makes the configuration. Focal points for Data Hub team trained on how to configure HNQIS: James O, James A, Kelly D, Mphatso N, Gedeon S, 
• During the configuration, Data Hub team creates the HNQIS Programs in DHIS2, all the DEs associated to the Programs, activate OUs on the Programs, create the 2 HNQIS Admin and Basic User groups and set up a demo account
• After 3-4 weeks, Data Hub team comes back with the configuration and the demo account to test. Demo accounts are active for _Test OUs and their log-in credentials are usually like GHdemo, KEdemo, MWdemo, etc

HNQIS configuration in DHIS2

• HNQIS Health Area = DHIS2 Program
  • There are 7 standard Health Areas for HNQIS and all of them have their naming convention. Important to stick to them, especially for Fixed DEs and Fixed Indicators working well.
  • The standard requirement for all REACH implementing countries is to have them conduct supportive supervision in order to improve the quality of care that the providers at all levels of the health care system give.
  • Program attribute PRG Program Type must be HNQIS or the HNQIS app won’t recognize that Program as an HNQIS Program
• Answer options = Option set
  • 99% of HNQIS questions should have Yes1No0 as Answer options
  • The remaining questions are either YesNo, RealSimulated and other ad hoc options (ie. drop-down list, number, short text, date)
• Branching logic
  • HNQIS accommodates branching logic up to 4 levels from parents to grand-grand children
  • Parent question is reported in the DE attribute 38 Question Parents and the Answer option that opens a child question is the DE attribute 39 Question Parent Options
  • This is to indicate which parent question the question opens to and in case of which answer, whether Yes or No:
    • 38 Question parents: UID(s) of the parent(s) questions that expand the current question. In case of multiple parent questions, UIDs must be separated by the character “,”. ie. CUTLiAKPjBJ,rP8xzKKqH4W
    • 39 Parent Question Options: UID(s) of the option(s) from parent questions that expand the current question. In case of multiple options, they will be separated by character “,”. In case of multiple parents and multiple options, options from different parent will be separated by the character “;”. ie. kkOywHQwQWE;kkOywHQwQWE,yVUHqeMvBJZ
• Scores
  • HNQIS questions accommodate scores. The scores contribute to the Composite scores (section scores) and to the overall QA score
  • Scores in DHIS2 are reported as DE attributes 30 Num w. and 31 Den w. Usually, the Num and the Den are the same score and what goes in the final Num is the Answer option * Score, while what goes in the final Den is the correct Answer option * Score
  • The way the Composite scores and the overall QA score are calculated is the sum of all scores associated to each question multiplied by each Answer options. Example: a question has a score of 2 and its Answer option is Yes1No0:
    • In case of Yes answer, the score is 2 * 1 = 2
    • In case of No answer, the score is 2 * 0 = 0
  • The overall QA score does not take into account the different weights of each section, but it’s the sum of all scores from all questions multiplied by their Answer options
  • All scores are coded in the system as 0CS – zero Composite Scores
  • A section is composed of a certain number of questions which contribute to the Composite score of that section
  • The DE attribute 35 Compositive Score is what defines the Composite score meaning which Composite score that question will contribute to
  • Please, note that the Feedback in the app will pop up only if the question has the DE attribute 35 Compositive score filled in
• Feedback content
  • It can be text, video or image
  • For text, it is the DE attribute Description
  • For video or image, it is the DE attribute 36 Image URL and 37 Video URL: here is where you have the google drive document ID associated with the relevant multimedia content as per google Drive folder (link below). Multiple items can be referred, separated by “#” 
• Question order
  • DE attribute 21 Question Order reports the order of the question in its section. ie. question order 170 means that is question number 7 of the first section. In case there is a new question added by the team after this, you can have the question order as 171 – before the next question which has been configured originally as 180
• Critical steps
  • HNQIS reports critical steps with a red asterisk. Critical steps are mandatory DEs and they can be marked as mandatory from Program -> Assign DEs -> Compulsory
• Tabs
  • DHIS2 sections are tabs in the app
  • You can manage sections from Program -> Create data entry form -> Section
  • Each tab/section also has a Composite score
• Access
  • All HNQIS countries have 2 User groups: HNQIS Admin and HNQIS Basic. For the Programs and for all sections of a Program, they are given the following rights:
  • HNQIS Admin:
    • Metadata: can edit and view
    • Data: can capture and view
  • HNQIS Basic:
    • Metadata: can view only
    • Data: can capture and view
  • No public access
• OUs
  • All HNQIS Programs need to be active on the relevant OUs as per country request
• HNQIS Blueprint
  • There is a blueprint to download metadata from servers, make changes, troubleshoot and other things
  • Make your own copy of the file from File -> Make a copy: https://docs.google.com/spreadsheets/d/1IVztQ40hGP86QAizFWiTSFZyedJPeERWVaDet3MBTiE/edit?gid=796407659#gid=796407659
• Changes
  • Small changes can be made directly from DHIS2 UI. However, it’s super important to coordinate with HNQIS users about upcoming changes to existing DEs and ask them to:
    • Send all unsent surveys from the app to DHIS2 before making any change to the DEs (how to make sure all surveys have been sent from the app to DHIS2: ask the users to go to the Improve module and make sure there is no asterisk before any survey)
    • Refresh metadata once edits are made in DHIS2 (how to refresh metadata from the app: ask the users to click on the 3 vertical dots in the right upper corner of the app and select refresh metadata)
  • In case the change is the addition of a new DE, there is no need for HNQIS users to send unsent surveys. Just coordinate with them in order to refresh metadata once the addition of the DE is done

HNQIS Users

• For entering data with HNQIS, HNQIS users MUST have a DHIS2 account for HNQIS data entry, only! This is because if a user has access to other Programs which are not HNQIS Programs, the app won’t recognize them and it will crash
  • User roles:
    • [country] HNQIS User role (ie. KE HNQIS) and _User – Data Entry Tracker
    • _Analytics – Services (all modules) and _App – Browser cache cleaner in case you want them to access HNQIS data from the DHIS2 dashboard
    • _App HNQIS
  • User groups:
    • [country] – HNQIS Basic (ie. KE – HNQIS Basic)
  • OUs:
    • HNQIS users must be assigned to the OUs they want to enter data from
• User attribute 42 User Announcement is used to communicate with HNQIS users and it reports a script that pops up on the HNQIS app screen when users log in

HNQIS OUs

• All OUs which are active for HNQIS have their OU attribute OUProductivityValues filled in. The OU attribute OUProductivityValues reports a string of 9’s and 0’s as per the System Parameter Setting and indicates whether that OU is in High or Low Prd group for the position represented by each Health Area in the string
• In case of missing Prd values, by default, the OU is in the Low Prd group

HNQIS servers

• https://reachdatahub.org
• 
  
  • It is the main server for all HNQIS configurations
  • We also have country-specific servers :
    • otss-ghana.org
    • otss-malawi.org
    • otss-mali.org
    • otss-sierraleone.org
    • otss-

HNQIS demo log-in accounts

• The demo log-in accounts, regardless of the server, are usually as follows:
  • Username: [country ISO code]demo
  • Passw: [country in EN]demo
  • Example:
    •  (Username; Password): 
    • KEdemo; 

HNQIS app and language

• The current version of the HNQIS app is 1.7.X (2023) and it works with DHIS2 instances in 2.30 - 2.40
• Currently, the HNQIS app supports EN, FR, ES, PT, LA, KH and MY. This means that all prompts in the app will be translated into one of these languages as long as the users select the language from their Android device settings
• POEditor is the software we use for managing language and it’s up to the CSAs to translate all the prompts into their local language. In case a country wants prompts in their local language, liaise them with Ignacio Foche at nacho@eyeseetea.com to give them access to POEditor for HNQIS
• In case a country wants HNQIS retrieving in their local language, the DE attributes Form name, Tab Name, Header and Description are in their local language

Country System Administrators (CSA)s responsibilities

• Local CSAs are responsible for:
  • Setting up HNQIS users
  • Maintaining HNQIS Programs active to relevant OUs
• Reference doc: HNQIS System Admin Manual