DHIS2 Performance Follow-up¶
DHIS2 performance data can help monitoring teams identify sites and indicators that require attention.
FieldOps allows teams to move beyond identifying a performance problem by recording a finding and creating a follow-up action to address it.
This connects DHIS2 reporting data with the operational workflow used to manage issues and accountability.
What you can accomplish¶
With DHIS2 performance follow-up, you can:
- Identify sites with indicators below their configured targets
- Review the affected indicator and reporting period
- Record a finding for a performance issue
- Assign a severity to the finding
- Track the finding through its lifecycle
- Add a follow-up action to a finding
- Assign responsibility for the action
- Set an action due date
- Track the action through its lifecycle
- Review whether the issue has been resolved
- Maintain an operational record of the response to the performance problem
The workflow is:
DHIS2 reporting → Performance issue → Finding → Follow-up action → Accountability
Before you begin¶
Before creating a performance follow-up, make sure that:
- The project has an active DHIS2 integration
- The relevant sites are mapped to DHIS2 organization units
- The relevant DHIS2 indicators are configured for the project
- Project targets and target directions have been configured where required
- DHIS2 reporting data has been synchronized
- The project has been reviewed for performance issues
Note
A DHIS2 performance result does not automatically create a finding or action. The monitoring team decides which performance issues require formal follow-up.
Step 1: Review project performance¶
Open the relevant project from Projects.
Review the DHIS2 Performance section.
Pay particular attention to:
- Sites without data
- Indicators below target
- Indicators without targets
- Overall reporting performance
The Action Required section can help identify sites where one or more indicators are below the configured project target.
Step 2: Identify a performance issue¶
Review the sites and indicators requiring attention.
For example:
Site: Nairobi Central Clinic
Indicator: Immunization Coverage
Actual: 61%
Target: 80%
Direction: Higher is better
Status: Below Target
This provides the evidence that a performance issue may require investigation.
Tip
Not every below-target result requires a formal finding. Use the project's monitoring procedures to determine which issues require investigation or corrective action.
Step 3: Record a finding¶
When a performance issue requires formal monitoring attention, record a finding in FieldOps.
A finding documents the issue identified by the monitoring team.
For example:
Immunization coverage at Nairobi Central Clinic is below the project target for July 2026.
The finding can capture the issue and its relevant monitoring context.
Depending on the finding configuration, users can record information such as:
- Finding title
- Description
- Severity
- Status
- Site
- Project
- Required follow-up
Finding severity¶
The severity of a finding helps the team prioritize its response.
A finding can be categorized according to the available FieldOps severity levels.
For example:
- Low
- Medium
- High
- Critical
Use the severity to communicate the importance and urgency of the issue.
For example:
High
may indicate that the performance issue requires prompt management attention.
Finding lifecycle¶
Findings can move through their configured lifecycle as the issue is investigated and addressed.
A typical workflow may be:
Open → In Review → Action Required → Resolved → Closed
The exact status used depends on the FieldOps finding workflow.
The finding provides the record of the issue while its lifecycle provides visibility into what has happened since the issue was identified.
Step 4: Add a follow-up action¶
After recording a finding, users can create a follow-up action.
The action defines what needs to be done in response to the finding.
For example:
Finding
Immunization coverage is below the project target at Nairobi Central Clinic.
Follow-up action
Conduct a facility review and develop a corrective action plan.
The action turns the finding into a specific piece of work that can be assigned and tracked.
Step 5: Assign responsibility¶
A follow-up action can be assigned to the person responsible for completing it.
For example:
Assigned to: Monitoring Officer
Assigning responsibility makes it clear who is expected to take action.
Tip
A finding describes the problem. An action describes what needs to be done about the problem.
Step 6: Set a due date¶
Where appropriate, set a due date for the follow-up action.
For example:
Due date: 30 Aug 2026
A due date helps the monitoring team track whether the required response is being completed within the expected timeframe.
Step 7: Track the action¶
The responsible user can update the action as work progresses.
The action lifecycle provides visibility into whether the required response is:
- Open
- In progress
- Completed
- Or in another configured action status
This allows managers to distinguish between issues that have been identified and issues that have actually been addressed.
Step 8: Resolve the finding¶
Once the required corrective action has been completed, the monitoring team can review the finding.
The team can verify whether the original issue has been adequately addressed.
Where appropriate, the finding can then progress through its lifecycle toward resolution and closure.
This provides an audit trail from the original performance issue through to the response.
Example end-to-end workflow¶
A project manager reviews DHIS2 performance and sees:
Site: Nairobi Central Clinic
Indicator: Immunization Coverage
Actual: 61%
Target: 80%
Status: Below Target
The manager determines that the result requires formal follow-up.
Finding¶
Title: Low immunization coverage at Nairobi Central Clinic
Description: Immunization coverage for July 2026 is 61%, below the project target of 80%.
Severity: High
The team then creates a follow-up action.
Action¶
Action: Conduct a facility review and develop a corrective action plan.
Assigned to: Monitoring Officer
Due date: 30 Aug 2026
Status: Open
The monitoring officer completes the required work and updates the action.
The team then reviews the finding and confirms whether the issue has been resolved.
Why this matters¶
DHIS2 provides valuable reporting information, but identifying a performance problem is only part of the monitoring process.
Without a follow-up workflow, a team may identify that:
Immunization coverage is below target.
but still have no structured way to answer:
- Who is responsible?
- What needs to be done?
- When should it be completed?
- What is the current action status?
- Has the issue been resolved?
FieldOps provides this operational layer.
The workflow becomes:
Reporting
DHIS2 provides the performance data.
↓
Performance monitoring
FieldOps compares performance against project targets.
↓
Finding
The monitoring team records the issue.
↓
Action
The team defines what needs to be done.
↓
Accountability
Responsibility and due dates are assigned.
↓
Resolution
The team tracks the response and closes the issue when resolved.
DHIS2 remains the reporting source¶
FieldOps does not replace DHIS2 as the source of the underlying reporting data.
DHIS2 remains responsible for reporting data such as:
- Indicator values
- Reporting periods
- Organization units
- DHIS2 indicators
FieldOps uses that information to support project-level monitoring and operational follow-up.
This separation allows organizations to continue using DHIS2 for reporting while using FieldOps for:
- Project monitoring
- Performance review
- Findings
- Follow-up actions
- Responsibility
- Accountability
Performance trends and follow-up¶
Performance trends can provide additional context when deciding whether a finding requires action.
For example:
| Period | Immunization Coverage |
|---|---|
| May 2026 | 72% |
| Jun 2026 | 68% |
| Jul 2026 | 61% |
A single below-target result may require investigation.
However, a sustained decline across several reporting periods can provide stronger evidence that a finding and corrective action are required.
Tip
Review the performance trend together with the current result before deciding whether an issue requires formal follow-up.
Missing data versus poor performance¶
A site without DHIS2 data should not automatically be treated as a below-target performance result.
These are different situations.
Missing data¶
The site has no relevant DHIS2 data for the reporting period.
Possible reasons include:
- The site has not reported
- Data has not yet been synchronized
- The organization unit mapping is incorrect
- The indicator has no data for the period
Below target¶
The site has a DHIS2 value, but the value does not meet the configured project target.
For example:
Actual: 61%
Target: 80%
Direction: Higher is better
This is a measurable performance issue.
Note
Investigate missing data separately from below-target performance. A missing value does not necessarily mean poor performance.
Recommended follow-up workflow¶
For recurring monitoring reviews, the following workflow is recommended:
- Open the project.
- Review DHIS2 Performance.
- Review Sites Without Data.
- Review Sites Requiring Attention.
- Review the relevant performance trend.
- Determine which issues require formal follow-up.
- Record a finding.
- Set the finding severity and relevant details.
- Add a follow-up action.
- Assign the responsible person.
- Set a due date where appropriate.
- Track the action.
- Review the outcome.
- Resolve and close the finding when appropriate.
What FieldOps adds to DHIS2¶
The value of the integration is not simply displaying DHIS2 data inside FieldOps.
FieldOps connects reporting data to an operational workflow.
An organization can therefore move from:
"This site is below target."
to:
"This is the finding."
then:
"This is what needs to be done."
and finally:
"This person is responsible, the action is due on this date, and we can track whether it was completed."
This creates a complete monitoring chain:
DHIS2 → Performance → Finding → Action → Accountability
What to do next¶
After identifying a performance issue, record the finding and create a follow-up action where formal intervention is required.