Analyze DHIS2 Performance¶

FieldOps allows you to analyze synchronized DHIS2 data directly from a project. This helps monitoring teams understand how sites are performing against configured DHIS2 indicators and quickly identify areas that require attention.

Before You Begin¶

Before analyzing DHIS2 performance, make sure that:

DHIS2 is connected to your FieldOps organization.
DHIS2 metadata has been synchronized.
The relevant DHIS2 organization units are mapped to FieldOps sites.
The project has DHIS2 indicators configured.
DHIS2 data has been synchronized for the reporting period you want to analyze.

For more information, see:

Open the Project¶

Sign in to FieldOps.
Open the relevant Program.
Open the Project you want to analyze.
Open the project's DHIS2 Performance section.

The DHIS2 Performance section is available for projects that have DHIS2 integration configured.

Select the Reporting Period¶

Before running the analysis, select the period you want to analyze.

Start Date¶

Select the beginning of the reporting period using Start Date.

For example:

2026-07-01

End Date¶

Select the end of the reporting period using End Date.

For example:

2026-07-31

The start and end dates determine the DHIS2 reporting period used for the performance analysis.

Tip

Select dates that correspond to a period for which DHIS2 data has already been synchronized.

Analyze Performance¶

After selecting the reporting period:

Select the Start Date.
Select the End Date.
Click Analyze Performance.
Wait for FieldOps to retrieve and process the synchronized DHIS2 performance data.

FieldOps then calculates the performance information for the project's mapped sites and configured indicators.

Understanding the Performance Summary¶

The performance summary provides an overview of the project's DHIS2 performance for the selected reporting period.

Reporting Period¶

Shows the period used for the analysis.

This confirms that the results correspond to the dates you selected.

Sites Mapped¶

Shows the number of FieldOps sites that are mapped to DHIS2 organization units for the project.

A site must have a valid DHIS2 organization unit mapping before FieldOps can associate DHIS2 data with that site.

Sites With Data¶

Shows the number of mapped sites for which DHIS2 data was available for the selected reporting period.

Sites Without Data¶

Shows the number of mapped sites for which no DHIS2 performance data was found.

These sites may require investigation.

Indicators Tracked¶

Shows the number of DHIS2 indicators configured for the project and included in the analysis.

Performance Records¶

Shows the total number of performance records returned for the selected reporting period.

Records With Data¶

Shows how many performance records contain an actual DHIS2 value.

On Target¶

Shows the number of performance records where the reported value meets or exceeds the configured target.

Below Target¶

Shows the number of performance records where the reported value is below the configured target.

No Target¶

Shows performance records where a DHIS2 value exists but no target has been configured for comparison.

Review Sites Requiring Attention¶

The Action Required section highlights sites and indicators that may require follow-up.

Use this section to identify:

Sites performing below their configured targets.
Sites with missing DHIS2 data.
Indicators that require investigation.
Performance gaps that may require field-level intervention.

This allows monitoring teams to focus their attention on the areas that need it most instead of reviewing every DHIS2 record individually.

Review Performance Trends¶

FieldOps can also display a DHIS2 Performance Trend for recent reporting periods.

The trend allows you to identify whether performance is:

Improving.
Declining.
Remaining stable.
Showing inconsistent results between reporting periods.

Use the trend together with the current reporting period to distinguish a temporary performance issue from a recurring problem.

Example¶

Suppose a project has:

10 mapped sites.
5 configured DHIS2 indicators.
50 expected performance records.
45 records containing data.
30 records on target.
15 records below target.
5 records with no data.

The analysis allows the monitoring team to quickly identify:

Which 5 sites have missing data.
Which indicators are below target.
Which sites require attention.
Whether the performance issue is improving or worsening compared with previous periods.

What to Do When Performance Is Below Target¶

If a site or indicator is below target, review the result and determine whether field-level follow-up is required.

If intervention is needed:

Identify the affected site.
Review the affected indicator and performance result.
Determine what action is required.
Create a follow-up action in FieldOps.
Assign the action to the responsible person.
Set an appropriate due date.
Track the action until it is completed.

See Performance Follow-up for more information.

What to Do When Data Is Missing¶

