Programas¶

Event and Tracker common features¶

Navigation Bar¶

Use the bottom navigation bar to move from one screen to another.

Event Dashboard¶

While entering information of the event, the bottom navigation bar allows the user to choose among:

1. Details
2. Entrada de dados
3. Analytics (when available)
4. Notas

TEI Dashboard¶

While in the TEI dashboard the bottom navigation bar allows the user to choose among:

1. Details
2. Analytics (when available)
3. Relacionamentos
4. Notas

Event listing for event and tracker programs¶

The bottom navigation bar also allows switching the visualization mode if the event program or the tracker program have been defined with coordinates. More information about the map view can be found on the specific section below.

1. Exibição de lista
2. Map view

Data Entry Flow¶

creating/editing an event¶

When creating an event or an enrollment, there are a number of fields that are not data elements or attributes, for example, event date, org unit, coordinates, enrollment date, category combinations.

Those elements are referred to as event/enrollment details and in previous versions they were displayed in different screens separated from the data elements or attributes. From 3.0, the details are displayed inside the form, as the first opened section for completion. Once they are filled in, for example when the user reopens the event or enrollment form, the details section will be visible and easily available, but collapsed to leave more space for the data collection.

Complete/Re-open event¶

When adding an event to an event program or inside a tracker program the user should fill the information and scroll down to make the save icon appear at the bottom right corner.

After tapping on the 'save' button, if the form does not contain any errors, warnings or empty mandatory fields, the app will ask if the user wants to complete the form. Two options are given to the user:

1. 'Not now': The app saves the form and go back to the event listing screen (or TEI dashboard for tracker programs). The status of the event will remain open.
2. 'Complete': The app saves the form and go back to the event listing. The status of the event changes to completed.

Note

To verify if an event is completed look at the icon, it must be a green checked box.

Note

If the event is non-editable, the app will hide the 'save' button

To re-open an event, the app now displays a "Re-open form" button in the Details screen. This button will be available only if the user has the correct authority (‘Uncomplete events’) to reopen a completed event.

Discard changes¶

Tapping the back arrow in an enrollment or event form now provide two options:

1. 'Discard changes', which allows the user to restored the fields to their previous values or,
2. 'Review' to remain in the form and update the fields.

If the user is in a new enrollment or event, the options allow the user to:

1. 'Discard changes': The enrollment or event is not created or,
2. 'Keep editing': Allowing the user to finish the enrollment or event.

From 3.1.0 Discard changes will not only apply to new events but also when edit them.

Field completion percentage¶

A porcentagem de dados concluídos em cada evento é mostrada no canto superior direito de um evento quando ele é aberto após o primeiro registro.

Note

The display of the percentage can be set up to be displayed or not using the #capture_app_android_settings_webapp_appearance_program

Sections Navigation¶

The sections can be collapsed for a simpler user experience. Sections in enrollment forms are also supported and are aligned with the design of the event sections.

Error messages¶

The app will list the name of the mandatory fields missing when the user tries to complete an event or enrollment. The sections containing the missing fields will be highlighted to help the user find the missing fields.

After tapping on the 'save' button, the app will display two options:

1. 'Not now': Allowing the user to save the form with an 'open' status or,
2. 'Review': The app will remain in the form for the user to fill the empty mandatory fields.

The errors and warnings are also shown as an indicator next to the section name including the number of errors for each section. A list of the fields with the errors/warnings when the user tries to save the form will be displayed.

After tapping on the 'save' button, the app will display two options:

Warnings

1. 'Not now': Allowing the user to save the form with an 'open' status or,
2. 'Complete': The form is saved and its status changes to 'complete'

Errorrs

1. 'Not now': Allowing the user to save the form with an 'open' status or,
2. 'Review': The app will remain in the form for the user to review the fields with errors

If there is a combinantion of errors, warnings and missing mandatory fields, the app will display the 'Not now' and 'Review' options only.

Event Notes¶

É possível adicionar notas a eventos em programas de evento único e eventos de estágio de programa. As notas estão disponíveis em uma nova guia no formulário de entrada de dados.

Maps¶

Map Layers¶

When displaying maps there are different layers that can be displayed by clicking on the specific button on the uppper right corner. The user can select one or more layers to be displayed. Both coordinate and polygons types will be displayed. The layers are depenandat on the type of program as explained below:

• Mostrar eventos (para programas sem registro)
• Visualização de satélite
• Coordenadas TEI (por padrão em programas com registro)
• Coordenadas de inscrição (somente para programas com inscrição)
• Coordenadas do estágio do programa (somente para programas com registro)
• Relacionamentos (apenas para programas com registro)
• Mapa de calor (apenas para programas com registro)
• Tracked Entity Attributes (Coordinates Value Type - Only for programs with registration)
• Data Elements (Coordinates Value Type)

From 3.0 custom map layers are also supported by the Android App. These custom layers, configured in the maintenance app, will be downloaded and displayed as additional layers to the default ones.

Map Carousel¶

On the map view of the program, a carousel of cards is displayed, one for each enrolled TEI (Tracker programs) or Event (Event programs).

• Os cartões TEI no carrossel seguem o mesmo design da exibição de lista TEI.
• Ao rolar horizontalmente o carrossel, o mapa aumenta o zoom nas coordenadas selecionadas. Se o campo de coordenadas estiver vazio, uma mensagem será exibida.

Each card displays Tracked Entity Attributes (for Tracker Programs) and Data Elements (for Event programs) configured as 'Display in list'.

Current Location displayed in maps¶

If the user has granted location permissions to the App, the map will show the current location represented as a blue color dot. The maps in the DHIS2 Android Capture App include the possibility to center the map on the user location.

