1. From the field to the report
Data captured on a phone in the field, offline if needed, arrives in the same system managers report from. No re-typing, no email attachments, no second spreadsheet.
On screen: our design, with invented sample data.
2. What we connect to
Common tools, not partnerships or endorsements
KoboToolbox, ODK
Survey and field tools
Submissions pulled on a schedule through the tools' own interfaces, using your project's credentials.
DHIS2, eHMIS
National reporting
Reports shaped to national formats, and automated exchange where your facility or programme is authorised to connect. We never assume or imply access.
HL7 FHIR
Health data standards
Structured exchange with other clinical systems where a project requires it.
Mobile money, bank references
Payments
Payment references reconciled against records. Direct collection depends on an agreement with the provider.
SMS, email, WhatsApp
Messaging
Reminders and alerts sent through providers you have an account with.
Excel, CSV, databases
Files and existing data
Imports during migration, scheduled exports, and connections to databases you already run.
3. Authorised, tested and written down
How we do it
- 01
Map the flow
Which data moves, in which direction, how often, and who owns it.
- 02
Agree access
Credentials and permissions come from the owner of each system, in writing.
- 03
Build and test
The link is built against test data first, with failures logged and visible.
- 04
Document and hand over
Every connection is written down so it can be maintained later.
What we will not do
Connect to any system without its owner's permission, copy data by scraping screens, or keep credentials anywhere but secure server configuration.
Have systems that should talk to each other?
List what you use today and what should move between them. We will tell you what is realistic.
Discuss integration