DHIS version 2.26 is out with a lot of improvements and new features.
Log in with admin/district on the demo system.
Program indicators can now utilize a new aspect of the analytics engine for program enrollments. This implies that you can compare data values and dates from different stages and events within an enrollment. This allows for calculation of indicators such as “average inpatient bed days” and “hemoglobin improvement since first visit”.
Daily relative periods
You can now push data analysis in the form of reports, charts and maps to your users via email. This helps improve awareness and visibility of your data, and can encourage people to more actively look at analysis. Push analysis is based on dashboards, and can be set up, run and scheduled from the Maintenance app. You can also run this immediately and preview from the the context menu.
Data element event clustering in GIS
Using the event layer in the GIS app, you can now specify which data element or attribute to use as a basis for event analytics and clustering. The data item must be of value type coordinate. As an example, for a malaria case program, you can have data elements of type "coordinate" for place of infection and household location, and visualize those locations on the map for the malaria cases.
Pivot table cell background coloring
You can now specify whether to color the cell text or cell background of pivot tables based on legend sets. This is helpful if you're creating scorecards, for example, where high and low values can be easily identified. Go to Pivot table > Options > Legend display style.
Explicit open periods for data entry
You can now specify exactly which periods should be open for data entry per data set. You can also determine when those periods will be made available for data entry. This is useful when you need finer control over which periods should be possible to enter data for, and when you need to schedule these periods to open at precise times.
Validation notification templates
You can now specify templates for notifications which are to be sent for data validation violations. The templates gives you full control over the notification text and supports variables for injecting the org unit name, period, validation rule and current date.
Event data in validation rules
You can now use program data elements, tracked entity attributes and program indicators inside validation rules. Aggregated values will be utilized from the event analytics engine when the validation rules' expressions are evaluated. This allows for combining routine data and event data in the same validation rule. This is useful for comparing thresholds collected as routine data with disease cases reported as events, for example. Validation rule management is now available in the Maintenance app.
Age value type
Data elements and attributes support a new value type: “Age”. This renders as a widget in Event/Tracker Capture apps and means you have to enter the age in weeks, months or years. The selected input converts to a date of birth. This simplifies the input of age at points of care, for example.
System Administration Features
Analytics cache of old data
We've added a new system setting for the caching of analytics data, where data older than a specified number of years will be cached. You can avoid caching your latest data, while older data that never changes, can be cached.
Public/private analytics cache setting
There's a new system setting for controlling whether cached analytics data should be public or private, meaning whether proxies should be able to cache the content. This is useful for heightening the security of sensitive data while still allowing web browsers to cache content.
Approval in analytics threshold setting
We've added a system setting which defines for how many years back in time approval should be relevant. After the specified number of years, all data becomes available in analytics - even if unapproved. This means that data will automatically be approved and visible after a given number of years. This enables you to prune the approval table and ensure that system performance is not degrading.
Env variables in config
Environment variables are now supported in the dhis.conf configuration file. You can use this for example to externalize database connection information such as URLs, user and password, instead of storing this data directly in the config file. This is useful for server administration and for cloud environments.
User account lockout
The system now supports locking the user account for 15 minutes after five successive failed login attempts. This is useful to prevent brute-force authentication attacks.
Web API features
Analytics raw data
We've introduced a new resource for retrieving analytical data without aggregation at /api/analytics/rawData. This resource lets you retrieve raw data denormalized across any data dimension. This is useful when integrating third-party BI/analytics tools, as you will get data values with all data dimensions “flattened out” without any pre-aggregation, allowing the external tool to perform the aggregation and filtering.
Pre-aggregation measures in analytics
The analytics API lets you specify measure criteria to be applied before data aggregation takes place. This allows for better filtering of data before aggregating.
Prune data element
Data elements with corresponding data and audit values can be pruned using the /api/maintenance/dataPruning resource.
You can download Live package, WAR file, sample data and source code here:
You can find documentation and Javadocs here:
You can read the Upgrade Notes and find the upgrade script here:
You can find the source code on Github here:
You can access the demo application here:
You can find details about each feature on JIRA here: