DHIS2 Integration

A built-in DHIS2 integration is not available today on any plan. OpenBoxes Lift does not push stock or consumption data to DHIS2, and it cannot import DHIS2 data-value exports.

Why DHIS2 exports cannot be imported#

DHIS2 aggregate data-value exports are per-period summary counts (opening balance, received, distributed, closing balance) keyed by DHIS2 UIDs. They contain no item-level stock — no lots, no expiry dates, no individual movements — and OpenBoxes computes stock from transactions, so summary counts have nothing to attach to. The import wizard recognizes these files and explains this rather than guessing at a mapping.

What to do instead#

  1. Export item-level data from the system that feeds DHIS2. DHIS2 is usually the reporting layer; the facility's stock cards, an eLMIS such as OpenLMIS, or paper registers hold the item-level truth. Those import fine, including as transaction history.
  2. Use the spreadsheet path for stock cards kept in Excel — the importer recognizes movement sheets (date / type / product / quantity).
  3. Build your own reporting feed with the OpenBoxes API: read stock-on-hand and stock movements on a schedule and submit aggregate values to your DHIS2 instance's Web API from your own script or an integration platform such as OpenFn or n8n. See Custom Integrations.

If a native DHIS2 integration matters to your organization, tell us at sales@openboxes.cloud — custom integration work is not part of any plan today, and we will say honestly whether we can help, and knowing real demand helps us prioritize the roadmap. For help with an import, contact support.