DHIS2 Sync Health¶
FieldOps provides project-level synchronization information so monitoring teams can understand whether the DHIS2 data used by a project is connected and synchronized successfully.
The DHIS2 Sync Health section is available on the project view when the project has an active DHIS2 integration.
It provides a quick indication of:
- When DHIS2 metadata was last synchronized
- The reporting period being reviewed
- How many relevant DHIS2 connections are being used by the project
- Whether those connections are healthy
- Whether synchronization requires attention
Before you begin¶
Before reviewing DHIS2 Sync Health, make sure that:
- A DHIS2 connection has been created
- The connection has been tested
- DHIS2 metadata has been synchronized
- At least one DHIS2 indicator has been configured for the project
- Sites used by the project have been mapped where required
Note
DHIS2 Sync Health is displayed at the project level. FieldOps determines the relevant DHIS2 connections from the DHIS2 mappings used by the project's sites.
Step 1: Open the project¶
Sign in to FieldOps and open the project you want to review.
Open the project from the Projects section.
If the project has an active DHIS2 integration, the project view will include the DHIS2 Sync Health section.
Step 2: Review DHIS2 Sync Health¶
Locate the DHIS2 Sync Health section on the project view.
The section displays four pieces of information:
- Last Synchronized
- Reporting Period
- DHIS2 Connections
- Sync Status
Last Synchronized¶
Last Synchronized shows the most recent successful DHIS2 metadata synchronization recorded for the relevant DHIS2 connection or connections.
For example:
Last Synchronized: 22 Aug 2026, 04:30
This helps users determine how recently FieldOps successfully synchronized DHIS2 metadata.
Note
The Last Synchronized timestamp is updated by the DHIS2 metadata synchronization process. It is not updated simply because a user views a project or tests a connection.
Reporting Period¶
Reporting Period shows the reporting period associated with the current DHIS2 performance view.
For example:
Reporting Period: July 2026
This provides context when interpreting the DHIS2 performance information shown elsewhere on the project.
The synchronization timestamp and reporting period represent different concepts:
- Last Synchronized indicates when synchronization was last successfully recorded.
- Reporting Period indicates the DHIS2 reporting period being evaluated.
A recent synchronization does not necessarily mean that the reporting period contains complete data.
DHIS2 Connections¶
DHIS2 Connections shows the number of distinct DHIS2 connections relevant to the project.
For example:
DHIS2 Connections: 2
A project may use DHIS2 data from more than one connection.
This is particularly useful for organizations that operate multiple DHIS2 environments.
Examples include:
- Different country-level DHIS2 instances
- Separate production and development environments
- Different partner-managed DHIS2 servers
- Different DHIS2 systems used by different programs
Note
FieldOps does not assume that an organization has only one DHIS2 connection.
The project determines which connections are relevant through the DHIS2 connections associated with its mapped sites.
Sync Status¶
Sync Status provides an overall indication of the health of the relevant DHIS2 connections.
FieldOps can display one of three statuses:
- Healthy
- Attention
- Not synchronized
Healthy¶
Healthy indicates that the relevant DHIS2 connections have been successfully tested as connected and a successful synchronization has been recorded.
For example:
Sync Status: Healthy
This indicates that the project has an established DHIS2 connection and synchronization has occurred successfully.
Attention¶
Attention indicates that the DHIS2 integration requires investigation.
This can occur when:
- A relevant DHIS2 connection has failed its connection test
- A connection is not in the expected connected state
- Synchronization information is incomplete
- A successful synchronization has not been recorded for all relevant connection conditions
For example:
Sync Status: Attention
When this status appears, review the relevant DHIS2 connection and synchronization information.
Warning
A project showing Attention does not necessarily mean that all DHIS2 data is unavailable. It indicates that the integration state requires investigation.
Not synchronized¶
Not synchronized indicates that no successful synchronization has yet been recorded for the relevant DHIS2 connection.
For example:
Sync Status: Not synchronized
This can occur when a connection has been created and tested but DHIS2 metadata has not yet been successfully synchronized.
Understanding multiple DHIS2 connections¶
An organization can have multiple DHIS2 connections in FieldOps.
For example, an organization could have:
| Connection | Purpose |
|---|---|
| Kenya DHIS2 | Kenya reporting environment |
| Uganda DHIS2 | Uganda reporting environment |
| DHIS2 Production | Production reporting |
| DHIS2 Development | Testing and development |
A project may use one or more of these connections depending on how its sites are mapped.
FieldOps therefore evaluates project sync health using the connections associated with the project's mapped DHIS2 sites rather than simply displaying every DHIS2 connection belonging to the organization.
How FieldOps determines the relevant connections¶
FieldOps looks at the project's sites and their DHIS2 mappings.
The relationship is:
Project
↓
Project Sites
↓
DHIS2 Site Mappings
↓
DHIS2 Connections
This means that the sync health shown for a project is based on the DHIS2 sources actually associated with that project's mapped sites.
Last synchronization versus connection testing¶
It is important to distinguish between connection testing and synchronization.
Connection testing¶
A connection test verifies that FieldOps can communicate with the configured DHIS2 server using the configured authentication method.
A successful test confirms that the connection is accessible.
Metadata synchronization¶
Metadata synchronization retrieves the DHIS2 configuration information required by FieldOps.
This can include:
- Organization units
- Data elements
- Data sets
- Indicators
The synchronization process records the successful synchronization timestamp.
Therefore:
Connection test
Can FieldOps connect to DHIS2?
Metadata synchronization
Has FieldOps successfully retrieved the DHIS2 metadata it needs?
These are related but different operations.
What Last Synchronized does not mean¶
The Last Synchronized timestamp should not be interpreted as the timestamp of every DHIS2 data value retrieved by FieldOps.
It represents the most recent successful DHIS2 metadata synchronization recorded by FieldOps.
For example:
Last Synchronized: 22 Aug 2026, 04:30
This means that FieldOps successfully recorded a metadata synchronization at that time.
It does not necessarily mean that every DHIS2 reporting value was created or updated at exactly that time.
Tip
Use the synchronization status together with the DHIS2 performance information when investigating missing or unexpected reporting data.
Investigating an Attention status¶
If a project displays Attention, review the DHIS2 configuration in the following order.
1. Check the DHIS2 connection¶
Open the relevant DHIS2 connection and review its connection status.
Confirm that:
- The DHIS2 server URL is correct
- The authentication credentials are valid
- The connection is active
- The DHIS2 server is accessible
2. Test the connection¶
Run Test Connection for the relevant DHIS2 connection.
If the test fails, review the error message and correct the connection configuration.
3. Synchronize DHIS2 metadata¶
If the connection is working but metadata is outdated or missing, run the DHIS2 metadata synchronization.
4. Check site mappings¶
Confirm that the project's FieldOps sites are mapped to the correct DHIS2 organization units.
5. Check project indicators¶
Confirm that the project has the expected DHIS2 indicators configured and that they are active.
6. Check reporting data¶
If the connection and metadata are healthy but performance data is missing, investigate whether DHIS2 contains data for the relevant reporting period.
Example¶
A project uses two DHIS2 connections:
Kenya DHIS2
Regional DHIS2
The project has sites mapped to both connections.
The project view displays:
DHIS2 Connections: 2
Last Synchronized: 22 Aug 2026, 04:30
Sync Status: Attention
The monitoring manager checks the connections and discovers that the Regional DHIS2 connection failed its latest connection test.
The manager can then:
- Open the Regional DHIS2 connection.
- Review the connection error.
- Correct the authentication or server configuration.
- Test the connection again.
- Synchronize the required DHIS2 metadata.
- Return to the project and review the sync health.
This allows the project view to act as an early warning point for DHIS2 integration problems.
Recommended monitoring practice¶
Monitoring teams should review DHIS2 Sync Health when:
- Preparing monthly project reports
- Reviewing unexpected missing data
- Investigating sites that appear not to be reporting
- Before conducting performance reviews
- After changing DHIS2 connection credentials
- After changing DHIS2 site mappings
- After adding new project indicators
A healthy connection does not replace reviewing the actual reporting data, but it provides an important first check when investigating DHIS2-related issues.
DHIS2 integration health workflow¶
A typical workflow is:
- Connect the DHIS2 instance.
- Test the connection.
- Synchronize DHIS2 metadata.
- Map DHIS2 organization units to FieldOps sites.
- Configure project indicators.
- Synchronize reporting data.
- Review project DHIS2 performance.
- Check Sync Health when data appears incomplete or unexpected.
- Investigate and correct integration issues where necessary.
This creates a simple operational chain:
Connection → Synchronization → Mapping → Performance → Monitoring
What to do next¶
If the DHIS2 connection is healthy, continue reviewing project performance and sites requiring attention.
If synchronization requires attention, review the DHIS2 connection and synchronization configuration before relying on the project's performance data.