You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/overview/ecosystem.md
+64Lines changed: 64 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,3 +4,67 @@ sidebar_position: 2
4
4
---
5
5
6
6
# Ecosystem overview
7
+
8
+
## How the Data Use Apps Work Together
9
+
10
+
The Data Use Apps are designed not as standalone tools, but as an integrated data-to-action ecosystem. Each app plays a unique role in the decision making cycle, creating a continuous loop from performance monitoring to action follow up. Together, they enable programs to move from identifying problems to implementing and tracking solutions within a single, unified workflow.
11
+
12
+
## The Data Use Apps Workflow
13
+
At the core of the ecosystem is a four-step process:
- Track Implementation & Accountability (Standalone or Linked AT)
18
+
19
+
This workflow ensures that data is not only analyzed but systematically used to improve services.
20
+
21
+
## How the Four Apps Connect
22
+
Below is the flow of interaction among the data use apps:
23
+
24
+
### Scorecard → BNA
25
+
Users begin by reviewing performance indicators in the Scorecard App.
26
+
If an indicator performs poorly (e.g., marked red or yellow), they can launch a Bottleneck Analysis to investigate further.
27
+
#### Purpose:
28
+
- Identify what is underperforming
29
+
- Move to understanding why it’s underperforming
30
+
31
+
### BNA → Root Cause Analysis
32
+
33
+
Within the BNA App, users evaluate performance through the Tanahashi model to identify the specific stage (availability, accessibility, acceptability, contact, quality) where the bottleneck exists.
34
+
From there, users perform root cause analysis (e.g., using the 5 Whys).
35
+
#### Outcome:
36
+
A list of bottlenecks and root causes that require action.
37
+
38
+
### BNA → Linked Action Tracker
39
+
Once bottlenecks and root causes are identified, users can seamlessly send them to the Linked Action Tracker.
40
+
#### Purpose:
41
+
- Create action plans
42
+
- Assign responsibilities
43
+
- Set timelines
44
+
- Link actions directly to BNA findings
45
+
46
+
This ensures transparent follow up on the exact gaps identified through analysis.
47
+
48
+
### Action Tracker (Standalone or Linked) → Implementation & Monitoring
49
+
Teams use the Action Tracker to:
50
+
- Track progress of planned activities
51
+
- Update status (in progress, completed, delayed)
52
+
- Document evidence
53
+
- Communicate responsibilities
54
+
55
+
The Action Tracker creates organizational accountability and closes the loop between data insights and real-world actions.
56
+
57
+
### Feedback Loop to Scorecard
58
+
As actions are implemented and data is updated in DHIS2:
59
+
- Improved performance becomes visible again in the Scorecard App
60
+
- Managers can verify whether actions had the expected impact
61
+
- If gaps persist, the cycle continues
62
+
63
+
This supports a continuous quality improvement cycle.
64
+
65
+
## Why the Ecosystem Matters
66
+
- Ensures end to end data use, not just analysis
67
+
- Creates a structured method to identify and fix performance gaps
Copy file name to clipboardExpand all lines: docs/overview/implementation.md
+132Lines changed: 132 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,3 +4,135 @@ sidebar_position: 3
4
4
---
5
5
6
6
# Implementation Framework
7
+
The implementation of the Data Use Apps requires a combination of technical setup, stakeholder engagement, and governance alignment. This section provides a high level guide to help countries, programs, and implementing partners adopt and operationalize the full Data Use Apps ecosystem successfully.
8
+
9
+
## Prerequisites
10
+
Before deploying the Data Use Apps, ensure the following technical and organizational prerequisites are in place:
11
+
12
+
### DHIS2 Platform Requirements
13
+
- DHIS2 version 2.39 or higher (recommended: latest stable version)
14
+
- Proper configuration of:
15
+
- Data elements and indicators
16
+
- Data sets or program indicators
17
+
- Organizational hierarchy
18
+
- User roles and sharing settings
19
+
- Functional analytics and data approvals where applicable
20
+
21
+
### Data Availability & Quality
22
+
The apps rely on timely and accurate data. Implementers should confirm:
23
+
- Routine data reporting is consistent
24
+
- Indicator formulas are correct and validated
25
+
- Data quality checks (DQAs) are conducted regularly
26
+
- Domains used in scorecards and BNA are populated with real data
27
+
28
+
### Infrastructure & Access
29
+
- Stable server hosting environment
30
+
- Reliable internet connectivity for end users
31
+
- User accounts with appropriate permissions (analysis, dashboards, apps)
32
+
- Access to the DHIS2 App Hub or ability to deploy custom apps
33
+
34
+
## Implementation Governance
35
+
Successful adoption requires strong governance structures to ensure ownership, sustainability, and alignment with national systems and guidelines.
36
+
37
+
### Leadership & Coordination
38
+
Countries should designate:
39
+
- A national coordinating team (MoH, implementing partners)
40
+
- A technical working group (TWG) for M&E or Digital Health
41
+
- A dedicated Data Use Task Team at subnational levels
42
+
43
+
These teams guide adoption, review progress, and ensure integration into existing planning processes.
44
+
45
+
### Integration With National Processes
46
+
The Data Use Apps must align with:
47
+
- Annual or quarterly performance reviews
48
+
- National health sector planning cycles
49
+
- RMNCAH, Nutrition, Immunization, HIV, or other program reviews
50
+
- Joint supervision and mentorship structures
51
+
52
+
Ensuring integration increases sustainability and reduces parallel processes.
53
+
54
+
### Roles & Responsibilities
55
+
Clear roles should be defined for:
56
+
- Ministry of Health / Program Units: Ownership, policy direction
57
+
-**District Teams**: Data review, bottleneck analysis, action follow-up
58
+
-**Facility Teams**: Data entry and local improvement actions
59
+
-**HISP Teams**: Technical configuration, user training, support
60
+
-**Partners (UNICEF, NGOs)**: Capacity building and supervision support
61
+
62
+
63
+
## Adoption Steps (High-Level Guide)
64
+
### Orientation & Stakeholder Buy-In
65
+
Introduce the role of the apps in enhancing data to action processes. Facilitate sessions with national and subnational leaders to build understanding and commitment.
66
+
67
+
### System Readiness Assessment
68
+
Evaluate:
69
+
- Data quality and availability
70
+
- Existing scorecards
71
+
- Completeness of indicator metadata
72
+
- Alignment with program needs
73
+
74
+
This ensures the tools are adopted on a solid baseline.
The Data Use Applications (Data Use Apps) are a suite of interconnected DHIS2 applications designed to strengthen data analysis, evidence based, informed decision making, and action planning across health and development programs. Developed collaboratively by **UNICEF**, **the University of Oslo (UiO)**, **HISP Uganda**, and **HISP Tanzania**, these apps empower stakeholders at all levels from national program leads to district managers and facility teams, to translate routine data into meaningful insights and tangible improvements in service delivery.
7
8
8
-
Introduction to Data use apps
9
+
## What Are Data Use Apps?
10
+
Data Use Apps are lightweight, modular DHIS2 applications focused on making data easy to interpret, actionable, and results oriented. They bring together essential tools for:
11
+
- Monitoring and tracking key performance indicators
12
+
- Identifying bottlenecks in service delivery
13
+
- Understanding root causes of performance gaps
14
+
- Planning and tracking interventions and activities
15
+
- Strengthening accountability and follow up mechanisms
16
+
17
+
Together, these applications create a streamlined workflow from **data** → **insight** → **action** → **follow up**, enabling continuous improvement cycles within health systems.
18
+
19
+
## Purpose of Data Use Apps
20
+
21
+
The primary purpose of the Data Use Apps is to close the gap between data collection and data use. While DHIS2 provides powerful data collection and reporting capabilities, many programs struggle with:
22
+
- Identifying gaps and bottlenecks affecting performance
23
+
- Coordinating follow up actions
24
+
- Tracking the implementation and impact of those actions
25
+
26
+
Data Use Apps simplify this process by giving users intuitive tools that help them:
27
+
- Review performance quickly using visual scorecards
28
+
- Detect bottlenecks through structured analysis using the Tanahashi model
29
+
- Identify root causes of poor performance
30
+
- Plan actions based on evidence
31
+
- Track progress on planned actions to ensure accountability and results
32
+
33
+
## Overall Vision
34
+
The vision of the Data Use Apps ecosystem is to build a culture of data use at all levels of the health system, where decisions are guided by evidence, resources are allocated strategically, and actions are monitored for results.
35
+
36
+
The long term goal is to provide a unified set of tools that:
37
+
- Enhance data driven planning and informed decision making
38
+
- Improve the quality and coverage of essential services
39
+
- Strengthen local and national accountability
40
+
- Support performance improvement across key indicators
41
+
- Enable governments and partners to achieve better outcomes for women, children, and vulnerable populations
42
+
43
+
By integrating analysis, diagnosis, planning, and monitoring into a single workflow, the Data Use Apps help institutions move from reactive reporting to proactive, evidence driven program management.
44
+
45
+
## Components of the Data Use Apps Suite
46
+
The suite currently consists of four core applications, each addressing a different stage of the data use cycle:
47
+
### Scorecard App
48
+
Provides a quick, visual way to track and compare the performance of key indicators. Color coding helps users immediately see where performance is strong, needs attention, or requires urgent action.
49
+
50
+
### Bottleneck Analysis (BNA) App
51
+
Helps users identify barriers affecting service delivery using the Tanahashi model (availability, accessibility, acceptability, contact, and quality). Users can analyze gaps and determine root causes of poor performance.
52
+
53
+
### BNA Linked Action Tracker
54
+
A dedicated tool that connects bottleneck and root cause findings to concrete actions. Users can plan, assign, and monitor activities directly linked to BNA results.
55
+
56
+
### Standalone Action Tracker (SAT)
57
+
A flexible app for teams that need an independent action-tracking workflow. It supports planning, coordination, and follow-up on priority actions, even beyond BNA processes.
0 commit comments