Navigation to Specific Location¶

If the TEI or event has coordinates a navigation icon will be displayed at the top right of the card. Click to open the location in the default maps app configured in the device.

Maps Accuracy¶

From 3.1.0, the capture coordinates process now includes a feature that displays the precision of the captured location. This allows users to see how accurate their location data is in real-time.

The user will see the tags according to the following ranges:

1. Low: >= 100m
2. Medium: < 100m to 25m
3. Good: < 25m to 6m
4. Very good: < 6m

The coordinate can be captured even if the accuracy is low, but this behavior can change if there is a restriction/limit on the precision (configured in Android Settings WebApp). When there is a restriction, the “Done” button will remain disabled until the precision meets the required threshold.

Maps Search¶

A new search functionality has been added, allowing users to look up specific locations by name or address. Once the user tap on the search bar, the keyboard will open and the user can enter any street or location name. The user can select any of the locations of the list or tap on the "select in map" to display all the locations in the map (blue pins).

When a place is selected, the location will be displayed as a card below the map, the pin will be positioned on the selected place and the search bar will be filled up with the place name.

The list of pins is based/limited on the current location. But once the search is done, if the user moves to a different area, the search can be done within the new area by tapping on the "search on this area" button.

Maps Manual Capture¶

By dragging the map the user can choose the pin location manually. At the bottom of the map, the label "selected location" will be displayed with the respective coordinates.

In 3.1 the manual capture can be disabled (Android settings webApp configuration).This will hid the search bar and won't allow the user to select any location on the map. It will be restricted to save the current location only.

Working Lists¶

Working lists are available in Event and Tracker Programs, once a list is selected the filters will be blocked and not allowed to change until the user resets the search.

The Android App supports the new tracker working lists, allowing users to filter by data elements. The working lists need to be configured in web using the web Capture App. The Android app will download the working lists that are configured and saved on the server side.

In 2.9, the working lists have been moved from the filters section to the main program screen. In earlier versions the user had to open the filters to be able to see and select a working list, from this version the working lists are always visible under the search bar facilitating its selection for filtering out Tracked Entity Instances

Synchronization based on working lists¶

From version 3.3.0, the Android Capture App supports synchronization based on working lists defined in the Capture web app and assigned through the Android Settings Web App (ASWA). Working lists allow administrators to specify exactly which tracked entity instances (TEIs) or events should be downloaded to a device, ensuring focused, context specific data for each group of users.

When working list based sync is enabled for a program:

• If a user has access to only one assigned working list, the Android app will synchronize only the data contained in that list.
• If a user has access to multiple working lists for the same program, the app will automatically merge all assigned lists into a single dataset during synchronization.
• If no working list is assigned or shared with the user, standard program-level synchronization rules apply.

This feature helps deployments reduce sync time, limit unnecessary downloads, and ensure that each user receives only the data relevant to their workflows.

Configuration note:

Working list assignments and synchronization rules are configured in the Android Settings Web App (ASWA). For instructions on how to assign working lists, manage sharing, and control synchronization behavior, see the Synchronization settings section of the ASWA documentation.

Indicadores de programa¶

The analytics tab supports displaying text and key/value pair in feedback or indicator section.

Legends¶

Legends can be assigned to Data Elements and they will be displayed next to value with the respective color and label.

Feedback rendering (New in 3.4)¶

Feedback messages generated through Display Text and Display Key Value Pair program rule actions support Markdown formatting. This allows structured and more readable content to be displayed directly in the app, including headings, lists, tables, links, and emphasized text.

In addition, legend-based styling enables feedback values to be visually highlighted using predefined legend sets. When numeric values are present in the content, they are evaluated against the configured legend ranges and rendered with the corresponding color. This allows dynamic color coding of key values, helping users quickly interpret results and identify important conditions.

Supported Markdown formatting¶

The following Markdown elements are supported in feedback content:

