Introduction

Using the metadata published by JSI/ Momentum (Data Elements and corresponding Category Combinations), PSI created data sets at country, district and facility level, based on internal reporting frequency. For presentation purposes, PSI decided to customise the layouts, as well as to include a custom functionality to hide sections not applicable to each specific country. The custom datasets just use standard HTML, CSS and Javascript.

Data Set structure

The MPHD implementation at PSI uses 6 data sets, divided in tabs which are related to the health areas that the data elements belong to. Additionally, each tab has 'areas' that are used to group data elements that are part of the same indicators. An example can be seen on the screenshot below.

The space surrounded by the black square is DHIS section, rendered as tabs. The space surrounded by the grey square is the 'form area'

List of MPHD datasets

Features

To improve the overall usability of these data sets only relevant tabs and areas are shown to each country user.

Hide/Show

As not all data elements that are part of these data sets are required to be submitted by every country, custom code to only show the relevant indicators was developed. This hide and show feature utilizes a script included in the custom HTML form, plus a set of 'fake' category options and categories to store information about in what countries a given tab/ indicator (area) should be shown.

Hide / show - How it works

Custom tags are included on the custom form to define the different 'indicator areas'. This 'indicator areas' are also defined as 'fake categories' and we use DHIS2's OU assignment to activate those area on a per country basis. The custom script in each form reads this 'fake category' and based on the stored information areas are shown/ hidden. Further details is available on this Hide & Show article.

Translations

DHIS2 allows user to set up translations for data element and category options, however, when a data set is custom, it is not possible to display such translations automatically. Furthermore, the data model provided will result in a repetitive use of long Data Element names. To workaround this, we link an option sets (and their options) to each of the data sets to store and manage translations. A custom script reads from it and display the content accordingly.

Translations - How it works

By inserting 'term' labels in the custom dataset which are related to the option codes, we use a custom script to source the translation that we keep for each option. In the following set of images, you can see like a given option has been translated in DHIS2, and then that value is used when rendering the custom form in French.

Open

Image above shows the option utilized for "MPHD - FP.RH.7 Number of facilities where MOMENTUM supported introduction/re-introduction of new FP methods" which reflects in the option set "MPHD - District Quarterly (Terms)"

This term translation to French is done via the option set build-in ability to assign translations.

Which is then used for the final rendering when the system/database language is set to French

Download

Please find below all the links that you will need to include custom data sets, hide/show and translation features to your configuration.