External platform pushing aggregate indicators to DHIS2 - > looking for technical guidance or developer contact

Implementation - Implémentation Interoperability
1

Title: External platform pushing aggregate indicators to DHIS2 — looking for technical guidance or developer contact

Hi community,

We’re integrating Kinala, a maternal health implementation platform (pilots in Nigeria and Kenya), with DHIS2 for aggregate reporting. Our dev team is building now and we want to make sure we’re on the right path before we go too far.

Our current approach:

  • Pushing aggregate indicators (PPH event counts, bundle initiation counts, execution trends) via /api/dataValueSets
  • Aggregate only — no Tracker or Event APIs, no patient-level data
  • Validating against a Dev/Test instance first

Two things would help us most right now:

  1. Is /api/dataValueSets the right API for this use case, or is there a better path for an external platform pushing periodic aggregate indicators?
  2. Can anyone point us to a developer or technical contact open to a short call to sanity-check our architecture before we go further?

Happy to share more detail on our setup. Thanks in advance.

Axel
Kinala

1 Like
2

Hi @Gassim, I thought I’d tag you here as this seems like it might be up your alley.

1 Like
3

@Gassim any guidance here?

1 Like
4

Hello @Axel,

I do have a bit of experience working with aggregate integration. You do have the right API and setup.

I could spare a few minutes to share my experience or check your implementation if you would like.

Regards.

1 Like
5

@nnkogift Thank you so much for engaging in this post. I’ll be in touch shortly.

I’ll welcome anyone else guidance

1 Like
6

Hi @Axel

Sorry I missed this post early during the month! I’m glad @nnkogift offered to look into your setup, thanks Gift for that and for the tag.

You are indeed in the right direction - technically, using the /api/dataValueSets should be the one to work for this scenario; furthermore, there might be other things to consider:

  • How’s the metadata configured?
    • Are the period types the same on both platforms? fixed periods format? (and if there are any relative periods then they won’t work with this specific api: Using relative period types with DHIS2 API)..
    • Organization Units are setup properly?
    • Metadata assignments (Data elements → datasets, datasets → OUs) are ready? and whether or not you will need to use category combinations?
  • Next point is about the Data Analytics, what do you want to see in your charts, maps, and dashboards? I mean to make sure the input will provide the expected output.
    • One thing to remember is that after pushing the data to dhis2, the analytics tables export needs to be run (either as a scheduled job via the Schedular app, or manually via the Data Administration app).

@nnkogift has a solid background on this.. and glad he’s already started with the help. :folded_hands:

Thank you!

7

Hi @Axel , yes, for aggregate data that is the correct endpoint. I would strongly encourage you to (if you can) to use version 43. We have completely rewritten that endpoint from the ground up, and it offers much better performance than earlier versions. Good luck and if you have questions you know where to find us.

Best regards,
Jason

1 Like