DHIS2 version 2.35 is out with many new features, apps, improvements and bug fixes. On this page you can find information on this software version, including feature descriptions, links to technical documentation, and more
Discover some highlights of new features in this DHIS2 release with our Feature Spotlight video series.
You can now easily print a dashboard, either with a single item per page or in the preset dashboard layout. This enables you to create a dashboard as a standard printed report for routine meetings or plannings. You can also save a dashboard as a PDF to be shared via email or messaging.
[ Video ][ Screenshot 1 | 2 ][ Jira ]
You can now create a line and bar combination chart. For example this is useful for showing a cumulative case count as bars and an infection rate as a line over time on the same chart.
[ Video ][ Screenshot 1 | 2 ]
Data items can now be grouped by multiple categories. For example you can group a bar chart of health facilities by facility type or ownership.
[ Video ][ Screenshot 1 | 2 ]
Many new color sets can now be applied to charts. These include light, dark, color-blind, grey scale, and patterns. This allows you to make more customized and printer friendly charts.
[ Screenshot 1 | 2 ]
You can now edit the style, color, and size of all text in the data visualizer app. This enables you to have larger or more interesting text for charts that are downloaded.
[ Video ][ Screenshot ]
Chart axis management is improved, with a new user interface and up to four axis supported. For each data item you can select which axis to assign as well as the visualization type to use in a single screen.
[ Screenshot 1 | 2 | 3 ]
A new menu is available for selecting the type of visualization, which offers nicer icons and a description of the visualization type, making it easier to select an appropriate way to explore your data.
[ Screenshot 1 ][ Jira ]
This allows you to make a thematic map that represents each org unit as a single point/bubble. The size and the color of the bubble proportional to the value of that org unit compared to the range or legend. This is a popular way to visualize COVID-19 and other disease maps where hotspots need to be easily identifiable.
[ Video ][ Screenshot 1 | 2 ]
The new data table for event layers allows you to search and filter events. The filtering is happening as you type and provides a quick way to look for cases and patterns.
[ Video ][ Screenshot 1 | 2 ]
Several improvements to the TEI layer are available.
[ Screenshot 1 ]
The Maps app is now able to allow users to define a color in a legend for those org units that do not have data. This makes it much more apparent which org units did not report any data.
[ Screenshot 1 ]
A new “event status” option in the Maps allows you to only show events that are active, completed, scheduled, overdue or skipped.
[ Screenshot 1 ]
The analytics engine now supports comparing various time periods relative to the aggregation periods within indicator expressions. This allows you to compare data in previous (or future) periods, which is useful for calculating trends, stock consumption, performance against targets and much more.
[ Docs ]
Program rule expressions will be validated as the user types it in. This will help the user avoid spelling errors and other preventable mistakes, as well as saving the user time when configuring program rules.
[ Screenshot 1 ][ Jira]
The capture app date picker is now improved, allowing direct year selection. This will make selection of dates far in the past quicker and easier. One example of this benefit is a user entering birth dates – being able to quickly select the birth year.
[ Screenshot 1 ]
It is now possible to write program rules that evaluate and react to the completed date of an event. This is done with the variable called V{completed_date}.This can be useful when scheduling messages to be sent at a certain number of days after a patient visit was completed.
[ Screenshot 1 ][ Jira][ Docs ]
The service for reading and writing tracker data is rewritten to improve performance. Reading and writing tracker data is now around 3 x faster, and can handle more than 100 concurrent users/requests. This will have a significant positive impact on overall server performance for tracker and event-focused DHIS2 installations.
It is no longer necessary to assign the “View user” authority to end users in order to use tracker and messaging apps. I.e. in Tracker capture, program stage user assignment and data elements of type username no longer requires any special authority.
In previous versions it was necessary to clean the cache with the cache cleaner to pick up certain changes to metadata. This is no longer necessary. When the version number is increased in the maintenance app, the Capture app will detect this and download the program and all dependencies, as well as all relevant independent metadata objects like constants and org unit groups.
Going forward, several core DHIS2 apps will be released monthly. You can now install such core apps directly from the App Hub, and have the new version override the bundled version in DHIS2. This can now be done from the App management app. This is beneficial as you can start using new features more quickly, and upgrade to receive bug fixes without having to test the entire system.
A new SMS configuration app is introduced, which provides a modern and more user-friendly user interface and additional options for configuring SMS in DHIS2. This app will replace the existing Mobile configuration module, which will be removed in 2.36.
[ Screenshot 1 | 2 | 3 ]
This app is completely rewritten, and provides a better user interface and increased stability.
[ Screenshot 1 | 2 ]
Basic support for the OpenID Connect (OIDC) authentication layer is introduced. So far Google is supported as a provider, while several additional providers will be added in the upcoming releases. OIC can support Single Sign-On solutions, where DHIS2 can utilize an existing directory of user accounts.
[ Docs ]
The changelog (aka. audit log) for aggregate data and tracker data which is persisted in the database can now be disabled in dhis.conf. This is helpful for instances where audit is not necessary or relevant, as it will reduce the size of the database and improve performance of data import.
[ Jira ][ Docs ]
The DHIS2 icon library has been reviewed. Some icons have been modified to be more neutral when it comes to race and gender representations. Also some domains like Education and COVID-19 have been added following the requests from the community.
[ Screenshot ]
A new user lookup API is available. This provides essential user information like ID, username and name, without exposing other sensitive properties. The endpoint is open for all authenticated users. The main user API is now protected with the “View user” authority.
[ Docs ]
The metadata and users endpoints are now protected with the “View User” authority. The API field filtering is now restricted for user information, allowing only basic user information to be exposed. This provides better privacy and protection of user information.
This version of the DHIS2 core software is fully compatible with the DHIS2 Android Capture App version 2.3.
Click on the links in the table below for more information about this software release and to access an interactive demo.
| To find more details about... | Follow this link: |
|---|---|
| Download release and sample database | Downloads |
| Documentation and Javadocs | Documentation |
| Upgrade notes | Upgrade notes for 2.35 on Github |
| Details about each feature on JIRA (requires login) | Details on JIRA |
| Overview of issues on JIRA (requires login) | Overview on JIRA |
| Source code on Github | DHIS2 source code |
| Demo instance | Demos |
| DHIS2 community | DHIS2 Community of Practice |
