Skip to content

What is iCapture v3

iCapture v3 is a modern, reusable data-capture application for DHIS2. It provides standard entry forms for datasets, event programs, and tracker programs, while giving implementation teams a clear way to extend the application for country-, programme-, and workflow-specific requirements.

Initially developed in mid-2025, iCapture v3 was created to address the limitations of earlier iCapture versions: outdated technology, difficult maintenance, limited support for newer DHIS2 deployments, weak release traceability, and limited collaboration between projects. It targets DHIS2 instances version 2.40 and later.

Why iCapture v3

DHIS2 implementations frequently need more than the default data-entry experience. Projects may require customised dataset and event forms, cross-program tracker workflows, reporting tools, local validation, localisation, or other implementation-specific behaviour. Delivering each requirement as a separate application creates duplicated effort and makes long-term maintenance harder.

Earlier iCapture versions supported datasets, events, and later tracker programs across many HISP Vietnam–Mekong projects. As DHIS2 and implementation requirements evolved, those versions became increasingly difficult to extend, maintain, version, and share with collaborating teams. iCapture v3 was created to provide a more sustainable foundation.

Challenges addressed by iCapture v3

Challenge in earlier implementations Why it matters iCapture v3 response
Older technology and limited compatibility with newer DHIS2 projects New implementations need a current, maintainable baseline. Uses newer libraries and targets DHIS2 version 2.40 and later.
Complex requirements were difficult to deliver Projects may need cross-program tracker workflows, complex forms, report downloads, or specialised validation. Keeps a reusable core while allowing each project to add its own extension.
Changes and deployed versions were hard to trace Teams need to know which features and fixes are included in a deployment. Uses semantic versioning and release changelogs.
No safe, clearly managed rollback path A failed release should not block restoration of a stable application. Supports release-based rollback to a previous stable version.
Core code and project configuration were mixed together A change for one project could affect another, and project configuration was exposed across teams. Separates the shared core from implementation-owned project extensions.
Collaboration was difficult Country teams and partners could not easily own or contribute to their implementations. Lets collaborators fork, manage, and version their own extension repositories, with core support from HISP Vietnam–Mekong.

A reusable foundation, without a one-size-fits-all application

iCapture v3 is designed to balance consistency and flexibility. The core application provides standard data-entry capabilities for datasets, events, and trackers. A project extension then adds the forms, workflows, configuration, and branding required by a particular implementation.

This avoids rebuilding common capabilities from scratch while allowing country teams and implementing partners to retain ownership of their local requirements.

Vendor independence and local ownership

iCapture v3 is designed to reduce dependence on a single implementation partner. A country team or implementing partner should be able to understand, maintain, and evolve its own implementation rather than treating the application as a black box.

The core-and-extension model supports this goal in practice:

  • Independent project ownership: a project extension can be maintained in its own repository by the country team or implementing partner.
  • Separation of concerns: project-specific source code and configuration are isolated from the reusable core and from other projects.
  • Transparent releases: semantic versions and changelogs make it possible to review what has changed in each release.
  • Operational continuity: a documented release history and rollback path help teams restore a stable version when a new release has an issue.
  • Maintainable handover: implementation, deployment, and configuration documentation provide a foundation for local maintenance and support.

HISP Vietnam–Mekong can support the core application and collaborating implementations without becoming the sole owner of every country deployment.

Software architecture alone does not remove vendor lock-in. The model depends on accessible repositories, clear ownership and governance, documented deployment procedures, transparent releases, and ongoing capacity building for local teams.

Benefits for implementation teams

  • Implementation teams can deliver tailored workflows without starting from an empty application.
  • Country teams and partners can own their extension repository and release cycle.
  • Developers work with a clearer separation between shared and project-specific code, with more traceable releases.
  • End users benefit from improved performance and user experience, with localisation support and a roadmap for offline and mobile use.

Current use cases

iCapture v3 is intended for DHIS2 implementations that need both standard data capture and tailored workflows. Current examples include:

  • Lao tracker implementation with maternal and child health programs and community health registers.
  • Cambodia HMIS implementation with highly customised dataset and event forms, dataset-report download, and event-completeness features.
  • Vietnam NCD implementation as a single data-capture application for aggregate, event, and tracker workflows.