Note: This summary was generated and reviewed by the dhis2 docs Ask AI tool and may contain errors. As this is a Wiki post, we encourage you to edit and improve this content with your own expertise, or reply with your questions for discussion!
This summary details the technical specifications, architectural changes, and performance benchmarks released in DHIS2 core version 43 and the Android Capture app version 3.4, alongside the development roadmap presented at the DHIS2 2026 Annual Conference. [What’s New]
1. Core Platform: v43 Performance Infrastructure
DHIS2 has integrated an automated performance testing framework directly into its development release pipeline [What’s New]. This infrastructure simulates routine user workflows under standard loads to systematically measure system responsiveness and prevent regression issues prior to production releases [What’s New].
The diagnostic tooling utilizes Gatling to simulate API traffic, pgbadger for database query log profiling, and async profiler to map CPU and memory resource usage [Performance Testing].
Field Filtering and Import Performance Benchmarks
Database optimizations implemented in core version 43 show the following changes in resource allocation and data throughput during bulk imports:
- Tracker Field Filtering Throughput: Event processing capacity changed from a baseline of 1,540 events per second to 57,366 events per second [Performance Testing].
- CPU Resource Allocation: CPU time consumed exclusively by field filtering dropped from 42% to 0.4% [Performance Testing].
- Change Log Batching: Database round-trip statements during transaction logs were reduced from 787,000 to approximately 6,000, resulting in a 27% reduction in total import duration [Performance Testing].
Database Schema Partition
In core version 43, tracker events and single events are split into separate database tables: trackerevent and singleevent [What’s New].
- Implementation Impact: This structural separation alters SQL queries written directly against the legacy combined event tables, necessitating schema reviews for custom database scripts and external reporting tools [What’s New].
Apache Doris Integration
Core version 43 supports the option to replace the default PostgreSQL analytics backend with Apache Doris, a performant columnar database, specifically to speed up aggregate and individual analytics queries on high-volume datasets without modifying the core application code [What’s New].
2. Platform Roadmap: Mobile and Extensibility
The upcoming roadmap focuses on expanding native mobile capabilities and adding granular sharing configurations [What’s Next].
Android App Plugins and Notifications
- Android Plugin Framework: The roadmap includes the introduction of an Android plugin framework to support custom user interfaces and specialized data entry logic directly inside the mobile app [What’s Next].
- Mobile Notifications: Development is underway to implement push and pull notifications (including native “red badges” on the app icon) to improve local coordination [What’s Next].
- Global Shell Utility: Diagnostic additions planned for the global application shell include a built-in cache cleaner and a user impersonation tool to assist administrators with troubleshooting [What’s Next].
Tracker Object-Level Sharing
The core security framework is being extended to support sharing permissions at the tracked entity instance or event level [What’s Next]. This feature is designed to allow administrators to share individual patient records or single events with designated users, rather than assigning permissions across entire programs [What’s Next].
3. Analytics: The Individual Data Visualizer (IDV)
The Individual Data Visualizer (IDV) consolidates line lists and pivot tables into a unified analytical environment [What’s New].
- Multi-program Queries: The IDV app supports queries across multiple program stages, tracked entity attributes, organizational units, and date ranges within a single report [What’s New].
- Integrated Charting: Visualisation features are being expanded to include charts (bar, line, pie, and single-value indicators) [What’s New].
- Release Cycle: The initial production release of the IDV app, alongside the Bulk Data Entry plugin (for clinical grid data entry), is scheduled for Q3 2026 [Surveillance DAC2026].
4. Developer Tools and AI Integration
DHIS2 has structured core development assets to support the use of AI coding assistants and Large Language Models (LLMs) [What’s New].
- Official AI Skills: Vetted developer “skills” have been published on the NFPX marketplace to guide AI agents to write applications that follow official DHIS2 coding patterns [What’s New].
- Developer Experience Bundles: When generating custom apps with the App Platform, core libraries bundle source code and TypeScript API signatures directly, allowing coding agents to parse and autocomplete backend function calls [What’s New].
- API Hooks: Ongoing development includes advanced webhooks and Model Context Protocol (MCP) integrations to support AI-driven metadata manipulation [What’s Next].
5. Strategic Sustainability: The Shared Service Fee
To fund ongoing core services that are not tied to specific vertical programs—such as data security teams, documentation translation, and performance testing—the HISP Centre has introduced a voluntary Shared Service Fee [Shared Service Fee].
- Fee Structure: The recommended annual contribution is $5,000 per year for public sector production servers in low-income countries [Shared Service Fee].
- Strategic Input: Participating institutions are recognized as “Contributing Partners,” which provides a formalized channel to participate in roadmap prioritization workshops with the core development team [Shared Service Fee].
What to Watch
The technical presentations are available for review on the DHIS2 YouTube channel:
- What’s New in DHIS2: DHIS2 v43 and Android Capture v3.4
- DHIS2 Performance Testing: How to Measure, Contribute, and Benefit
- What’s Next in DHIS2 #dac2026 (Roadmap Session)
- New Features in Context: Epidemiological Surveillance DAC2026
- Shared Service Fee & Technology Partners
Community Call to Action
- The DHIS2 core team is seeking production-like metadata profiles and anonymized user workflow logs to expand the scope of the automated performance testing rig [What’s Next; Performance Testing].
- If you have configurations or feedback regarding the v43 database table split or the IDV app preview, please document them on Jira or share your findings in the thread below.