Map Sites to DHIS2 Organization Units¶
After synchronizing DHIS2 metadata, map your FieldOps sites to the corresponding DHIS2 organization units.
Site mapping tells FieldOps which DHIS2 organization unit represents each operational site. This relationship is used when FieldOps retrieves DHIS2 reporting data for project performance monitoring.
Before you begin¶
You need:
- An active DHIS2 connection
- Successfully synchronized DHIS2 metadata
- At least one FieldOps site
- The corresponding DHIS2 organization unit available in FieldOps
- Permission to manage DHIS2 site mappings
Note
A FieldOps site must be mapped to a DHIS2 organization unit before FieldOps can use DHIS2 reporting data for that site.
How site mapping works¶
FieldOps maintains a relationship between:
FieldOps Site
Nairobi Central Clinic
and:
DHIS2 Organization Unit
Nairobi Central Clinic
Once the mapping is created, FieldOps knows which DHIS2 organization unit to use when retrieving reporting data for the FieldOps site.
The mapping is specific to a DHIS2 connection.
Note
The same FieldOps organization can have multiple DHIS2 connections. A site may therefore be associated with the appropriate DHIS2 source used by the project.
Step 1: Open the site¶
Sign in to FieldOps and open the project or site where you want to configure the DHIS2 mapping.
Open the relevant Site.
Locate the DHIS2 integration or mapping section.
Step 2: Select a DHIS2 connection¶
Select the DHIS2 connection that contains the organization unit you want to use.
If your organization has multiple DHIS2 connections, make sure you select the correct one.
For example, an organization might have:
- Kenya Production DHIS2
- Uganda Production DHIS2
- Development DHIS2
The correct connection should correspond to the DHIS2 system where the site's reporting data is maintained.
Step 3: Select the DHIS2 organization unit¶
Select the DHIS2 organization unit that corresponds to the FieldOps site.
FieldOps uses the organization units synchronized from the selected DHIS2 connection.
For example:
FieldOps Site
Nairobi Central Clinic
DHIS2 Organization Unit
Nairobi Central Clinic
Save the mapping.
Warning
Make sure the DHIS2 organization unit represents the same physical or operational location as the FieldOps site. An incorrect mapping can cause FieldOps to associate the site with the wrong DHIS2 reporting data.
What happens after mapping?¶
Once the mapping has been saved, FieldOps can use the DHIS2 organization unit when retrieving reporting data for the site.
The mapped site can then participate in project-level DHIS2 performance monitoring.
This allows FieldOps to determine:
- Whether the site has reported data
- Which indicator values were reported
- Whether indicator values meet project targets
- Whether the site requires monitoring attention
Mapping multiple sites¶
You can map multiple FieldOps sites to their corresponding DHIS2 organization units.
For example:
| FieldOps Site | DHIS2 Organization Unit |
|---|---|
| Nairobi Central Clinic | Nairobi Central Clinic |
| Westlands Health Centre | Westlands Health Centre |
| Kasarani Health Centre | Kasarani Health Centre |
Each mapping establishes the relationship between the operational site in FieldOps and the reporting location in DHIS2.
Multiple DHIS2 connections¶
An organization may use more than one DHIS2 connection.
This can happen when:
- Different countries use separate DHIS2 instances
- Different programs report through different DHIS2 systems
- Partners maintain separate DHIS2 environments
- Development and production environments are separated
- Different projects use different DHIS2 servers
When mapping a site, select the connection that contains the correct DHIS2 organization unit.
Tip
Use descriptive names for DHIS2 connections so users can easily identify the correct DHIS2 source when creating site mappings.
Choosing the correct organization unit¶
DHIS2 organization units are hierarchical.
For example:
Kenya
→ Nairobi County
→ Nairobi Sub-County
→ Nairobi Central Clinic
Select the organization unit that corresponds to the actual reporting location for the FieldOps site.
Do not automatically select a parent organization unit simply because its name is similar to the FieldOps site.
Warning
Mapping a FieldOps site to a county, sub-county, district, or other parent organization unit instead of the actual reporting facility can result in incorrect performance data.
Correcting a mapping¶
If a site was mapped to the wrong DHIS2 organization unit, update the mapping and select the correct organization unit.
Before correcting a mapping, confirm:
- The FieldOps site
- The DHIS2 connection
- The DHIS2 organization unit
- The reporting location represented by that organization unit
This helps prevent reporting data from being associated with the wrong site.
Mapping and project performance¶
Site mapping is required before FieldOps can include a site in DHIS2 project performance monitoring.
For example:
- Nairobi Central Clinic is created as a FieldOps site.
- Nairobi Central Clinic is mapped to its DHIS2 organization unit.
- The site belongs to a project.
- The project is configured to track Immunization Coverage.
- DHIS2 reporting data is synchronized.
- FieldOps retrieves the indicator value for the mapped organization unit.
- FieldOps compares the value with the project's configured target.
- The project performance view shows the result.
This connects the DHIS2 reporting location to the operational project structure in FieldOps.
Sites without a DHIS2 mapping¶
Sites that do not have a DHIS2 mapping cannot provide DHIS2 reporting data to the project.
The project's DHIS2 Performance section can show the number of sites that are mapped and the number of mapped sites that are reporting data.
If a site is expected to report through DHIS2 but is not included in the mapped sites, check its DHIS2 mapping.
Troubleshooting¶
The DHIS2 organization unit is not available¶
Check that:
- The correct DHIS2 connection is selected
- The connection is active
- DHIS2 metadata has been synchronized
- The organization unit exists in the connected DHIS2 instance
- The DHIS2 account has access to the required metadata
If the organization unit was recently created in DHIS2, synchronize metadata again.
The wrong organization unit was selected¶
Review the DHIS2 organization unit hierarchy and confirm that the selected organization unit represents the actual reporting location.
Update the site mapping if necessary.
The site is mapped but has no reporting data¶
A mapping only establishes the relationship between the FieldOps site and the DHIS2 organization unit.
The site may still have no data if:
- The DHIS2 organization unit has not submitted data
- Data for the selected reporting period is unavailable
- The relevant indicator has not been configured for the project
- Reporting data has not yet been synchronized into FieldOps
Review the project's DHIS2 performance and synchronization status.
What to do next¶
After mapping your sites, configure the DHIS2 indicators that each project should track.