Capture App now has all of the features of Tracker Capture, and more!
Line Listing App supports listing Tracked Entities that are enrolled in multiple programs
Android Capture App analytics now supports linelists that are updated while offline
More than 500 bugs fixed, thanks to the strong focus on maintenance and targeted bug-fixing activities for this release
In v41, a new login app built on React is introduced. This app provides customizable configuration options, allowing easy customization of the login experience to match your specific context.
Introducing the first preview of the completely new Maintenance App. In v41 we are releasing the data element sections with new modules continuously introduced as they are developed. The updated features include advanced filtering options, bulk sharing capabilities, and a sleeker user interface.
Dhis2 will support from this version support the selection of multiple options for datasets for both aggregated and individual multi-select data elements. They will also be available for analysis through indicators and program indicators.
DHIS2 2 now allows uploading custom icons, expanding beyond the built-in library, to allow for context-specific icons such as those used by the Ministry of Health or NGO, as well as expand the availability of icons for non-health-related areas. These icons are available across the web and Android, and are configured via Maintenance DHIS2 Web App.
We are adding more configuration options to the aggregate data entry form to allow you to customise the look and feel of the data entry form without building a custom HTML form. We have started with the option to pivot categories as rows and have data elements as columns or move a category to a row. You can now also add rich text fields before and after a section.
From v41, Capture and Tracker Capture are considered feature equal. This means that the software development team is not adding any further functionality to Tracker Capture, only fixing critical/security bugs if discovered. The Tracker Capture app and old tracker endpoint are now deprecated, and will not be bundled into v42.
Since the Capture app is on continuous release, you can also use this app from 2.38 and above. There are certain features that have needed new backend dependencies, but if those are not required for you, you can use the app management app and update the app to newer versions on 2.38 and above.
The features that need specific backend versions are the following:
There are also several features that are only available in the Capture app which we hope will encourage you to test it out. These include:
The relationships widget is updated for the Capture app with various improvements
When creating a tracked entity through a relationship, tracked entity attributes configured with “inherit” will be prefilled with values from the source tracked entity in order to reduce data entry burden and improve data quality
The Capture App now includes a growth chart widget for individual tracked entities, based on the WHO z-scores for:
You are now able to download working lists in the Capture app as JSON or CSV files
Individual tracked entities in working lists can now be marked for follow-up, and filtered to provide a list of all designated for follow-up
The referral widget has been updated and renamed the “Related Stages Widget” in the Capture app with additional functionality and improved user experience.
In order to support referall workflows and correct attribution of analytics, we have completed the ownership transfer of enrollments between org units. The ownership transfer overwrites the ownership field of an enrollment, while preserving the enrolling org unit and event org unit fields
One time referrals are now supported in the Capture app, allowing for a selected org unit to access an enrollment without overwriting the ownership field.
Image attributes can now be displayed in working lists, to easier enable identification of tracked entities for use cases such as patient identification; inventory management; lab equipment monitoring; etc.
Uploaded images can now be previewed in both the event page and profile widget
Various improvements to the changelog, including sorting and filtering in order to provide important information about when a value was created, changed or deleted and by which user.
As a part of the platform strategy to support greater customizability and external development, we have added extension points to the Capture App allowing DHIS2 application developers to inject custom plugins in the data entry form as well as the enrollment dashboard. For an example of this in action, see the new growth charts and documentation, which were built using these same extension points.
We have completed a full review of the /tracker API and made significant changes in order to harmonize names and parameters for consistency and ease of use. These improvements include some breaking changes that should be noted and addressed. See details in the v41 README, as well as the documentation.
You can now append &verbose=TRUE to the end of a query in order receive better information for debugging and testing program rules in the Capture app.
Android App now supports offline line listing analytics. Created in DHIS2 web app, configured in Android Settings Web App (ASWA). Displayable on home screen and event/tracker programs; searchable by period, Org. unit, or custom columns.
DHIS2 now allows customizing tracker terminology like “event” and “enrollment” for end users’ familiarity. Admins can configure it per program via the Maintenance App, and the Android Capture App reflects these custom terms.
The Android Capture app now provides clear and explicit error messages for configuration issues, enabling effective communication between users and administrators to promptly resolve empty screen problems caused by empty forms or lack of access.
Android App now notifies users when actions requiring internet connection are tapped without connectivity. Improves behavior of non-responsive parts like sync buttons when no connection is available.
Improved tracker program user flow with confirmation dialog for TEI deletion, redesigned scheduling event dialog, streamlined org. unit selection for single access pre-filled, and program rule “Hide program stage” alignment with Capture web.
Redesigned inputs for all value types in v2.10, improving data entry. Signature input and complete legend description enhance the experience. New fields have default settings, and admins have the option to opt-out via the Android Settings web app.
DHIS2 Android App now supports custom map layers configured in Maps Web App. These layers are downloaded and displayed alongside default ones, enhancing mapping capabilities.
Implementations are more and more demanding in terms of offline need of individual records. This version of the app has been reviewed to optimize performance when there are big numbers of TEIs downloaded locally.
TEI dashboard’s bottom part, displaying program stages, revamped for a cleaner look. Events list now offers more space, less non-critical info. Plus, create event button relocated to top (timeline view).
In this version, event/enrollment details like event date, org unit, coordinates, and category combinations are integrated within the form. They’re readily accessible as the first section, collapsed after filling for efficient data collection.
Search form improved for cleaner, intuitive experience. Buttons now explicit for search/creation. TEI search with barcodes streamlined: Unique result opens TEI Dashboard; multiple results show TEI list; no results prompt creation or external search.
Users can export an encrypted local database for troubleshooting, allowing admins to import the exact environment. This aids in diagnosing sync issues and ensuring data integrity. Access to the exported database requires credentials for security.
Vector files can not be imported into DHIS2 and displated in the maps app. This allows for much more flexibility in displaying geographic data from other sources in the maps app.
Replace the legacy push analytics service with more modern functionality which uses the same visualization engine as the web-based visualization apps. Allow dashboards to be rendered on the server and sent to a user’s email, respecting sharing settings.
Data Visualizer application now supports the “cumulative values” setting for pivot table visualization types in v41. Each cell in the table displays the sum of the value in that cell and all preceding values in the same row.
The Data Visualizer application in v41 introduces support for outlier tables as a visualization type. This enhanced functionality replaces and improves upon the legacy outlier tables that were previously available in the WHO Data Quality application.
The Line Listing app now supports the creation of line lists for tracked entities which allows for creating a list of tracked entities that are registed or enrolled in multiple programs. This includes the ability to add and filter on data from different programs that tracked entity is enrolled in and/or view attributes of tracked entities that are shared across programs.
In v41, the Job Scheduler app now allows configuration of grouping jobs to run in sequence or in parallel. This functionality, previously added in v40 via the API, can now be easily configured through the app interface.
Introducing a new simple scheduler based on the current database state, running asynchronously to execute task configurations. This eliminates issues with the previous “black box” approach, ensuring the job triggers as specified in the configuration.
The Data Exchange app has been updated to allow for creation and editing of the data exchanges directly within the app. Making it much easier to set up exchanges and transfer data or convert tracker data into the aggregate model.
The Integrity check app has been given an extensive update, allowing individual check runs, separating longer checks, and providing informative recommendations.
(experimental) Additional plugin types can now be bundled in DHIS2 web apps, allowing Capture App functionality to be easily extended. These widgets can be installed in the App Management App and can be configured for different programs in the Data Store.
(experimental) It is now possible to apply partial updates to keys in the Data Store and User Data Store. When applying a partial updates, items can be appended to array type keys. It is also possible to optionally specify a maximum size in the “roll” parameter which will discard items from the beginning of the array if its size exceeds the maximum after the new item has been appended. This is an experimental feature which may be updated in future DHIS2 releases.
(experimental) To work around issues with too-long DHIS2 API request URIs, causing HTTP 414 URI Too Long errors, it is now possible to create short-lived query aliases. A query alias is a shortened API path which is mapped to a specific longer path on the DHIS2 server. Query aliases can be deterministically created and then reused until they expire. This is an experimental feature which will be expanded, supported by the App Runtime, and leveraged in DHIS2 frontend apps such as the Data Visualizer in future releases.
(experimental) A global app shell can be optionally installed, which will be served independently of individual applications. The global shell will ensure consistent headerbar and command pallet as well as other common global functionality such as alerts, session management, and more. This is an optional and experimental feature which will be expanded in future releases.