---
title: "#dhis2 articles | Hashnode"
description: "Explore 14 articles tagged #dhis2 on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/dhis2"
---

Tag

# #dhis2

14 posts · 0 followers

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Aug 20](https://hashnode.com/posts/gsoc-2026-final-report-building-offline-sync-for-librehealth-neoroo/6a878ed8f496f804d9662862)

### [GSoC 2026 Final Report: Building Offline Sync for LibreHealth NeoRoo](https://devanuragt.hashnode.dev/gsoc-2026-final-report-building-offline-sync-for-librehealth-neoroo?utm_source=hashnode&utm_medium=feed)

For my GSoC project this year, I spent the summer contributing to NeoRoo under LibreHealth. It's an app built for nurses doing Kangaroo Mother Care in NICUs to log baby vitals and send that data to DH

3 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-final-report-building-offline-sync-for-librehealth-neoroo?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Aug 10](https://hashnode.com/posts/gsoc-2026-week-12-fixing-the-last-background-sync-bugs/6a79b78550fcfa150c43929e)

### [GSoC 2026 Week 12: Fixing the last background sync bugs](https://devanuragt.hashnode.dev/gsoc-2026-week-12-fixing-the-last-background-sync-bugs?utm_source=hashnode&utm_medium=feed)

Last week was mostly about fixing bugs. I found two problems: sometimes the app created duplicate records during background sync, and sometimes the background engine crashed. Both only happened someti

1 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-12-fixing-the-last-background-sync-bugs?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Aug 3](https://hashnode.com/posts/gsoc-2026-week-11-background-sync-without-burning-battery/6a701eb75aa9de15d57d56cc)

### [GSoC 2026 Week 11: Background sync without burning battery](https://devanuragt.hashnode.dev/gsoc-2026-week-11-background-sync-without-burning-battery?utm_source=hashnode&utm_medium=feed)

Last week I finished the iOS side of the sync bridge, so Flutter now sees the same behavior on both Android and iOS. This week I moved into background synchronization, which is the part that matters m

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-11-background-sync-without-burning-battery?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Jul 26](https://hashnode.com/posts/gsoc-2026-week-10-ios-sync-is-finally-taking-shape/6a662058dd29d77b000f01ca)

### [GSoC 2026 Week 10: iOS sync is finally taking shape](https://devanuragt.hashnode.dev/gsoc-2026-week-10-ios-sync-is-finally-taking-shape?utm_source=hashnode&utm_medium=feed)

Last week I finished the Sync UI and Conflict Logs screens, so the app now has a much clearer way to show what is happening in the background. This week I started the native iOS sync bridge, which is

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-10-ios-sync-is-finally-taking-shape?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Jul 20](https://hashnode.com/posts/gsoc-2026-week-9-making-sync-visible-in-the-app/6a5e1bf445e682b91ed68e3f)

### [GSoC 2026 Week 9: Making sync visible in the app](https://devanuragt.hashnode.dev/gsoc-2026-week-9-making-sync-visible-in-the-app?utm_source=hashnode&utm_medium=feed)

Last week the backend side moved forward a lot. The server-wins conflict strategy is in place, and anything that cannot be safely merged is preserved in a local conflict\_log so it is not lost. The Syn

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-9-making-sync-visible-in-the-app?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Jul 12](https://hashnode.com/posts/gsoc-2026-week-8-wiring-the-queue-into-the-actual-ui/6a53d50bac1a62f6948a4cd9)

### [GSoC 2026 Week 8: Wiring the queue into the actual UI](https://devanuragt.hashnode.dev/gsoc-2026-week-8-wiring-the-queue-into-the-actual-ui?utm_source=hashnode&utm_medium=feed)

Last week's focus was building the offline sync engine itself, and it came together nicely. The queue is backed by SQLite, retries follow the exponential backoff schedule, and ConnectivityMonitor trig

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-8-wiring-the-queue-into-the-actual-ui?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Jul 5](https://hashnode.com/posts/gsoc-2026-week-7-midterm-done-now-building-the-offline-queue/6a4a5699f92414ae3e714ec0)

### [GSoC 2026 Week 7: Midterm done, now building the offline queue](https://devanuragt.hashnode.dev/gsoc-2026-week-7-midterm-done-now-building-the-offline-queue?utm_source=hashnode&utm_medium=feed)

Last week was a good one. I fixed the release build issues caused by R8 and got the midterm debug and release APK compiling cleanly. That was a relief because reflection-heavy native code can be annoy

3 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-7-midterm-done-now-building-the-offline-queue?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Jun 29](https://hashnode.com/posts/gsoc-2026-week-6-bidirectional-sync-done-midterm-milestone-reached/6a428658d75f0a32a839d2a1)

### [GSoC 2026 Week 6: Bidirectional sync done, midterm milestone reached](https://devanuragt.hashnode.dev/gsoc-2026-week-6-bidirectional-sync-done-midterm-milestone-reached?utm_source=hashnode&utm_medium=feed)

This was a big week and a satisfying one to wrap up. The full bidirectional sync engine is now complete. pullTrackedEntity fetches records from the local d2 database, pushEvent handles clinical events

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-6-bidirectional-sync-done-midterm-milestone-reached?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Jun 21](https://hashnode.com/posts/gsoc-2026-week-5-infant-push-is-done-now-pulling-data-and-mapping-clinical-events/6a383c5a38638395c528fe3a)

### [GSoC 2026 Week 5: Infant push is done — now pulling data and mapping clinical events](https://devanuragt.hashnode.dev/gsoc-2026-week-5-infant-push-is-done-now-pulling-data-and-mapping-clinical-events?utm_source=hashnode&utm_medium=feed)

Week 4 delivered the most satisfying milestone so far. End-to-end infant push is working through the d2 SDK tracker module. All 22 Dart model attributes are being mapped into the DHIS2 tracker payload

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-5-infant-push-is-done-now-pulling-data-and-mapping-clinical-events?utm_source=hashnode&utm_medium=feed)

[Anurag Thakur](https://hashnode.com/@devanuragt) · [Jun 14](https://hashnode.com/posts/gsoc-2026-week-4-from-fragile-string-matching-to-uid-based-sync/6a2ef96d68b4f759d3d6cf8d)

### [GSoC 2026 Week 4: From fragile string matching to UID-based sync](https://devanuragt.hashnode.dev/gsoc-2026-week-4-from-fragile-string-matching-to-uid-based-sync?utm_source=hashnode&utm_medium=feed)

Week 3 went well and actually a bit beyond the plan. Metadata sync is working, org units are cached, and I built a small debug screen to inspect what the d2 SDK is pulling down locally. That debug scr

2 min read · [devanuragt.hashnode.dev](https://devanuragt.hashnode.dev/gsoc-2026-week-4-from-fragile-string-matching-to-uid-based-sync?utm_source=hashnode&utm_medium=feed)