• Paragraphs: plain text separated using \n\n
• Headings: # to ######
• Bold text: **bold text**
• Italic text: *italic text*
• Unordered lists: prefix items with -
• Ordered lists: prefix items with numbers (1., 2., etc.)
• Links: [text](https://example.com)
• Images: ![alt text](https://example.com/image.jpg) (public URLs only)
• Tables: defined using pipe (|) notation

Spacing and line breaks

Spacing within feedback content must be explicitly defined using line break characters.

• Use \n\n to create a new paragraph or visual separation between sections.
• Single line breaks may not be preserved consistently.
• Proper spacing is required for Markdown elements such as tables and lists to render correctly.

Example

The following example demonstrates how Markdown can be used within program rule actions to render structured feedback content, including formatted text and tables.

Action 1: Display text
Static text: ## Weight per visit
Expression:
d2:concatenate(
"\n\nFacility: ", V{orgunit_code},
"\n\nDate of birth: ", V{incident_date}
)

Action 2: Display text
Static text: ## Summary
Expression:
d2:concatenate(
"\n\n|Visit|Weight|\n|---|---|\n|Birth|", #{weightbirth},
"|\n|Second visit|", #{weight2}, "|"
)

Notes

• Table columns are rendered with equal width
• Tables can be scrolled horizontally if they exceed screen size
• All text is left-aligned by default
• Markdown support is limited to the elements listed above

Data Entry Form¶

Hint messages¶

The input fields will display had a hint message saying "Insert value here" which will remain until a value is entered by the user.

Navigation button¶

In forms with multiple sections, the App includes a "Next" button at the end of each section which calls the user to action. The funtion of the button is to close the current section and open the new one.

Program Stage section description¶

To provide more context and information at the moment of data collection the description has now been brought to the user interface and will be displayed below the section name. The description will always be visible but if the text is too long (more than 3 lines) the app will add an ellipsis and a show more/less button to expand or collapse.

Enable/disable collapsible sections in forms¶

Stage sections in the Android App are displayed with collapsible menus that enable the user to open one section at a time. The purpose of this accordion-like implemementation is to help the user navigate very long forms, however some implementations would prefer to list the sections one after the other.

This new version of the application enables the admin use to decide if the sections should appear in extended mode. This configuration is made through the Android Settings Web App and will display the sections one after the other with the name the secion acting as a separator. In extended mode, the "next" button at the end of each section is removed.

New inputs per value types¶

The inputs for all value types have been redesigned. Tappable areas and texts have been increased and selection modes are improved to offer cleaner and more intuitive user experience. By default the Android App will display the current forms. Admin users are able to opt-in to use the new forms through the Android Settings WebApp.

Actionable Icons¶

This feature enables users to take action on phone numbers and email addresses directly from the app. When tapping on the icons, the app will dial a phone number or open an email app copying the address from the event or enrollment data entry form.

Customized Tracker Terminology¶

In order to facilitate the terminology used in DHIS2, it has been decided to gradually enable the possibility to customize certain terms to each particular use case. In 3.0, the terms "event" (used in a program stage context) and "enrollment" are customizable.

To customize the terms, the admin can go to the Maintenance and when creating or editing the program add a text to:

1. "Custom label for enrollment" in the Enrollment details section OR
2. "Custom label for event" in the stage details section

In 3.1, the term "event" (program context) is now customizable.

Relationships¶

The relationship tab displays sections once the tab is open. Each section represents a different relationship type and the + icon will be available only if the user has capture access to the relationship type.

The name of the section will be the "relationship name seen from the initiating or receiving entity" depending on the configuration of the relationship.

In 3.1.0, the relationship cards have also been updated with a new design to offer a more intuitive and visually appealing experience. The new design emphasizes clarity and usability, making it easier to view and manage relationships at a glance.

Delete a relationship¶

To delete a card, long press on it and select one or more. Then, tap on the remove icon to display the dialog. Finish the process by tapping on the "Remove" button.

To prevent accidental deletions and enhance user control, a new confirmation dialog also has been added when deleting a relationship. This dialog will prompt users to confirm their action, ensuring that relationships are only deleted intentionally.

Custom Intents¶

This feature is available from Android Capture App version 3.3.0.

Custom Intents is a powerful feature that allows the DHIS2 Android Capture App to integrate with third-party Android applications. By configuring custom intents, administrators can enable the Android app to launch external applications, send data to them, and receive data back to populate fields automatically.

This feature enables seamless integration with specialized apps such as: - Barcode and QR code scanners - GPS and mapping applications - Biometric identification systems - Custom data collection tools - Camera applications - Medical device applications - Any other Android application that supports intent-based communication

Custom Intents are configured using the Android Settings Web App and can be linked to Tracked Entity Attributes or Data Elements.

Note

1. Custom Intents leverage the Android Intent system, which is a fundamental component of Android's inter-app communication mechanism. Understanding basic Android Intent concepts can be helpful when configuring this feature.

2. When a custom intent is configured for a tracked entity attribute or data element, the field will only accept data from the configured third-party application. Manual data entry will not be available for that field.

Data Entry Flow¶

1. User navigates to the form containing the configured field
2. User taps the custom intent button/icon next in the field
3. The third-party application launches with the configured request parameters
4. User completes the action in the third-party app (e.g., scans a barcode, captures location)
5. The third-party app returns the result to DHIS2
6. The configured response value is automatically populated in the field
7. User can review the value before saving

Note

When the Extra Type is List of JSON Objects, the returned values will be concatenated into a single string separated by commas (e.g., 120,118,122). This allows storing multiple values from the list in a single field.

Search Flow¶

When configured for the SEARCH screen:

1. User navigates to the search screen for tracked entities
2. User taps the custom intent button for the search field
3. The third-party application launches
4. The returned value is used as a search parameter
5. Search results are displayed based on the captured value

Note

When the Extra Type is List of JSON Objects, the search will match tracked entity instances that contain any of the values in the returned list. This allows searching for multiple entities at once.

For configuration steps, see the Custom Intents section of the Android Settings Web App documentation.

Event Programs specific features¶

Event - TEI relationships¶

The app allows adding relationships from single events (in event programs) to TEIs. There is a new tab in the event screen, named relationships, that will be displayed only when this type of relationships are configured in the server for the specific program.

Note

The current version does not allow TEIs to event relationships, or using events that belong to an enrollment.

Cards design¶

The new design of cards offers a cleaner and more intuitive layout replacing the use of coloured icons by explicit text when relevant.

Main changes¶

Sync button: It now appears as a button at the bottom of the card and it is only displayed if there are unsynced data or an error or warning after a sync.

Event status: After an event program is completed, the app will add a label in each card to specify the status.

Tracker Programs (program with registration) specific features¶

Relationships in maps¶

In tracker programs, the user can see relationships on a map by tapping the map icon on the relationships tab.

• Uma seta é mostrada na direção do relacionamento.
• Para relacionamentos bidirecionais, a seta aponta para os dois lados.
• Cada tipo de relacionamento exibe uma cor diferente.
• Se um ou ambos os TEIs tiverem um polígono como coordenada, a linha vai de (e para) o ponto mais próximo no polígono de ambos os TEIs.

TEI Dashboard¶

The TEI Dashboard has been redesigned for both portrait and landscape view. The new design offers a cleaner and more intuitive layout replacing the use of coloured icons by explicit text when relevant and moving some secondar actions to the hidden menus.

Dashboard card¶

Main changes in 2.9:

Edit registration form: In previous versions, there was a button "Open TET details" at the bottom of the TEI dashboard card. Now, the button is located at the top bar of the screen with the label "Edit TET" (For example: Edit Patient)

Follow-up: In previous versions, there was an icon at the top right corner of the card to mark the TEI. Now, to mark for follow up, the user needs to tap the three dot menu and select the "Mark for follow-up" option.

Card title In previous versions, the title included the values of the first 3 tracked entity attributes marked as Display in List. Now, the tile of the card can bdisplay the first Tracked Entity Attribute marked as Display in list OR a customize text, called TEI header, using program indicators and the Android Settings web App.

More information here on how to configure the TEI header.

Tracked Entity Attributes: From 2.9, the complete list of tracked entity attributes marked as Display in List will be display in the dashboard card. The first three will always be visible and if there are more, a show "more" button will appear to expand the list.

Programs: From 2.9, if the TEI is enrolled to more than one program, a list of the programs will be display and will also allow the user to tap on the label and navigate to full list of enrollments.

Program stages¶

Main changes in 3.0:

Event list: fresh and more clean look of the list of events, with more space and less -not critical- information displayed.

Timeline view: the button for creating new events has been moved to the top.

Navigation panel¶

To simplify and personalize the user experience, the user interface actions offered to the user at the TEI dashboard will be tailored to the specific configuration of each program.

• Relationships tab will not be visible if the program relationships are not configured
• "Create event" button will be hidden when the user cannot create more events based on tracker configuration.
• The Indicator tab will not be visible if the program has no program indicators configured.
• Organisation Unit filter will not be visible if the user has only one Organisation Unit configured.

Creating A Stage¶

To create a new event, the user needs to tap on the plus icon on the stage card. This icon is always visible unless the stage is non-repeatable and already created.

When the user taps on the button, that program stage will unfold showing to the user all the already existing events of that particular program stage

If the user is creating a new stage and there is only one option based on the program configuration, the available program stage is selected automatically and program stage selection step is skipped.

Share a TEI¶

The "Share" button has been removed from the TEI dashboard and the functionality to share a TEI through QR code has been relocated on the three vertical dot menu, at the top right corner of the screen.

Design de cartão TEI¶

The TEI Card has been designed to display as much information as possible considering the constrains of screen size.

From 2.9 the card has been redesigned to offer a cleaner and more intuitive layout replacing the use of coloured icons by explicit text when relevant.

The main changes are:

Card title The tile of the card can be composed by the first Tracked Entity Attribute marked as Display in list or a customize text, called TEI header, using program indicators and the Android Settings web App. More information here on how to configure the TEI header.

Sync button: It now appears as a button at the bottom of the card and it is only displayed if there are unsynced data or an error or warning after a sync.

Enrollment status: After a program is completed or cancelled, the app will add a label in each card to specify the status.

Overdue events: Is now displayed as a red label with the text: "Overdue" + date of the event

Follow-up: After a TEI is marked for follow-up, an orange label with the text "Marked for follow-up" is added to the card

Concluir / Desativar Inscrição¶

To complete or deactivate an enrollment, click on three dot menu in the uppper right corner and select "Complete" or "Deactivate".

Search Flow¶

Configurable TEI Search¶

Searching TEIs before creating is not mandatory now. Using the Android Settings App (v2.2.0) it is possible to configure the mandatoriness of the TEI search before creating an enrollment. Follow the steps below to enable the creation of TEIs without searching:

1. Open the Appearance menu in the Android Settings App
2. In 'Program' add a Program Setting
3. Select a tracker program
4. Tick the "Allow the user to create a TEI without searching" checkbox
5. Salve

If the feature is enabled, the Android App will display a "create new" button after opening a program and a search won't be required. If the feature is not enabled or the user is in a previous version of the app, a search must be performed to avoid possible duplicates. Once the search is performed the search button will become "Add" button for the user to create a new enrollment.

Search by unique QR/bar Codes¶

In 3.0, the search form has been improved to provide a cleaner look and a more intuitive user experience. The buttons have been made more explicit for differencing search from creation. In addition the flow for searching TEIs using attributes rendered as bar / QR codes has been made more agile. If there is only one result and the attribute is unique, the app will open the TEI Dashboard directly. If there are multiple results, the app will display all the cards on the TEI list (this is equal to the current workflow), and if there are no results, the app will display the create button and allow the user to “search outside the program” if the configuration allows it.

Aimed at aligning it with the web instance for a more consistent user experience, 3.1.0, by default, sorts the unique attributes (QR, barcode) at the top of the list of searchable attributes. Users can quickly and easily find the attributes for a more exact search.

The sort of the attributes will follow:

• At the top: QR/barcode attributes (unique)
• QR/barcode attributes (not unique)
• Other Attributes (unique)
• Configured order or default order (if not configured)

Offline and Online Search¶

To improve the response time in the search results, the Android App now searches offline first and displays the results while making an online search as a second step, transparent to the user.

Searching outside the program is offered as a second step when the attributes used in the search contain at least one Tracked Entity Type (TET) attribute

Redefinir campos de pesquisa¶

The search fields are used to look up for a specific entity, and the circled arrow to reset the search. All fields will be blank for the user to do a new search.

Tela de pesquisa para todos os tipos de entidades rastreadas¶

User can search across all programs by specific tracked entity type (TET). In the Search screen there is a drop down which shows all the programs available for the active TET (active TET is defined by the selection of the program in the home screen). That drop down should also have an option with TET name, for example: All Person.

Quando o utilizador seleciona essa opção, os campos de pesquisa disponíveis serão apenas os atributos TET (sem atributos específicos do programa). As restrições de pesquisa não se aplicam, porque pertencem aos programas.

A pesquisa retornará os TEI's encontrados no banco de dados local e também aqueles na OU Pesquisa do utilizador (quando o utilizador estiver online). Para aqueles encontrados online, o utilizador terá que selecioná-los e todo o registro será baixado.

** Nota **

Ao configurar search org. unidades, certifique-se de que sua organização de captura. unidades estão contidas em sua organização de pesquisa. unidades, para fazer essa captura org. unidades devem ser selecionadas, bem como a organização de pesquisa. unidades.

Painel TEI em programas¶

O utilizador pode ver o painel TEI sem qualquer programa, selecionando o TEI na lista se a pesquisa foi sem programa.

Os painéis mostrarão a lista de inscrições ativas.

Histórico de inscrições TEI e novas inscrições¶

User can see the complete historical records of the TEI. Clicking on the upper right corner menu, select "Program Enrollments". A list of "Active enrollments" will be displayed, followed by a list of "Past enrollments" (completed or cancelled), followed by the programs in which the TEI could be enrolled. User can also return to the "TEI Dashboard" without any program' by selecting "All enrollments".

Excluir TEI's e inscrições¶

To delete a TEI or an enrollment, select the desired option in the three dots menu of TEI dashboard. Local TEI or Enrollment will be deleted from the database. Records that has been previously synced with the server will be marked for deletion if the user has the following authorities:

• F_ENROLLMENT_CASCADE_DELETE
• F_TEI_CASCADE_DELETE

In this case they will be shown in the TEI search list, but will not be accessible.

From 3.0, there is a confirmation message to reduce errors when tapping on the delete button.

Warning

When users enter a TEI and while it is not synced to the server they will be able to delete the TEI and the enrollment even if they have not been asigned these authorities. This is by design and to allow users rolling back in case of having entered wrong data (TEI and/or enrollment) and thus preventing it reaching the server and requiring another user with higher privileges to fix the issue.

Visão de grupo das fases do programa no painel TEI¶

The TEI Dashboard offers the possibility to change the list of events from the chronological view to a stage grouping view. The stage grouping view will group and collapse the events per program stage. Each program stage group can be expanded by the user and the events will be displayed chronologically.

Herdar valores¶

Ao criar um novo TEI para um relacionamento, herde qualquer atributo do programa marcado com a verificação de herança na web.

Isso significa que quaisquer atributos existentes no primeiro TEI devem passar para o novo TEI e ser mostrados no formulário de registro.

Quebrando o vidro¶

The "breaking the glass" feature is now supported in DHIS2 Android Capture App. If the program is configured with an access level of "Protected" and a search is done outside the user scope, a dialog requesting a reason for access will be displayed for the user to temporarily override the ownership privilege of the proram. This means, the user will gain access to the program related data.

After the reason is written, the app will download the TEI and the dashboard will open. If the TEI being downloaded doesn't have an enrollment in the current program, an enrollment date and organisation unit will be asked.

Analytic charts¶

It is possible to display the evolution in data elements as charts, values or tables. These data elements must be a numeric value type and configured in a repeatable stage.

1. Single value: It will display the newest value in the program.

1. Charts: It is possible to display the values as a line chart o as a bar chart.

The Nutrition Growth charts are shown according to the WHO standards. This option will render a background image and apply the axis (0 to 5 monthly)according to the WHO model.

1. Tables: It will display the data elements or indicators in the rows and the periods in the columns.

Referrals¶

when a user makes a permanent referral of a TEI, the ownership will be updated accordingly on the server.

From 2.9, admin users can now enable or disable the referrals in the DHIS2 Android Capture App through the Android Settings WebApp.

When users add events (tapping on the + icon) in a tracker program, the DHIS2 Android Capture App offers three options: Add (for new events), Schedule (for planning future events) and Refer (for referrals or transfers). IF the referral option is not needed, then the admin user can remove the option from the menu to simplify the user experience. The removal can be general (for all the programs) or for specific programs.

Transfers¶

Significant enhancements to the transfer flow, aimed at making the process more user-friendly and transparent. The transfer button has been moved to a more accessible location within the three dot menu in the TEI Dashboard, ensuring that users can easily find and initiate transfers without unnecessary navigation.

Also, the ownership organisation unit has been added as a parameter in the TEI card. If the ownership org unit and enrollment org unit are the same, then the enrollment one will be hidden.

Once the transfer process has started, the user will see a dialog with all the org units available (search scope), once an org unit is selected, the transfer button will be activated. After tapping on the button, the ownership org unit will change to the new one. The user must sync data to reflect the changes in the instance.

[EXPERIMENTAL] TEI Header¶

The TEI Header is a title that can be added to the TEI cards and dashboards in the app. The title helps identify a TEI by displaying a summary of key information. It is formed by a concatenation of Tracked Entity Atributes and fixed text. The title is configured through a Program Indicator in the maintenance app and its assigned to the tracker program in the Android settings webapp. This feature is experimentan and depending on feedback and adoption it will be refined and incorporated in the Web Capture app.

Attention

In the Maintenace app, text expressions aren't valid. Even though the error is display in the dialog, save the program indicator and assign it in the Android Settings Web App, the DHIS2 Android capture app will read the expression accordingly.

For more information on how to configure the TEI header, click here.

Scheduling¶

Schedule after completion¶

In 3.0, the schedule dialog after completion has been redisigned to facilitate the creation of the event.

Schedule events dialog¶

As a continuation of the new schedule dialog introduced in the version 3.0, a new intuitive and user-friendly schedule dialog has been implemented to enhance the overall user experience, making it easier to book, reschedule, or cancel events.

Once an event has been scheduled, when the user taps on it, the app will display a dialog with the following:

1. Due date field: Allows the user to open the calendar by tapping on the icon or change the date manually. This will facilitate the process of re-scheduling an event.
2. Enter event button: after tapping on this button, the app will open the event with the current date and the user can start filling the form.
3. Cancel event button: after tapping on this button, the app will close the event and mark it as "skipped". As before, the user can always enter the event, add a report date, changing the status from skipped to open.

Dashboard quick actions¶

The Quick Actions bar is a new feature in the DHIS2 Android Capture App that enables users to access frequently used actions directly from the Tracked Entity Instance (TEI) Dashboard. These actions are displayed as customizable chips, streamlining workflows and reducing the number of taps needed to perform routine tasks.

Each action is displayed as a chip in the TEI Dashboard. By default, all chips are unselected, and the Quick Actions bar is not displayed in the app. When tapped, the chip performs a predefined function. The available actions include:

1. Mark for follow-up
2. Transfer
3. Complete
4. Cancel
5. More enrollments

The chips cannot be reordered. The order of appearance is as the list above.

Limitations and considerations¶

• Quick Actions are available only when configured via Android Settings WebApp (v2.4.2)
• Each program must be configured individually.
• Feature parity is maintained: actions remain available in the TEI Dashboard 3-dot menu even when Quick Actions are disabled.

Visão geral dos recursos com suporte¶

The following is a comprehensive list of all features available for Programs with and without registration in DHIS2, and notes on whether or not these have been implemented in the Android Capture app.

Nas notas, 'administrador' se refere a alguém que desenvolve e configura um sistema DHIS2, e 'utilizador' se refere a alguém que usa aplicativos para capturar dados, atualizá-los e revisar relatórios.

lenda	Descrição
	Recurso implementado
	Feature not implemented (will be ignored)
	Não aplicável
	Trabalho em progresso. Recurso ainda não totalmente implementado ou com comportamento inesperado já relatado.

Programa¶

Característica	Descrição do recurso	Programa com registro	Programa sem registro	Notas sobre implementação
Método de entrada de dados para conjuntos de opções	Permite que um administrador escolha como as opções serão exibidas na tela em todo o programa (ou seja, como listas suspensas ou como botões de opção)			Isso será substituído pelas novas opções de renderização.
Combination of categories (Attribute CatCombo)	Permite que um administrador anexe uma categoria (conjunto de opções) ao programa, exigindo que os utilizadores categorizem cada inscrição. (Isso é chamado de Combinação de Categoria de Atributo no DHIS 2.)
Fluxo de trabalho de aprovação de dados	If an admin selects a pre-configured Data Approval Workflow, this will be used to enforce an "approval" or "acceptance and approval" cascade, enabling users to sign-off and lock data.
Exibir lista de primeira página	If this option is ticked, the landing page displays a list of active enrolments once an Org Unit and Program have been chosen. (Attributes shown are those ticked as "display in list".)
A primeira etapa aparece na página de registro	Quando esta opção é escolhida, durante a inscrição no Programa, a tela do primeiro Estágio do Programa também é mostrada (a inscrição e o primeiro evento são capturados juntos em uma tela).			No Android, isso é implementado abrindo automaticamente o evento após a inscrição ser concluída, em vez de adicionar o formulário à mesma tela.
Dias de expiração de eventos concluídos	Permite que os administradores bloqueiem a entrada de dados um certo número de dias após a conclusão de um evento.
Tipo de período de expiração + dias de expiração	Permite que os administradores definam um período (por exemplo, semanalmente, mensalmente) e bloqueiem a entrada de dados um certo número de dias após o final do período.
Permitir futuras datas de inscrição	Se marcado, permite que o utilizador insira datas de inscrição futuras durante a inscrição em um programa; caso contrário, os utilizadores ficam restritos às datas atuais ou anteriores.
Permitir datas de incidentes futuros	Se marcado, permite que um utilizador insira datas futuras de incidentes durante a inscrição em um Programa; caso contrário, os utilizadores ficam restritos às datas atuais ou anteriores.
Inscreva-se apenas uma vez (por tempo de vida da instância de entidade rastreada)	Se marcado, evita que um TEI (por exemplo, pessoa) seja inscrito neste Programa mais de uma vez.
Mostrar data do incidente	Se marcado, as datas de registro e incidente são mostradas ao utilizador para captura de dados; caso contrário, apenas a data de inscrição é mostrada / capturada.
Descrição da data do incidente	Permite que um administrador personalize o rótulo que é usado para a data do incidente.
Descrição da data de inscrição	Permite que um administrador personalize o rótulo que é usado para a data de inscrição.
Coordenadas de captura (inscrição)	Permite que os utilizadores capturem coordenadas geográficas durante a inscrição no programa.
Polígono de captura (inscrição)	Permite que os utilizadores capturem locais (áreas fechadas) durante a inscrição no programa.
Coordenadas TEI	Permite que os utilizadores capturem coordenadas geográficas para o TEI durante a inscrição no programa.
Relacionamentos: criar e atualizar	Permite que os utilizadores criem e atualizem relacionamentos.
Relacionamentos - link de atalho para adicionar um parente	Isso permite que os administradores adicionem um link para um relacionamento específico ao Dashboard, permitindo que os utilizadores criem diretamente um TEI vinculado (por exemplo, paciente "criança").
Atributos: exibir na lista	Esta configuração determina se um Atributo pode ser visualizado em listas, como resultados de pesquisa, e se pode ser visualizado na lista de atributos mostrada em "Perfil" no Painel.			Os primeiros três atributos serão mostrados
Atributos: obrigatórios	This enables an admin to mark an Attribute as "mandatory";, meaning the enrolment can"t be saved until a value is captured.
Atributos: data no futuro	Para atributos de data, isso permite que um administrador evite ou permita que datas futuras sejam capturadas.
Formulário de registro - padrão	O formulário de entrada de dados padrão simplesmente lista todos os atributos definidos para o TEI.
Formulário de registro - personalizado	Isso permite que um administrador defina um layout personalizado (usando HTML) para o formulário de registro.	-		Layouts personalizados não são compatíveis com o aplicativo Android
Notificações de programa	Você pode configurar notificações automatizadas para quando as inscrições ou conclusões do programa ocorrem, ou em um intervalo definido antes / depois do incidente ou das datas de inscrição. Eles podem ser enviados como mensagens DHIS 2 internas, e-mails ou SMSs.			Esta funcionalidade é executada no lado do servidor, uma vez que os dados são recebidos. Não funcionará quando o aplicativo estiver funcionando offline.
Ativar / desativar inscrição	Desativar um painel TEI fará com que o TEI se torne “read-only”. Isso significa que você não pode inserir dados, inscrever o TEI ou editar o perfil TEI.
Completo permitido apenas se a validação passar	Marque a caixa de seleção para garantir que um evento criado por este programa seja concluído apenas quando todas as regras de validação forem aprovadas.
Datas de abertura / fechamento da unidade organizacional	Permite que um administrador defina datas de abertura e fechamento para uma unidade organizacional, o que impede que os utilizadores adicionem ou editem eventos fora dessas datas.
Níveis de compartilhamento de dados / Pode capturar dados	Permite ao utilizador adicionar novo evento, editar dados e deletar eventos no programa.
Níveis de compartilhamento de dados / Pode visualizar dados	Permite que o utilizador veja a lista de eventos dentro do programa.
Níveis de compartilhamento de dados / sem acesso	O utilizador não será capaz de ver o programa

Estágio do programa¶

Característica	Descrição do recurso	Programa com registro	Programa sem registro	Notas sobre implementação
Formulário do evento - padrão	O formulário de entrada de dados padrão simplesmente lista todos os atributos pertencentes a um registro de programa
Formulário de evento - formulários de seção	Os formulários de seção permitem que você divida os formulários existentes em segmentos
Formulário de evento - personalizado	Defina um formulário de evento personalizado como uma página HTML.			Layouts personalizados não são suportados no aplicativo Android.
Notificações de estágio do programa	Você pode configurar notificações automatizadas para quando o estágio do programa for concluído ou em um intervalo definido antes / depois das datas de eventos programados. Eles podem ser enviados como mensagens DHIS 2 internas, e-mails ou mensagens SMS.			Esta funcionalidade é executada no lado do servidor, uma vez que os dados são recebidos. Não funcionará quando o aplicativo estiver funcionando offline.
Repetivel	Se Repetível estiver marcado, este estágio pode ser repetido durante uma inscrição no programa. Se não for, o estágio só pode acontecer uma vez durante a inscrição no programa.
Repetivel	Se Repetível estiver marcado, este estágio pode ser repetido durante uma inscrição no programa. Se não for, o estágio só pode acontecer uma vez durante a inscrição no programa.
Dias de intervalo repetível + padrão	O sistema irá sugerir a data de vencimento como o cálculo do último evento + datas de intervalo padrão.
Tipo de período	Permite que um administrador configure um conjunto de períodos (por exemplo, semanas ou meses) para cada evento no estágio do programa, em vez de apenas uma data. Ao criar eventos, os utilizadores são solicitados a escolher um período (em vez de uma data) para cada novo evento que eles criam naquele estágio do programa.
Gerar evento automaticamente	Se marcado, uma "reserva" é gerada para esta Etapa do Programa no momento da inscrição, com base nos "Dias agendados desde o início".
Gerar eventos com base na data de inscrição (não na data de incidente)	Verifique nele as datas de vencimento de geração automática de eventos das fases do programa deste programa com base na data de inscrição. Se não estiver marcada, as datas de vencimento são geradas com base na data do incidente.
Abra o formulário de entrada de dados após a inscrição + data do relatório para usar	If selected, once an enrolment is complete, an event's data entry form should open directly afterwards.
Peça ao utilizador para concluir o programa quando o estágio estiver concluído	Se selecionado, ao concluir o estágio do programa, o utilizador deve ser solicitado a concluir o programa. (Esta configuração será ignorada se "Pedir ao utilizador para criar um novo evento" também estiver marcada.)
Peça ao utilizador para criar um novo evento quando o estágio for concluído	Se selecionado, quando o estágio do programa for concluído, o utilizador será solicitado a reservar.
Ocultar data de entrega	Mostra apenas a data real para eventos, ocultando a data de vencimento.
Coordenadas de captura (evento) / Ponto-tipo de característica	Enables the user to capture geographical coordinates when each event is created particularly useful in devices that have GPS (eg Android), as instead of having to type in coordinates, the user can automatically populate them with the press of a button.
Capturar polígono (evento) / Tipo de recurso-polígono	Permite que os utilizadores capturem locais (áreas fechadas) quando cada evento é criado. Um polígono deve conter pelo menos 4 pontos.
Descrição da data do relatório	Allows an admin to customize the label that is used for the event's date.
Elementos de dados - obrigatórios	Isso permite que um administrador marque um elemento de dados como "obrigatório", o que significa que um evento não pode ser salvo até que um valor seja capturado.
Elementos de dados - permitir fornecido em outro lugar	No formulário, isso coloca uma caixa de seleção ao lado do elemento de dados selecionado e permite que os dados anteriores sejam puxados para o elemento de dados.
Elementos de dados - exibição em relatórios	Exibe o valor deste elemento de dados no evento único sem função de entrada de dados de registro.
Data de elementos de dados no futuro	Para elementos de dados de data, isso permite que um administrador evite ou permita que datas futuras sejam capturadas.
Elementos de dados - opções de renderização como rádio	Permite que um administrador escolha como as opções serão exibidas na tela para cada elemento de dados (ou seja, como lista suspensa ou como botões de opção).
Bloco de formulário de entrada após preenchido	Impede todas as edições de eventos após sua conclusão.
Comentários do evento	Permite ao utilizador adicionar comentários gerais a um evento. Esses comentários são cumulativos (novos comentários são adicionados abaixo dos comentários existentes).

Programa com registro: painel de entidade rastreada¶

Característica	Descrição do recurso	Status	Notas sobre implementação
Mensagens	Permite que os utilizadores enviem mensagens ad-hoc de texto livre para TEIs (por exemplo, pacientes) via SMS ou e-mail.
Marque para acompanhamento (botão com triângulo de exclamação)	Permite que um utilizador marque um TEI (por exemplo, paciente) como requerendo acompanhamento.
Exibir histórico de auditoria TEI	Permite que um utilizador veja um histórico de todas as edições de atributos para este TEI (por exemplo, paciente).	-
Indicadores de programa inline	Se a caixa de um indicador de programa "exibir em formulário" estiver marcada, o indicador aparecerá no painel Captura do Rastreador e será atualizado ao vivo conforme ocorre a captura de dados.
Apagar eventos	Permite que o utilizador exclua um evento.
Agendar eventos	Na caixa de diálogo de geração de eventos, o utilizador também deve ver a opção de agendar um evento. O processo é como criar um evento, mas o utilizador será enviado de volta ao painel do TEI após o evento ser agendado.
Encaminhamento de pacientes	Na caixa de diálogo de geração de eventos, o utilizador também deve ver a opção de encaminhar um paciente. O processo é como criar / agendar um evento, mas o utilizador pode alterar a unidade organizacional e deve especificar se é uma referência única ou permanente. Uma vez, apenas criará o evento na UO especificada.
Redefinir campos de pesquisa	O utilizador pode limpar os campos de pesquisa pressionando o ícone de seta arredondada no canto superior direito da tela de pesquisa.
Tela de pesquisa para todos os tipos de TE	O utilizador pode pesquisar em todos os programas de um tipo de entidade rastreada (TET). Na tela de pesquisa há um menu suspenso que mostra todos os programas disponíveis para o TET ativo (o TET ativo é definido pela seleção do programa na tela inicial). Essa lista suspensa também deve ter uma opção com o nome TET. (Pessoa em nosso servidor). Quando o utilizador seleciona essa opção, os campos de pesquisa disponíveis serão apenas os atributos TET (sem atributos específicos do programa). Todas as restrições de pesquisa não se aplicam, porque pertencem aos programas.
Painel TEI sem programa	O utilizador pode ver o painel TEI sem qualquer programa, selecionando o TEI na lista se a pesquisa foi sem programa. Os painéis mostrarão os atributos TET no cartão de detalhes seguido por uma lista de inscrições ativas.
Histórico de inscrições TEI e novas inscrições	O utilizador pode ver o registro histórico completo do TEI. Ao clicar no ícone do canto superior direito, eles verão uma lista de inscrições ativas, seguida por uma lista de inscrições anteriores (concluídas ou canceladas), seguida pelos programas nos quais o TEI poderia ser inscrito. Os utilizadores devem ser capazes de navegar para as diferentes inscrições da lista.
Nível de acesso - quebrando o vidro	Se o programa estiver configurado com nível de acesso protegido e o utilizador pesquisar e encontrar instâncias de entidades rastreadas pertencentes à unidade organizacional para a qual o utilizador não possui autoridade de captura de dados, o utilizador terá a opção de quebrar o vidro. O utilizador descobrirá um motivo para quebrar o vidro e, em seguida, obterá a propriedade temporária da instância da entidade rastreada.

Programa sem inscrição: Programa de evento único¶

Característica	Descrição do recurso	Status	Notas sobre implementação
Lista de eventos (grade)	Uma lista de eventos existentes que é exibida quando um programa é selecionado.
Classificar e filtrar eventos na grade	Permite ao utilizador classificar os eventos listados ou filtrar os eventos com base em palavras-chave ou intervalos específicos de datas / números.		Os eventos são classificados cronologicamente. O utilizador pode filtrar por período e unidade organizacional.
Editar eventos na grade	Permite ao utilizador editar diretamente os elementos de dados mostrados na lista / grade de eventos.
Ver o histórico de auditoria do evento	Enables the user to see a history of all changes to the event's data elements.
Mostrar / ocultar colunas (na lista / grade de eventos)	Permite que o utilizador modifique os elementos de dados mostrados na lista / grade de eventos (aplica-se apenas a esse utilizador).
Porcentagem de conclusão de campo	A porcentagem de dados concluídos em cada evento é mostrada no canto superior direito de um evento quando ele é aberto após o primeiro registro. As percentagens devem ser adaptadas aos efeitos das regras do programa nos formulários.		A porcentagem de conclusão não leva em consideração os tipos de valor não suportados nos formulários.
Apagar eventos	Permite que o utilizador exclua um evento.