DHIS version 2.33 is released

Dear all,

DHIS2 version 2.33 is out with many new features, apps, improvements and bug fixes!

(Log in with admin / district on the demo server. Right-click on the links to open in new tab)

ANALYTICS FEATURES


Multiple maps and timelines: In the maps application you can now render multiple maps in the same screen to show how the data has evolved over time. You can also have a single map which can “play” the changes to data on a timeline to show the change over time. This is useful e.g. to show how an outbreak is spreading over time, or how coverage of a service changes over time.

Demo | Screenshot 1 | 2 | 3 | Jira

Single value charts and dashboard items: You can now render a single aggregated value in data visualizer. This simple visualization displays a single value which can be saved and added to the dashboard. This allows for a dashboard item which provides essential information at a glance, such as the number of new cases of a disease or the number of facilities currently having a stock-out. |

Demo | Screenshot 1 | 2 | Jira

Patient line-listing with data from multiple stages in event reports: You can now create a list of patients or tracked entity instances based on enrollment that displays data across any number of stages in a single table. In the case of disease surveillance patients line listing, this would typically be demographic data (Patient/TEAs), initial clinical examination and diagnosis (stage 1), specimen tracking & lab results (stages 2x), case investigations (stages 3x), follow-up visit stages and final outcome stage, all in a single table.

Screenshot 1 | Jira

Improved date reporting in Event reports: Event reports now show enrollment dates and incident dates as well as event program stage dates. It can also show the description of these dates instead of just “Event date”. This can be configured in the program, e.g. as “Date of birth” or “Date of postnatal visit”.

Screenshot 1 | Jira 1 | 2

Google Earth Engine Layers: Several improvements have been made to the temperature and precipitation layers from Google Earth Engine. Previously it took a long time to load the weekly periods for multiple years. Two dropdowns have been added, one for year (default is the most recent) and one for week. For temperature layers, the data set has been updated to include the more recent time periods.

Screenshot | Jira 1 | 2

TRACKER AND EVENT FEATURES


Performance and stability improvements: This version offers significant performance and stability improvements, in particular in the area of transaction handling and queries optimization:

  • The system has been reviewed to minimize the number of expensive read-write transactions, which has an impact on overall performance and might lead to database deadlocks.

  • Tracker attribute uniqueness check performance has been optimized.

  • Tracker notifications are asynchronous to avoid blocking.

  • Tracked entity instance auditing is asynchronous to avoid blocking.

  • Removed expensive circular checks for tracked entity instances, enrollments and events.

  • Removed expensive loops checking access permission on data elements during import.

  • Database indexes reviewed to make sure the relevant indexes are used for data-intensive queries.

Working lists based on user assignment in tracker capture: It is now possible to build working lists based on user assignment of events. This functionality lists tracked entity instance and filtering criteria and makes it easier to view and follow up on events. Working lists can be incorporated into the user’s normal work processes, enabling planning, prioritization and focus on specific events and specific TEI.

Screenshot 1 | 2 | Docs | Jira

Working lists and user assignment in capture app: Similar to the working lists in tracker capture, single event programs can now be configured to allow user assignment of events and create working lists based on filtering criteria such as user, date, status, etc.

Demo | Screenshot 1 | 2 | Docs 1 | Docs 2 | Jira 1 | Jira 2

Listing of tracker programs in capture app: The capture app now lists tracker programs as well as single event programs in the program selector. Selecting a tracker program provides an information screen explaining that the program is handled in another app, and the user can click a deep link to open the tracker in the correct org unit and program. This feature lets users see all their programs, both tracker and event programs, in the same place.

Screenshot | Docs | Jira

Display of program ownership: The current ownership of all enrollments in the selected program is now displayed as “owned by” in the enrollment widget. The ownership is first assigned to the organisation unit that enrolled the TEI into the given program, and is transferred by referring a TEI using the “move permanently” option. Ownership can be different for a single TEI in different programs, for example one clinic can follow up a patient in HIV, while another clinic follows up the same patient in MCH.

A user that has capture access to the organisation unit that is the current owner of the TEI/Program will have write access to all enrollments for that TEI/Program combination. A user that has search access to the organisation unit that is the current owner will have access to search and find the TEI/Program combination.

Screenshot 1 | 2 | Docs | Jira

Deduplication flagging in tracker capture: When searching for tracked entity instances in tracker capture, it is now possible to flag the presence of possible duplicates in the results. When a duplicate is flagged, it acts as a reminder that the data needs to be cleaned up, and as information for anyone using the data in their daily work. The data is also available for future functionality for identifying and merging duplicates.

Screenshot | Docs | Jira

Bidirectional relationships: Bidirectional relationships can now be configured in tracker capture. A relationship represents a link between two entities in the tracker data model, and is considered data in DHIS2 based on a Relationship Type, similar to how a Tracked Entity Instance is based on a Tracked Entity Type. Relationships can now be defined as unidirectional or bidirectional, with bidirectional relationships creating an automatic relationship on both sides of the linked entities, such as a Mother and Child.

Screenshot | Docs | Jira

Updated icon library: The icon library has been updated to include 534 searchable icons, covering a wide variety of health, agriculture, transport and education-related topics.

Screenshot | Jira

Image resizing: It is now possible to resize/downgrade the images stored in the server when returned via the API, in order to reduce bandwidth consumption when downloading associated images to DEs, TE attributes or Options, and to minimize storage on the Android database. When requesting a data value of type image, the query can specify Small (256x256px); Medium (512x512px); Large (1024x1024px).

