The tools are a means, not the message
We are platform-literate rather than platform-loyal. These are the platforms, standards and tooling we know deeply and choose from per programme. Our identity is the outcome, not the logo.
How it fits together
A reference architecture, not a product pitch
Every engagement maps onto these layers. Which product fills each layer is decided with the partner, based on what already exists.
Reference architectureData flows up, from the point of service to the decision
- DecisionsWhere the data is usedAnalytics Platforms
- PlatformsWhere data is captured and managedDHIS2Deepest expertiseGeistflowMobile & Web Applications
- ExchangeHow systems talk to each otherOpenHIEAPIs & Integration
- StandardsHow systems agree on meaningHL7 FHIR
Platforms
Where data is captured and managed
DHIS2Open-source platform for collecting, managing, analysing and visualising data, developed at the University of Oslo.Platform2 case studiesGeistflowA platform for building record-keeping applications that are defined rather than programmed, so the same definitions run offline on Android and online in the browser.Platform1 case studyAnalytics PlatformsDashboards and analytics tools that turn programme data into information for decisions.Platform
Our stance
Open source, open standards, institutional ownership
We prefer digital public goods because they outlive projects and procurement cycles. Where we build something new, it is handed over with code, documentation and a trained team, so no partner depends on us to keep the lights on.
Talk about your architecture