Configure Project Indicators¶
After synchronizing DHIS2 metadata and mapping FieldOps sites to DHIS2 organization units, configure the DHIS2 indicators that each project should track.
Project indicator configuration allows FieldOps to turn DHIS2 reporting data into project-specific performance monitoring.
Different projects can track different DHIS2 indicators, even when they use the same DHIS2 connection.
Before you begin¶
You need:
- An active DHIS2 connection
- Successfully synchronized DHIS2 metadata
- At least one FieldOps site mapped to a DHIS2 organization unit
- A FieldOps project
- DHIS2 indicators available in FieldOps
- Permission to configure project integrations
Note
Synchronizing DHIS2 indicators does not automatically add them to projects. Each project must explicitly configure the indicators it wants to track.
How project indicators work¶
A DHIS2 indicator exists in the connected DHIS2 system.
FieldOps allows you to associate that indicator with a specific project.
For each project indicator, FieldOps can configure:
- The DHIS2 indicator
- Target value
- Target direction
- Display order
- Active or inactive status
This allows the same DHIS2 indicator to be monitored differently across projects.
For example, one project might configure:
Immunization Coverage — Target: 80%
while another project might configure:
Immunization Coverage — Target: 90%
The underlying DHIS2 indicator remains the same, but the project-specific performance expectation can be different.
Step 1: Open the project¶
Sign in to FieldOps and open the project where you want to configure DHIS2 indicators.
Open the project's DHIS2 integration or indicator configuration section.
Step 2: Add a DHIS2 indicator¶
Select the option to add a DHIS2 indicator to the project.
FieldOps will provide the DHIS2 indicators that have already been synchronized from the configured DHIS2 connection.
Select the indicator you want the project to track.
For example:
Indicator
Immunization Coverage
Save the project indicator configuration.
Step 3: Configure the target¶
Set the target value that represents the expected project performance.
For example:
Indicator
Immunization Coverage
Target
80
The target is used by FieldOps when determining whether the indicator is performing as expected.
Note
The target is configured at the project level. Different projects can therefore use different targets for the same DHIS2 indicator.
Step 4: Configure the target direction¶
Specify whether a higher or lower indicator value represents better performance.
FieldOps supports two target directions.
Higher is better¶
Use Higher is better when an increase in the indicator represents improved performance.
Examples include:
- Immunization coverage
- Treatment coverage
- Number of beneficiaries reached
- Percentage of facilities reporting
For example:
Target: 80%
Actual: 85%
Result: On Target
Lower is better¶
Use Lower is better when a decrease in the indicator represents improved performance.
Examples include:
- Stock-out rate
- Disease incidence
- Average response time
- Default rate
For example:
Target: 10%
Actual: 6%
Result: On Target
Warning
Choose the target direction carefully. FieldOps uses this setting to determine whether the actual DHIS2 value is performing above or below the configured target.
Step 5: Save the indicator configuration¶
After selecting the indicator and configuring its target and target direction, save the project indicator.
The indicator is now part of the project's DHIS2 performance configuration.
Active and inactive indicators¶
Project indicators can be configured as active or inactive.
An active indicator is included in the project's DHIS2 performance monitoring.
An inactive indicator remains configured for the project but is not actively used for current performance monitoring.
This can be useful when:
- A project stops monitoring an indicator temporarily
- An indicator is replaced by another indicator
- Project monitoring priorities change
- Historical configuration needs to be retained
Display order¶
Project indicators can have a display order.
This allows the project team to control the order in which indicators are presented in the project's DHIS2 performance configuration.
For example:
- Immunization Coverage
- Stock-out Rate
- Facility Reporting Rate
Use an order that makes sense for the project's monitoring priorities.
Multiple indicators¶
A project can track multiple DHIS2 indicators.
For example, a health project might track:
- Immunization Coverage
- Stock-out Rate
- Facility Reporting Rate
- Treatment Completion Rate
FieldOps can then evaluate the performance of the configured indicators for the project's mapped sites.
How indicator configuration affects project performance¶
Once an indicator has been configured, FieldOps can use the synchronized DHIS2 reporting data to evaluate project performance.
The workflow is:
- A DHIS2 indicator is synchronized into FieldOps.
- The indicator is added to a FieldOps project.
- A project target is configured.
- A target direction is configured.
- FieldOps retrieves the corresponding DHIS2 reporting data.
- The value is associated with the mapped FieldOps site.
- FieldOps compares the actual value with the configured target.
- The project performance view displays the result.
This allows monitoring teams to move from raw reporting data to project-specific performance assessment.
Performance status¶
FieldOps can classify configured indicator performance based on the actual value and the project's target configuration.
The project performance view can show indicators as:
- On Target
- Below Target
- No Target
On Target¶
The actual DHIS2 value meets the configured project target according to the target direction.
Below Target¶
The actual DHIS2 value does not meet the configured project target.
This can identify a potential monitoring issue requiring investigation or follow-up.
No Target¶
No target has been configured for the indicator.
Without a target, FieldOps cannot determine whether the indicator is performing against the project's expected level.
Tip
Configure targets for indicators where the project team needs a clear performance threshold.
Sites requiring attention¶
When a configured indicator is below its project target, FieldOps can identify the affected site.
For example:
Site
Nairobi Central Clinic
Indicator
Immunization Coverage
Actual
61%
Target
80%
Status
Below Target
This allows monitoring teams to identify where attention may be required.
Findings and follow-up actions¶
A below-target DHIS2 indicator can become a starting point for the FieldOps findings and action workflow.
For example:
DHIS2 performance
Immunization Coverage: 61%
Target: 80%
Site: Nairobi Central Clinic
The monitoring team can record a finding describing the issue.
For example:
Immunization coverage is below the project target at Nairobi Central Clinic.
The team can then create a follow-up action for the finding.
For example:
Conduct a facility review and develop a corrective action plan.
The action can then be assigned and tracked through its lifecycle.
This connects project indicator monitoring with operational accountability:
DHIS2 indicator → performance result → finding → action → accountability
Tip
DHIS2 provides the reporting data and FieldOps provides the workflow for identifying issues, recording findings, assigning actions, and tracking follow-up.
Changing an indicator configuration¶
Project indicator configuration may need to change as project priorities evolve.
You may need to update:
- Target value
- Target direction
- Display order
- Active or inactive status
Before changing a target, confirm that the new target reflects the project's current monitoring requirements.
Removing or deactivating an indicator¶
If a project no longer needs to actively monitor an indicator, consider making the indicator inactive rather than treating the DHIS2 indicator itself as deleted.
The DHIS2 indicator remains part of the synchronized DHIS2 metadata.
Project configuration determines whether the project actively tracks it.
Note
Deactivating a project indicator does not delete the indicator from DHIS2 or from FieldOps's synchronized DHIS2 metadata.
Troubleshooting¶
The indicator I need is not available¶
Check that:
- The correct DHIS2 connection is being used
- The indicator exists in DHIS2
- DHIS2 metadata has been synchronized
- The DHIS2 account can access the indicator
- The indicator is available in the synchronized metadata
If the indicator was recently created in DHIS2, synchronize metadata again.
The indicator has data but no performance status¶
Check whether a project target has been configured.
If there is no target, FieldOps cannot classify the indicator as on target or below target.
The performance result is the opposite of what I expected¶
Check the project's target direction.
For indicators where higher values represent better performance, use:
Higher is better
For indicators where lower values represent better performance, use:
Lower is better
Recommended configuration¶
For each indicator that a project actively monitors:
- Select the DHIS2 indicator.
- Set the project target.
- Select the correct target direction.
- Set the display order if required.
- Keep the indicator active.
- Save the configuration.
- Synchronize DHIS2 reporting data.
- Review the resulting project performance.
What to do next¶
After configuring project indicators, synchronize DHIS2 reporting data so FieldOps can evaluate the configured indicators for your mapped sites.