With the release of DHIS2 v42, the Capture app becomes the default application for all tracker and event-based data entry. As the Tracker Capture app is no longer available from v42 and beyond, teams across the DHIS2 community are transitioning to Capture for individual data collection workflows.
While some users may already be familiar with the app, v42 introduces several important enhancements that significantly improve the user experience. From working lists and bulk operations to improved access control and localisation support, these changes are designed to make everyday tasks faster, more intuitive, and more reliable.
We have been preparing for this transition in advance and this post highlights the most relevant improvements made in the Capture app that arose from requirements brought up by users of DHIS2. This post focuses on how these changes affect data entry staff, programme managers, and implementers in their day-to-day work. Whether you’re beginning the transition or adapting to the latest version of Capture, this post aims to support a smoother, more informed shift.
Preparing for the Transition
The DHIS2 team has developed a comprehensive Transition Kit, along with demo videos and training materials, to support the move from Tracker Capture to Capture.
Please note that the complexity of the transition may vary based on how your instance is currently configured. Some teams may shift quickly, while others may require time to align programme structures, re-train users, or validate workflows.
New Functionalities and Enhancements in Capture app
Bulk Operations [View documentation]
Challenge:
Managing large volumes of data is tedious, with users needing to complete or delete records one by one, often relying on backend support.
Solution:
The Capture app now supports bulk operations for both tracker and event programs. This includes the ability to complete or delete multiple enrolments or events simultaneously. This is a major time-saver for teams managing high volumes of data.
This reduces repetitive manual actions for data entry users, and supports implementers in managing clean-up tasks without depending on custom scripts or API workarounds.
Working Lists [View documentation]
Challenge:
Frontline staff and programme managers often need to access the same types of records repeatedly (e.g. tracking defaulters, reviewing newly registered clients, or following up with scheduled visits). In Tracker Capture, doing this required manual filtering or API support.
Solution:
With the Capture app’s Working Lists, allowing users to save customised filters of TEIs or events directly on the front page line list.
For frontline health staff, this means quicker access to the records they work with most frequently. (e.g. seeing a list of all people scheduled for a particular vaccine during the week).
For programme managers, it simplifies monitoring specific cohorts (e.g. defaulters or new registrations) without relying on backend configurations.
[Note that working lists in the Capture app are different from the Line Listing app. While both present tabular views of data, the Line Listing app is primarily used for analytics, reviewing and reporting, whereas working lists are designed for action-oriented, day-to-day data entry and follow-up within the Capture app.]
Improved Access Control [View documentation]
Challenge:
Inaccurate permissions across users might lead to accidental deletions of TEIs.
Solution:
Capture app now allows for more granular permissions. For example, users may have access to view or edit a TEI or an enrolment but not delete them. These controls help uphold data integrity and align with organisational policies.
This gives programme managers and administrators more control over who can make changes to records, helping maintain data integrity.
Linked Events [View documentation]
Challenge:
Programmes often require follow-up visits, referrals to other facilities, or multiple stages of care. Previously, managing these connections required switching between forms.
Solution:
The Capture app introduces the Linked Event widget, allowing users to schedule, enter, or link to another event from within the same workflow.
- Programme staff can manage follow-ups and referrals without leaving the current record.
- Clear linkages between related stages help improve visibility and transparency in treatment.
Other Enhancements in v42: Small Changes, Big Difference
The v42 release includes many other interesting usability refinements that improve the overall experience for both new and experienced users of the Capture app:
1. Assigned User Filters in Working Lists
Working lists can now be filtered by “assigned user” at the program stage level, making task management and supervision easier for managers and facility leads.
Supervisors can more easily identify which staff are responsible for which records, allowing them to manage workloads and accountability.
2. View Org Unit in Working List Columns
The organisation unit tied to each event or enrolment can now be displayed directly in the table view.
This helps users working in multi-facility contexts clearly understand where data originates, improving situational awareness and reducing confusion.
3. Support for Non-Gregorian Calendars
The Capture app now supports calendar systems such as Ethiopian, Nepali, and Islamic, based on system settings.
This improves user confidence and alignment with national practices, especially in countries where non-Gregorian calendars are commonly used.
4. Breadcrumb Navigation on Event and Enrolment Pages
Breadcrumbs help users keep track of where they are in the workflow and allow them to move between pages more efficiently.
This gives all users better orientation in the system and makes it easier to navigate back during multi-step workflows.
5. Org Unit Contextualisation
The Capture app now allows users to hover over organisation units in working lists, widgets, and forms to view the full organisational hierarchy, providing additional context.
This helps users who work across multiple facilities or administrative levels to better understand the context of the data they are viewing or editing. This is especially helpful when organisational units have similar names, or when users have overlapping responsibilities across many org units.
6. Permanent Transfers
Tracked Entity Instances (TEIs) can be permanently transferred from one org unit to another directly from the enrollment widget. By selecting the “Transfer” option from the Enrolment widget’s dropdown menu, users can easily complete the action in a single step.
This feature supports implementers and frontline health staff who are responsible for mobility of patients across org units. It ensures that TEIs are accurately reassigned, without having to rely on backend changes, or data re-entry.
Reach out to us
If you have already transitioned or are planning to do so soon, we encourage you to share your experience or seek support via the community forum. If you’d like to reach out to us, leave a comment below, and we’ll get in touch with you directly!