If a site appears under Sites Without Data, or a performance record does not contain a value, investigate the cause.

Check the following:

Confirm that the FieldOps site is mapped to the correct DHIS2 organization unit.
Confirm that DHIS2 contains data for the selected reporting period.
Confirm that the relevant DHIS2 data elements and indicators are configured correctly.
Check the DHIS2 synchronization status.
Synchronize the required DHIS2 data if necessary.
Return to the project and run Analyze Performance again.

See DHIS2 Sync Health for information about checking synchronization.

If Performance Is on Target¶

If performance is on target, no immediate corrective action may be required.

Continue monitoring the project across subsequent reporting periods to determine whether performance remains consistent.

The performance trend can help identify longer-term changes even when the current reporting period is performing well.

Refreshing the Analysis¶

When new DHIS2 data becomes available, synchronize the relevant data and then run the analysis again using the appropriate reporting period.

This ensures that the project performance view reflects the latest synchronized DHIS2 data.

Troubleshooting¶

If the performance analysis does not return the expected results, check:

The DHIS2 connection is active.
The required DHIS2 metadata has been synchronized.
The project's sites have been mapped to DHIS2 organization units.
The project has DHIS2 indicators configured.
DHIS2 data exists for the selected reporting period.
The relevant DHIS2 data has been synchronized successfully.

If the problem persists, see DHIS2 Troubleshooting.

Automatic Follow-Up for Below-Target Performance¶

FieldOps can automatically turn DHIS2 performance issues into an actionable field follow-up workflow.

When you analyze DHIS2 performance and an indicator is found to be below its configured target, FieldOps automatically creates:

A Visit for the affected site.
A Finding within that visit identifying the below-target indicator.

This means you do not need to manually create a visit or finding for every performance issue.

How it works¶

The workflow is:

DHIS2 Data → Performance Analysis → Below-Target Indicator → Visit Created → Finding Created → Follow-Up Action

For example, suppose a project tracks an immunization indicator with a target of 80%.

If DHIS2 reports:

Target: 80%
Actual: 62%
Status: Below Target

FieldOps can automatically create a follow-up visit for the affected site and create a finding identifying the performance issue.

The finding becomes the starting point for your accountability workflow.

What is created automatically?¶

1. Visit¶

FieldOps creates a visit associated with the affected project and site.

The visit provides a dedicated place to investigate and document the performance issue.

2. Finding¶

A finding is automatically created within the visit.

The finding identifies that the site's DHIS2 performance is below the configured target.

You can then review the finding and determine what corrective action is required.

Continue the follow-up workflow¶

Once the visit and finding have been created, you can use the normal FieldOps follow-up workflow.

From the finding, you can:

Review the performance issue.
Document observations and additional information.
Create an Action to address the issue.
Assign the action to a responsible person.
Set a due date.
Track the action's progress.
Add updates as work progresses.
Mark the action as completed when the issue has been addressed.

This creates a complete accountability chain:

DHIS2 Performance → Visit → Finding → Action → Resolution

Important¶

The automatically created visit and finding do not replace your normal monitoring workflow.

They provide a structured starting point for investigating performance problems identified from DHIS2 data.

You can open the visit, review the finding, add additional evidence or information, and create follow-up actions as needed.

What to Do Next¶

After analyzing DHIS2 performance:

Review the indicators that are below target.
Open the automatically created visit for the affected site.
Review the finding created for the performance issue.
Investigate the underlying cause during the visit.
Create an action from the finding if corrective action is required.
Assign the action to the responsible person.
Set a due date and track progress through action updates.
Complete the action once the issue has been addressed.

This allows FieldOps to turn DHIS2 performance data into a practical field monitoring and accountability workflow.

What to Do Next¶

After analyzing DHIS2 performance, use the results to drive follow-up and accountability.

The recommended workflow is:

Synchronize DHIS2 Data → Analyze Performance → Identify Issues → Create Follow-Up Actions → Track Resolution

If you identified performance issues that require intervention, continue with Performance Follow-up.

If you identified missing or incomplete data, continue with DHIS2 Sync Health.

If you need to configure or change the indicators used by the project, see Configure Project Indicators.