Docs | Jira

Program indicator and program rules health checks: Program indicators and rules are now evaluated during the integrity check in the Data Administration app, reviewing for invalid expressions and filters; missing actions or priority and more.

Screenshot | Docs | Jira

Z-score calculations in program rules: Standard functions for calculating Z scores “weight for height” and “height for age” are now available in program rules. Z score calculation for weight for age was present from 2.32. This is useful in settings where a clinician would otherwise be calculating Z-scores by hand. The d2 function calculates z-score based on data provided by WHO weight-for-height indicator. Its value varies between -3.5 to 3.5 depending upon the value of height.

Screenshot 1 | 2 | Docs | Jira 1 | 2

APPS FEATURES


Reports app: The new reports app is out of beta and comes with many new improvements. As an example, standard reports are now linkable and can be opened from a URL. The old reports module has been removed.

Demo 1 | 2 | Screenshot | Docs | Jira

Enrollment section forms: You can now create section-based forms for enrollments in tracker. The configuration can be done in the maintenance app under the “attributes” section > “Create registration form” in the tracker program configuration wizard. This allows for creation a section-based tracker enrollment form without creating custom HTML-based forms.

Demo | Screenshot | Docs | Jira

RELEASE INFO


Release Information Link
Download release and sample database https://www.dhis2.org/downloads
Documentation and Javadocs https://www.dhis2.org/documentation
Upgrade notes Upgrade notes for 2.33 on GitHub
Details about each feature on JIRA (requires login) https://jira.dhis2.org/issues/?filter=11153
Overview of bugs fixed in JIRA (requires login) https://jira.dhis2.org/issues/?filter=11159
Source code on Github https://github.com/dhis2
Demo instance https://play.dhis2.org/2.33.0/
DHIS 2 community https://community.dhis2.org/
11 Likes

Thanks Phil.

Looking forward to testing and using the new app. Especially on expressions on indicators.

4 Likes

Hi Philip and kudos to all wining team, and everyone who took DHIS2 to the next level. Just in a quick glance, so many useful features and functionalities.

Keep it up

4 Likes

Dear @phil and all of the team

This is absoultely fantastic. Thank you for these upgrades and new features - many of which I have asked about and have requested through this community and through JIRA. It is really great to see that the requests from the users really do get implemented.

We appreciate the hard work you all do to make our lives easier!

5 Likes

Much kudos to the development team! Long awaited feature of combining data from multiple stages I like this so much because it is gonna save us a lot of time that was spent on linking reports from different stages. :ok_hand:

4 Likes

Thanks dev team and the community for these amazing new features and improvements. Just a quick question …Where has the data approval functionality been moved to, as it is not available in the new reports app?

3 Likes

Comment from Public Health perspectives related to this release:
Great and Useful features in 2.33. the more investment and development on the TEI and multiple relation the more supporting for advancing the Universal Health Coverage Concept. Basically the Family Medicine approach which relying totally on the family members relationship. Really thank you for providing such useful feature which is help in improving the quality of health care services as a result of linking health and clinical data between family members. This is one of best use case to track the common shared risk factor for family member. Keep great Job :slight_smile:

3 Likes

Hi @banga,

The existing data approval functionality was problematic and we plan to release a new standalone data approvals app that is really fit-for-purpose. Unfortunately that app is not available at this time, so we are not able to support that functionality in version 2.33 yet.

Kind regards,
Phil

2 Likes

Thanks Phil. Looking forward to this.

1 Like

Hi Phil,

This is a bit tricky then if implementations already use the existing data approval functionality. Was it not possible to leave the existing as it is until the new one is available?

Regards

Elmarie Claasen

image001.png

Health Information Systems Program

2 Likes

Thanks for this excellent work! Looking forward to the new map functionality. I hope to see much more from DHIS2 in future releases in this direction, enabling precision public health…bringing the “where”.

Great work!

1 Like

Thank you for new map functionality. I hope this feature can add to dashboards. :+1:

1 Like

Hi @Elmarie_Claasen,

Unfortunately, it was not possible to keep the existing data approval component at the same time as making certain architectural improvements. It is our belief that this is not a heavily used feature, but those implementations relying on it should feel free to let us know and help us to gauge the priority for the new data approval app.

Kind regards,
Phil

1 Like

Hi @taufiqhs,

Yes, the new maps functionality is also available on dashboards! :wink:

1 Like

Hi Phil,

We will communicate with Oslo regarding our use of the data approval app as well as requirements.

Regards

Elmarie Claasen

image001.png

Health Information Systems Program

1 Like

Ouh okay.

Sorry, And thank you for importing apps

1 Like

Hello,

When will the DHIS2 Capture app be compatible with 2.33? I see that right now it only works with servers up to 2.32.

1 Like

Hi @berhard,
The Web Capture app is supported in 2.33. Do you face any issues with it?

Markus

1 Like

Hi @Markus Thanks for responding and confirmation. Yes, we are facing problems when we update the app and open. Couldn’t finish the configuration process and taking almost a week, and still didn’t open. Here below is how it looks like.

Thank you
Mastewal
Commun

1 Like

@Mastewal, can you try to clear app data on settings> Application Manager. Then try signing in again. Make sure you have stable internet connectivity. I saw you are using WiFi, if may also try using mobile data.

Thanks,

Herald

1 Like