DHIS2¶
FieldOps integrates with DHIS2 to bring reporting data into the operational workflows used by monitoring teams.
Instead of switching between DHIS2 and FieldOps to understand project performance, teams can connect their DHIS2 instance, synchronize DHIS2 metadata, map FieldOps sites to DHIS2 organization units, select indicators for a project, and view performance directly from the project.
What you can accomplish¶
With the DHIS2 integration, you can:
- Connect a FieldOps organization to one or more DHIS2 instances
- Test DHIS2 connections before using them
- Synchronize DHIS2 organization units
- Synchronize DHIS2 data elements
- Synchronize DHIS2 data sets and their data element relationships
- Synchronize DHIS2 indicators
- Map FieldOps sites to DHIS2 organization units
- Select which DHIS2 indicators a project should track
- Configure project-specific indicator targets
- Define whether higher or lower indicator values represent better performance
- View DHIS2 performance for the project's reporting period
- See how many project sites are mapped to DHIS2
- See which mapped sites are reporting data
- Identify sites without data
- See indicators that are on target or below target
- Identify sites requiring attention
- Generate findings from identified monitoring issues
- Create and track follow-up actions for findings
- Review recent DHIS2 performance across multiple reporting periods
- Monitor the health and recency of DHIS2 synchronization
This allows DHIS2 to provide the reporting data while FieldOps provides the project, site, monitoring, findings, and follow-up workflow around that data.
How the integration works¶
The DHIS2 integration follows these main steps:
- Connect a DHIS2 instance to FieldOps.
- Test the DHIS2 connection.
- Synchronize DHIS2 metadata.
- Map DHIS2 organization units to FieldOps sites.
- Select DHIS2 indicators for a project.
- Configure project targets and target directions.
- Synchronize DHIS2 reporting data.
- Review DHIS2 performance from the project.
- Identify sites without data or below-target indicators.
- Record findings and create follow-up actions where required.
DHIS2 connections¶
A FieldOps organization can have multiple DHIS2 connections.
This is useful when an organization works with different DHIS2 environments or systems.
For example:
- Different programs may use different DHIS2 instances
- A development environment may be kept separate from production
- Different partners may report through different DHIS2 servers
- A regional organization may work with multiple country-level DHIS2 instances
- Different projects may use different DHIS2 environments
FieldOps therefore does not assume that one organization has only one DHIS2 connection.
DHIS2 connections are associated with the DHIS2 data used by mapped sites. This allows projects to work with the appropriate DHIS2 source.
DHIS2 metadata¶
FieldOps can synchronize the DHIS2 metadata required to configure the integration.
The synchronization includes:
Organization units¶
DHIS2 organization units are synchronized into FieldOps so they can be associated with FieldOps sites.
Data elements¶
DHIS2 data elements are synchronized and made available to the FieldOps DHIS2 integration.
Data sets¶
DHIS2 data sets are synchronized together with their relationships to data elements.
Indicators¶
DHIS2 indicators are synchronized so projects can select the indicators they want to track.
Note
Metadata synchronization does not automatically make every DHIS2 indicator a project indicator. Projects explicitly configure the indicators they want to track.
Site mapping¶
FieldOps sites can be mapped to DHIS2 organization units.
This creates the relationship between the operational location in FieldOps and the corresponding reporting location in DHIS2.
For example:
FieldOps Site
Nairobi Central Clinic
DHIS2 Organization Unit
Nairobi Central Clinic
Once a site is mapped, FieldOps can use the corresponding DHIS2 organization unit when retrieving performance data.
Warning
Accurate site mapping is important. An incorrect mapping can cause FieldOps to display DHIS2 data for the wrong location.
Project indicators¶
DHIS2 indicators can be associated with individual FieldOps projects.
This allows different projects to track different indicators even when they use the same DHIS2 connection.
For each project indicator, FieldOps can store project-specific configuration such as:
- Target value
- Target direction
- Display order
- Active or inactive status
Target direction¶
FieldOps supports two common performance interpretations.
Higher is better
Used when increasing the indicator represents improved performance.
Examples:
- Immunization coverage
- Number of beneficiaries reached
- Percentage of facilities reporting
Lower is better
Used when decreasing the indicator represents improved performance.
Examples:
- Stock-out rate
- Disease incidence
- Average response time
This allows FieldOps to determine whether an indicator is performing against its configured project target.
Project DHIS2 performance¶
Once the integration has been configured, project users can view DHIS2 performance from the project.
The DHIS2 Performance section provides a high-level view of the project's reporting performance.
It includes:
- Reporting period
- Sites mapped
- Sites reporting
- Sites without data
- Indicators tracked
- Performance records
- Records containing data
- Indicators on target
- Indicators below target
- Indicators without configured targets
This gives monitoring teams a quick way to understand whether project sites are reporting and whether tracked indicators are performing as expected.
Sites requiring attention¶
FieldOps can identify sites where one or more tracked DHIS2 indicators are below the configured target.
The project can therefore highlight:
- The affected site
- The indicator
- Actual value
- Target value
- Target direction
- Performance status
- Reporting period
For example:
Site: Nairobi Central Clinic
Indicator: Immunization Coverage
Actual: 61%
Target: 80%
Status: Below Target
Period: July 2026
This turns DHIS2 reporting data into an actionable monitoring signal.
Findings and follow-up actions¶
DHIS2 performance can be used as a starting point for the FieldOps monitoring and accountability workflow.
When a project identifies a performance issue, users can record a finding in FieldOps.
A finding can document the issue identified during monitoring, including its severity and lifecycle status.
Users can then add a follow-up action to the finding.
Actions allow the team to move from identifying a problem to assigning responsibility and tracking the required response.
The workflow is:
- DHIS2 provides the reporting data.
- FieldOps identifies an indicator or site requiring attention.
- The monitoring team records a finding.
- The finding documents the issue and its severity.
- A follow-up action is created.
- Responsibility for the action can be assigned.
- The action is tracked through its lifecycle.
- The team can review the outcome and close the issue when resolved.
For example:
DHIS2 performance
Immunization coverage: 61%
Target: 80%
Site: Nairobi Central Clinic
↓
FieldOps 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.
↓
Accountability
Assigned to: Monitoring Officer
Due date: 30 Aug 2026
Status: Open
This creates a workflow from reporting data to operational accountability.
Tip
DHIS2 provides the reporting data. FieldOps provides the operational workflow for understanding the data, recording issues, assigning follow-up actions, and tracking accountability.
DHIS2 performance trend¶
FieldOps provides a view of recent DHIS2 performance across multiple reporting periods.
This helps users identify whether performance is:
- Improving
- Declining
- Stable
- Missing data
The project performance view currently displays the three most recent reporting periods.
Sync health¶
FieldOps provides DHIS2 synchronization information at project level.
The DHIS2 Sync Health section shows:
- Last synchronized
- Reporting period
- Number of relevant DHIS2 connections
- Overall synchronization status
The synchronization status can indicate:
Healthy¶
The relevant DHIS2 connections have been successfully tested and synchronization has occurred.
Attention¶
A relevant DHIS2 connection has failed its connection test or the synchronization state requires attention.
Not synchronized¶
No successful synchronization has yet been recorded for the relevant DHIS2 connection.
Note
The Last Synchronized timestamp represents the most recent successful DHIS2 metadata synchronization recorded by FieldOps.
Recommended setup workflow¶
For a new DHIS2 project, use the following order:
- Create a DHIS2 connection.
- Test the connection.
- Synchronize DHIS2 metadata.
- Review the synchronized organization units and indicators.
- Map FieldOps sites to DHIS2 organization units.
- Configure the DHIS2 indicators for the project.
- Set indicator targets and target directions.
- Synchronize DHIS2 reporting data.
- Open the project and review DHIS2 performance.
- Review sites without data and sites requiring attention.
- Record findings for issues that require monitoring attention.
- Create and track follow-up actions where required.
What FieldOps adds to DHIS2¶
DHIS2 remains the source of reporting data.
FieldOps adds the operational layer around that data, allowing teams to move from identifying a performance problem to taking action.
With the integration, teams can combine DHIS2 reporting with:
- Projects
- Sites
- Monitoring workflows
- Performance targets
- Findings
- Follow-up actions
- Assigned responsibilities
- Action tracking
- Accountability
The result is a workflow that connects:
DHIS2 reporting → performance monitoring → findings → actions → accountability
This means teams can use DHIS2 for reporting while using FieldOps to monitor project performance and coordinate the operational response.
DHIS2 documentation¶
Use the following guides to configure and manage the DHIS2 integration: