GBS Share Point
Help Desk
GBS Share Point
Help Desk
GBS Share Point
GBS Share Point
Help Desk
Help Desk
Account recovery
PSI logo
Healthy Lives. Measurable Results.
We tackle the most pressing health problems,
so that people can lead healthier, happier,
more productive lives.

New for 2.25: General features

[2.23] Current user in menu: The “profile” link in the header has now been exchanged for the name of the logged in user. The profile section has been rewritten and has received the new and modern look.
[2.23] User setting fallback to system setting: User settings now fall back to equivalent system settings if not set. You can define system settings for all user settings, meaning you can define system wide default settings. As an example, you can enable system email notifications system-wide, and then allow individual users to disable it for their own account.
[2.23] Usage analytics: A new app called Usage Analytics is available and lets you visualize statistics on how people (end-users) are utilizing the analytical features of DHIS 2. This includes how many times people have loaded charts, pivots, dashboards; how many favorites of various kinds people have created and how many people are logging in versus total number of users. The system will capture and store daily snapshots of usage statistics automatically which can be visualized through this app.
[2.25] Predictors: A new data predictor feature allows you to generate data values based on an expression and several other parameters. This is useful for generating targets, thresholds and predicted data in the future.
[2.23-2.25] Maintenance App: A new maintenance app is available which includes organisation units, data elements, indicators, Data sets, metadata attributes, constants, option sets, tracked entity attributes, tracked entity attribute groups, relationship types and tracked entities. Note that you now need to use the Maintenance app instead of the old Data elements and Indicators and Organisation units and Data sets apps.
[2.23] Metadata attributes for constant and legend set: Constant and legend sets now have support for dynamic metadata attributes
New Value Types
[2.23] Capture coordinates: A new value type, coordinates has been introduced, allowing you to capture coordinates for attributes and data elements.
[2.25] Organisation unit value type: A new value type organisation unit has been introduced, allowing you to select organisation units for attributes and data elements in Event Capture and Tracker Capture apps. This means that you can associate multiple organisation units to an event which is useful e.g. to store place of infection in addition to place of treatment. Try it out with the Inpatient morbidity mortality program.
[2.25] Capture location of enrollment: You can now capture the coordinate / location of an enrollment. This allows you to know where an enrollment took place. The location map widget is based on OpenStreetMap. This can be enabled through the capture coordinates property in program maintenance.
[2.25] Flexible disaggregation: Data elements can now be disaggregated differently for each data set they are part of. Put differently, a data element can be linked to multiple category combinations. When assigning a data element to a data set, you can define which category combination to use. This is useful in order to reuse data elements, for instance when different provinces in a country employ different data disaggregation, or when the disaggregation change from year to year.
[2.25] Data value audit: The data value import process now generates data value audit records. This allows for proper auditing of data being ingested from bulk data imports.
[2.25] Soft data value delete: Data values are now “softly” deleted, meaning they are marked as deleted in the database rather than permanently removed. A new field deleted has been introduced for data values which is set to true for deleted values. Softly deleted data can optionally be included when requesting data through the API by setting the includeDeleted param to true. This allows clients, such as Android apps and third-party systems, to react when data has been deleted in DHIS 2.
[2.24] Metadata synchronization: Metadata synchronization enables DHIS 2 instances to synchronize metadata with each other. Given a central and multiple remote instances, metadata created at central can sync with the remote instances. The remote instances will check the central instance for new, available metadata packages/versions. This allows the implementor to roll out metadata updates in a controlled and staged manner.
[2.24] Improved program rules: There are two new types of actions for program rules. These allow consolidated errors and warnings when events is completed (in tracker capture) and saved/updated (in event capture). This is useful when there is a combination of things in the form that should trigger an error/warning, whereas each single data element might be legal in itself.
Also, program rules now have support for validating regular expression patterns through the function d2:validatePattern.
[2.23] Cross-event program rules: Program rules can now reference values from events other than the active event for single event without registration (event capture).
[2.24] System-generated identifiers: For unique tracked entity attributes you can now have the system automatically generate and assign numeric IDs. When registering tracked entity instances on web, the tracker capture registration form will automatically be populated with a number in the given pattern. In tracker on Android, the ID generation is used to reserve a series of IDs for each Android device. This allows offline registration of tracked entity.
[2.23] Include first stage of program in registration: Programs can now optionally choose to have the first stage of a program appear on the same page as registration.
[2.25] Reminders and notifications: A new notification solution allows for setting up reminders for upcoming events and notifications for missed events in tracker programs. Reminders can be sent before and after scheduled events, directly to people and DHIS2 users. Also, notifications can be sent on program enrollments and enrollment completion. Messages can be delivered by SMS, email and as DHIS2 messages.

Leave a Reply

Your email address will not be published. Required fields are marked *