Integrations Overview¶
Connect external data platforms to FieldOps and bring data into your operational workflows.
FieldOps currently supports integrations with KoboToolbox, ODK Central, and DHIS2.
Each integration has its own workflow and documentation covering what you can accomplish, how to connect the platform, how to configure it, and how to troubleshoot common problems.
Choose the platform your organization uses to get started.
-
KoboToolbox
Bring KoboToolbox form submissions into FieldOps and connect them to your Programmes, Projects, Sites, and Monitoring Templates.
-
ODK Central
Connect ODK Central, map forms to your FieldOps operational structure, and synchronize submission data into FieldOps.
-
DHIS2
Connect DHIS2, synchronize reporting data, map organization units to FieldOps sites, configure project indicators and targets, and monitor performance through FieldOps.
How integrations work¶
Each integration connects FieldOps to an external system that your organization already uses for data collection or reporting.
The configuration process depends on the platform.
Data collection integrations¶
KoboToolbox and ODK Central are primarily used for collecting field data through forms.
The general workflow is:
- Create a connection.
- Test the connection.
- Select or map an external form.
- Associate the form with the appropriate FieldOps Programme, Project, Site, and Monitoring Template where applicable.
- Synchronize submissions into FieldOps.
- Use the synchronized data within FieldOps workflows.
DHIS2 integration¶
DHIS2 is primarily used for reporting and indicator data.
The general workflow is:
- Create a DHIS2 connection.
- Test the connection.
- Synchronize DHIS2 metadata.
- Map DHIS2 organization units to FieldOps sites.
- Configure the DHIS2 indicators tracked by a project.
- Configure project-specific targets and target directions.
- Synchronize DHIS2 reporting data.
- Review project performance.
- Identify sites or indicators requiring attention.
- Record findings and create follow-up actions where required.
DHIS2 therefore provides the reporting data while FieldOps provides the project-level monitoring, findings, follow-up, and accountability workflow.
Create a connection¶
A connection allows FieldOps to communicate with the external platform.
Depending on the integration, you may provide details such as:
- Server or Base URL
- Account credentials
- API token or personal access token
- Project information
- Connection-specific authentication details
You can use Test Connection to confirm that FieldOps can successfully communicate with the external platform.
Note
Authentication requirements differ between integrations. Follow the documentation for the specific platform you are connecting.
Configure the integration¶
After creating a connection, configure how the external data relates to your FieldOps operational structure.
For KoboToolbox and ODK Central, this primarily involves mapping an external form to the appropriate:
- Programme
- Project
- Site
- Monitoring Template, where applicable
For DHIS2, configuration involves:
- Synchronizing DHIS2 metadata
- Mapping DHIS2 organization units to FieldOps sites
- Selecting the DHIS2 indicators tracked by a project
- Configuring project-specific targets
- Configuring target direction
The configuration ensures that synchronized external data can be interpreted within the appropriate FieldOps project and site context.
Synchronizing data¶
After an integration has been configured, FieldOps can synchronize data from the connected platform.
For KoboToolbox and ODK Central, synchronization brings external form submissions into FieldOps.
For DHIS2, synchronization brings reporting and indicator data into FieldOps so that project teams can review performance.
Where available, you can use Sync Now to request an immediate synchronization.
Note
Automatic synchronization runs periodically. Use Sync Now when you want to request synchronization immediately.
What integrations add to FieldOps¶
Integrations allow FieldOps to work with systems that organizations already use for field data collection and reporting.
Instead of requiring teams to replace their existing platforms, FieldOps adds an operational layer around the data.
KoboToolbox and ODK Central¶
External form submissions
↓
FieldOps
Monitoring workflows, visits, evidence, review, findings, and follow-up
DHIS2¶
Reporting and indicator data
↓
FieldOps
Project performance, targets, findings, follow-up actions, and accountability