Aller au contenu
For the complete DHIS2 documentation index, see llms.txt.

Architecture de l'application BNA

The BNA Application is built on architecture that eases the user interactions by having a design concept that promotes the user to follow their intuition complemented with high performance that considers the lowest internet connection scenarios with descriptive notification messages if the user misses a step along the way.

Concepts de design de l'application BNA

Faire plus en moins d'étapes

Most of the operations in the application can be achieved in three steps or less. The BNA App gives a district user or any user at any level with no administrative privilege the ability to perform operations without a need to switch between modules or drop ongoing activities. Users can bookmark interventions, filter interventions by organization unit or period and more with everything being just a click away.

Suivez votre intuition

The BNA App has been built from the ground app, to make functionalities more accessible, more intuitive and most importantly more capable. The App follows a minimalistic design that minimizes any chances of the user getting lost in the middle of performing their usual operations.

Mise en page de l'application BNA

The BNA App is flexible to adapt to any number of user journeys depending on the country's implementations. The primary two users are:

  1. Administrators: can manage interventions with operations such as creating interventions, applying data filters for interventions, making legend definitions and many more administrative operations.
  2. District users: analyzing the bottlenecks can switch through their interventions, bookmark their favorite interventions and perform root cause analysis through the root cause analysis widget.

Other bottleneck App users can be national, and regional/counties users who can only analyse bottlenecks, sub-nation analysis, route causes for each bottleneck and their solutions.

Menu global du DHIS2

To browse the BNA app, access the DHIS2 demo server with the login credentials provided on the page. Once logged in, search for Bottleneck Analysis App on the Search bar.

Accessing DHIS2 Global Menu while using BNA App in DHIS2

Search for Bottleneck Analysis application and click on it

Figure 2.3.-B: Searching for the Bottleneck Analysis App on apps list or by typing full or part of app name “Bottleneck Analysis App

Liste des interventions

Une fois l'application BNA chargée, les utilisateurs auront accès aux interventions disponibles et auront la possibilité de rechercher d'autres interventions qui ne figureront peut-être pas dans l'application au moment du chargement. L'accès aux interventions partagées est limité au niveau d'accès où elles sont partagées.

Illustration 2.4-A: Liste des interventions disponibles pour les utilisateurs connectés dans l'application BNA

Illustration 2.4-B: Graphique d'analyse des goulets d'étranglement pour l'intervention sélectionnée à partir de l'illustration 2.4-A

Filtres globaux des interventions

Right under the interventions list there are controls for the active interventions. The filter control when clicked expands to offer the user an ability to make data selections, period selections, organisation unit selections, and legend configurations. However, all users except administrators have access to Period Organisation unit filters only. More details on these operations can be found on chapter 4 section 4.

Contrôles du filtre global dans l'une des interventions sélectionnées dans l'application BNA

Éléments d'intervention

Toutes les interventions dans l'application BNA comportent trois éléments, à savoir :

  1. Le graphique d'analyse des goulets d'étranglement
  2. Le tableau d'analyse des sous-niveaux
  3. Le widget d'analyse des causes profondes

These intervention items will be empty when an intervention is created. The administrator is expected to configure the intervention items by making selections on the global filters. More details on how to configure interventions can be found on Chapter 4 Section 5. The district user is expected to enter data into the root cause analysis widget as explained in the next chapters.