# ✏️ 2026 CHT Community Meetups Notes

**URL:** <https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490>\
**Category:** Community Calls\
**Created:** [January 13, 2026, 12:35pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490 "2026-01-13T12:35:50Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [January 13, 2026, 12:35pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/1 "2026-01-13T12:35:50Z")

</div>

**Topics Discussed**

**1. Squad updates**

This is the [link](https://github.com/orgs/medic/projects/112/views/24) to access the roadmap, we currently have 5 active squads. Below are the updates from the various working groups:

- **CHT Plugins** - the team has completed the ideation phase and is moving into the technical design stage. They are working towards an MVP that will allow one to add custom in-app tabs which will show static or dynamic content, work offline and interact with CHT data models.
- **Hosting TCO reduction V2** - the group is exploring reducing spaces required for upgrades by splitting large ddocs and making changes to the upgrade process to allow more control of what is reindexed.
- **CHT multi-agent system** - a hierarchial multiagent system has been built which has multiple agents that covers research, QA and development and works together to automate the workflows and improve the CHT development process. The [\* MCP server](https://mcp-docs.dev.medicmobile.org/mcp) has been set up using kapa.ai. Please reply to this [\* forum post](https://forum.communityhealthtoolkit.org/t/creation-of-cht-agent-multi-agent-squad/5488) if you would to be involved in this work
- **Task prioritization** - the overdue task bubble functionality has been built and will be released in v5.1.0
- **Display of previous month targets** - the team is finalizing two remaining tasks and this improvement is likely to be available in the next CHT release.

**2. Community priorities overview.**

This is the list of priorities that have been raised by the community:

- Ability to pause on a form
- Client and task visibility across catchment areas
- Support for uploading attachments in contact forms
- option to hide target goal past the goal
- Offline synchronization support.
- Task filter

The community is exploring ways to organize and list these priorities to make it easier to track, discuss and act on them collectively.

[Slides](https://docs.google.com/presentation/d/1pDgb-LS45KJIg_ZmM5LDlLrRS7YiGWLsnXo6pBbVdyk/edit?slide=id.g2ba59de7fa7_0_0#slide=id.g2ba59de7fa7_0_0)

---

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [February 17, 2026, 5:16pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/2 "2026-02-17T17:16:18Z")

</div>

**Topics discussed during the Feb 10 Meetup**

**1.Massive Online Open Validation Evaluation (MOOVE) Initiative**

- This intervention is being implemented in Kenya by Strathmore University, Kenyatta National Hospital and the University of Nairobi and it aims to evaluate the performance of large language models (LLMs) in supporting clinical decision support by comparing their outputs to local clinical guidelines assessing their usability in primary care settings
- The study has 3 phases  
**hypMOOVE**
  - in this stage, the accuracy of LLMs is evaluated using clinical scenarios without patients involvement
  - LLMs outputs are reviewed retrospectively by Expert Clinicians  
**SilentMOOVE**
  - De-identified data will be captured during routine patient visits. Clinicians will review the LLMs outputs after patient encounter and provide feedback

- The Implementation will take place in 3 counties in Kenya (Kajiado, Nairobi and Migori)

**2. Squad updates**

- Display of previous month targets - the team is finalizing this feature and it will be available in CHT v5.1.
- [Task filters](https://github.com/medic/cht-core/issues/10577) have been added to CHT which will enable users to filter tasks based on due date, task type and place (for users who manage many places). These changes will be available in the next CHT release.

[Slides.](https://docs.google.com/presentation/d/1KFhkK75YkfMxLI3qRUhuqne3i3nrooeCOYDPlkbve8k/edit?slide=id.g3c6943cdffc_0_1658#slide=id.g3c6943cdffc_0_1658)

---

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [March 17, 2026, 8:21pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/3 "2026-03-17T20:21:26Z")

</div>

The focus of our March 2026 Community Meetup discussion was the CHT hosting total cost of ownership and the ongoing initiatives aimed at reducing the hosting costs.

**Why does this matter?** Disk space is the main cost driver, as CouchDB creates massive index files which consume disk space far beyond the actual data stored. For some projects, the disk costs are significant which might pose a challenge to the long term sustainability of the projects.

**TCO phase 1 - What was achieved?**  
CouchDB Nouveau was introduced to replace the existing CouchDB search which has enabled disk savings in the excess of 30% for large instances. These improvements were released in v5.0. For partners who plan to upgrade, there are a few important considerations, including:

- You will need 3-5 times disk space during the upgrade.
- Kubernetes deployments need additional manual steps.

Early 5.0 upgrades for production CHT deployments have delivered 5- 25 % disk savings, depending on the instance size.

**[The TCO V2:](https://github.com/medic/cht-core/issues/10092) What’s next**  
TCO phase 2 aims to split views into separate design documents, which would ensure faster upgrades and further reduce the disk space needed for the upgrade.

**How to get involved** : we encourage you to join the weekly **TCO V2 community squad calls** held **every Tuesday from 3:15 - 4:15 pm GMT** to contribute and share your perspectives. [Meeting link](http://meet.google.com/mzp-kimg-zzs).

[Slides](https://docs.google.com/presentation/d/1TRJA68y60mmlueM0GGpANufY4foOWhHqcvg-PDJu1Ec/edit?slide=id.g2ba59de7fa7_0_0#slide=id.g2ba59de7fa7_0_0)

---

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [April 23, 2026, 5:32pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/4 "2026-04-23T17:32:11Z")

</div>

**April Community Meetup summarized notes.**

**Capturing GPS Data in CHT**  
GPS data is captured automatically in CHT reports, with every form edit storing an additional location entry. To enable geolocation capture, users must grant location permission to the Android app. If permission is denied twice, users are directed to device settings to manually enable it.

In addition to automatic capture, a number of projects use the map widget which is embedded directly into forms as a more deliberate and structured way of collecting geolocation data.

**Analysis of GPS submissions.**  
A review of geolocation data across various CHT projects from multiple geographies revealed a GPS capture success rate ranging from 30% to 70%. The primary driver of failures was geo timeouts, with additional cases attributed to users not having granted location permission.

Other challenges shared by deployments included low GPS accuracy in remote and rural areas and instances where users turned off location services to conserve battery life.

**Using GPS data to deliver responsive care.**  
Several projects are already leveraging geolocation insights to strengthen community health service delivery. Notable examples include the [use of geospatial data to optimize health service delivery in Uganda](https://forum.communityhealthtoolkit.org/t/utilization-of-geospatial-data-to-strengthen-health-service-delivery-a-case-of-using-echis-uganda-data/3974) and the Datharm team’s work using GPS data to deliver targeted routine immunisation services across three states in Nigeria.

**Ongoing GPS tracking enhancements and route Optimization.**  
The CHT community is actively working on a set of GPS tracking enhancements, including [storing geolocation data when submitting contact forms](https://github.com/medic/cht-core/issues/10676) and [GPS timeout fix](https://github.com/medic/cht-core/issues/10679). These improvements will lay the foundation for [smart route optimization capabilities work](https://github.com/orgs/medic/projects/112/views/4?pane=issue&itemId=157499723&issue=medic%7Ccht-roadmap%7C191) that one of our community squads is currently driving forward.

Want to contribute to this work? Join us [here](http://meet.google.com/ipi-anmo-zrg) every Wednesday at 1:00 pm GMT to learn more and get involved.

[Meetup slides](https://docs.google.com/presentation/d/1ZMJP2iBDy_qJveOw-F6jlzzUJra9mDqfPPxGc14rT4g/edit?slide=id.g2ba59de7fa7_0_0#slide=id.g2ba59de7fa7_0_0).

---

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [May 13, 2026, 12:13pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/5 "2026-05-13T12:13:22Z")

</div>

Thank you for your participation and thoughtful contributions at yesterday’s Meetup. Below are the highlights from the session.

**Community Squads Overview**  
Community squads are working groups formed to design and build specific CHT features. We currently have 2 squads in the emerging phase and 5 active squads in progress. See the [Roadmap](https://github.com/orgs/medic/projects/112/views/4) for full details.

**Latest squad product development updates**.  
**CHT Multi-Agent Squad**  
The research layer is now complete, the group is finalising work on the OpenDeepWiki MCP Server; commands are already available to support code-calling agents for indexing.

**UI Extensions**  
A live demo done during the session showcased how the newly built UI extension framework supports incorporating an additional tab to CHT. The team is now working on updates to ensure compatibility across both the legacy and new UI. This feature is expected to ship within the next few weeks.

**Hosting TCO reduction squad**  
The approach of splitting docs to reduce the 5x disk space required during upgrades has been deferred. The team is now focused on removing the largest redundant views, logging failed replications from misconfigured users and archiving data that is no longer needed.

**CHT Learning Resources Revamp.**  
The squad is actively gathering feedback on the CHT learning journey. Please take a few minutes to complete [this survey](https://docs.google.com/forms/d/e/1FAIpQLScuFK4nBCwzW7rjtjrz48P_9NWUlTnHlPjGKHwEnbTOZl3EUA/viewform), your input will directly shape the improvements the community prioritizes.

**Smart Task Prioritisation & GPS Tracking squad**  
The working group is currently working on the following improvements:

- Interaction tracking metrics which will capture how users engage with the task page to help measure the impact of task changes.
- The[free text functionality](https://github.com/medic/cht-core/issues/10694) in task page will enable CHWs to search for patient and household names directly from the task list
- Other GPS enhancements include designing an intuitive UI workflow for reliable GPS data capture, adding visual cues to confirm GPS has been captured and fixing the [timeout bug](https://github.com/medic/cht-core/issues/10679).

You can access the Meetup slides [here](https://docs.google.com/presentation/d/17MevHgLF4QAbyRGm4teaOmXE2BiGp7ZH5hgOfj7308w/edit?slide=id.g2ba59de7fa7_0_0#slide=id.g2ba59de7fa7_0_0). 🙏

---

<div class="post-metadata">

**Author:** ![mrjones](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/mrjones/32/681_2.png) [@mrjones](https://forum.communityhealthtoolkit.org/u/mrjones)\
**Post date:** [June 9, 2026, 10:19pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/6 "2026-06-09T22:19:21Z")

</div>

Thanks for attending the June Meetup call! While it was an smaller call than usual, we’re always happy to help out whoever attends.

**Two new squads**

We covered the [Peer 2 Peer](https://github.com/medic/cht-roadmap/issues/196) squad which is looking to implement fully offline synchronization between two users of the CHT. The primary use case is coming out of West Africa where a supervisor would meet up with a CHW in a rural setting. The CHW would synchronize their data to the supervisor over an ad hoc WiFi network, a feature built into all Android devices. Some time later, the Supervisor would be able to synchronize the CHW’s data when the supervisor has connectivity.

We also reviewed the just started [No Code CHT Configuration squad](https://github.com/medic/cht-roadmap/issues/193). This squad looks to remove the requirement to be an app developer when a CHT user wants to create a new workflow.

**Review Existing Squads**

We reviewed the [entire squad list](https://github.com/orgs/medic/projects/112/views/24) and listed out the active ones:

- No Code CHT Configuration
- Peer 2 Peer Synchronization Support
- CHT Learning Resources Revamp
- GPS Tracking Enhancements & Route Optimization
- Smart Task Prioritization
- Hosting TCO (Total Cost of Ownership): Upgrades
- Hosting TCO (Total Cost of Ownership): Optimize indexes
- Hosting TCO (Total Cost of Ownership): Archiving
- CHT Hierarchical Multi-Agent System

**Hosting Cost Calculator**

We recently updated our online [Hosting Cost Calculator](https://forum.communityhealthtoolkit.org/t/launch-of-interactive-cht-hosting-cost-calculator/5618), and did a demo of what these changes are and why we made them - to be more reflective of real world hosting costs. [Check it out today](https://docs.communityhealthtoolkit.org/hosting/cht/costs/)!

All of our squads are open to any one who is reading this - we [encourage you to participate](https://docs.communityhealthtoolkit.org/community/squads/) to shape the CHT to be what will be the most helpful for you deployment.

---

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [July 17, 2026, 2:08pm UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/7 "2026-07-17T14:08:08Z")

</div>

Thank you for participating in our July Meetup! 🎉

Here are some highlights from the presentations:

**1. CHW sync visibility for supervisors**  
@Romuald_Dansou led a discussion on recent improvements that allow supervisors to view CHW sync data within the supervisor app.

During a recent field visit, the team observed that supervisors weren’t aware of which CHWs had synced and which hadn’t, this prevented them from providing timely support and accessing performance data. To close this gap, the team has built enhancements that allows supervisors to view each CHW’s last sync date and specific performance-based areas for improvement, directly on the CHW profile.

This implementation uses a scheduled OpenFn workflow that runs each weekend, reading telemetry data from CHT and generating a report showing last sync dates. To help improve the users’ experience, the team is now exploring adding sync details directly to the CHW list and leveraging UI Extension functionality to build custom pages and components within CHT to display sync data.

**2. Community priorities discussed.**

- **Peer-to-peer syncing (P2P)** - this feature will enable CHWs to sync data to supervisors without an internet connection; the squad is exploring various approaches for data transfer
- **Archiving feature** , with this functionality; it will be possible to move outdated data to cold storage to improve performance, especially for projects with large datasets
- **[UHC mode improvements](https://github.com/medic/cht-core/issues/10692)** will add household filters based on collected data

The P2P and archiving work is already in progress.

**3. CHT Roadmap**  
We reviewed the[current roadmap](https://github.com/orgs/medic/projects/112/views/4). The active squads include:

1. No-Code CHT Configuration Squad
2. Peer-to-Peer Syncing
3. CHT Learning Resources Revamp
4. Multi-Agency Squad
5. GPS Tracking Enhancements Squad
6. Total Cost of Ownership

The above community working groups are open to everyone, please feel free to join them to contribute.

---

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [August 25, 2026, 6:37am UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/8 "2026-08-25T06:37:12Z")

</div>

Thank you to everyone who joined the **August CHT Community Meetup**! Below is a summary of the key updates and discussions from the session.  
**1. Squad updates**  
**a) CHT multi-agent system**  
The Multi-Agent System community team is developing an AI-assisted system to support CHT development, troubleshooting and bug fixing.  
The system uses a layered architecture with supervised checkpoints across multiple phases:

- Research layer: researches and retrieves relevant CHT documentation.
- Development layer: generates code and tests to address identified issues and needs
- QA Supervisor: validates the generated code and tests.

During the Meetup, @hareet showcased how the system could identify and fix a pregnancy workflow bug. The Research Supervisor can triage a reported CHT issue, query the MCP server, and generate a fully grounded GitHub issue then the multi-agent systems is able to proceed to build a fix and test it.

The beta version is now ready, it supports different AI models and can run offline.

**b) Total cost of ownership reduction work**  
The group has continued to explore ways to reduce CHT hosting cost and improve CHT performance.  
Recent and ongoing improvements include:

- Replication logs for large users, released in CHT v5.2.
- Archiving and index optimizations, which are expected to reduce disk-space requirements and improve synchronization times for CHWs.

**c) Smart task prioritization.**  
The enhancement to support geolocation capture in contact forms is ready and will be included in the next CHT release.  
The [Smart Task Prioritization – Phase 2](https://forum.communityhealthtoolkit.org/t/smart-task-prioritization-v1/5718) has also kicked off. If you are interested in contributing, please consider joining the squad weekly meeting every Wednesday at 1pm GMT.

**d) CHT Resources Revamp**  
The squad is working on improving the [CHT Demo App](https://demo-cht.dev.medicmobile.org/) experience by adding an ICCM use case, making it easier for users to explore CHT capabilities through a practical ICCM implementation.

**2. Improving contributor experience**  
The community has been working on PR process improvements to provide contributors with automated, early feedback when they submit a pull request.

The new GitHub actions will help guide contributors by automatically checking whether:

- The PR follows the required template.
- The PR is linked to an existing issue.
- The PR is assigned to the author.

These checks should make the contribution process smoother and help contributors address common issues earlier in the review process.

🙏

---

<div class="post-metadata">

**Author:** ![antony](https://communityhealthtoolkit.b-cdn.net/user_avatar/forum.communityhealthtoolkit.org/antony/32/69_2.png) [@antony](https://forum.communityhealthtoolkit.org/u/antony)\
**Post date:** [October 5, 2026, 5:43am UTC](https://forum.communityhealthtoolkit.org/t/2026-cht-community-meetups-notes/5490/9 "2026-10-05T05:43:01Z")

</div>

Thank you to everyone who joined our **September Community Meetup**! 🙌  
Below are the key highlights from what was presented and discussed.

**Contact Summary & Task Mapping Proof of Concept**  
The Smart Task Prioritization Squad is exploring how offline maps can help CHWs better plan and prioritize their work in the field.  
During the Meetup, the team demoed the latest proof of concept, which introduces:

- **Household locations on the contact summary:** a new map field allows CHWs to view a household’s location based on GPS data captured through contact forms.
- **Tasks on an in-app map:** tasks can now be visualized on the map, with markers showing the task name, patient name and distance from the CHW’s current location.
- **Quick task access:** selecting a task marker opens the task directly, making it easier for CHWs to move from the map to the required action.
- **Search and sidebar support:** existing search and sidebar functionality are also available within the task-mapping experience.
- **Offline-first mapping:** the proof of concept uses offline OpenStreetMap vector files, enabling map functionality even when connectivity is limited.

**Community priorities**  
We also discussed other priorities raised by the CHT community, including the ability to move contacts between catchment areas. This would support continuity of care when household members move from one area or region to another ensuring their information can follow them and remain accessible to the appropriate CHW. This is a [recurring need](https://github.com/medic/cht-core/issues/7736) raised by the community, we will continue exploring how it could be supported in CHT.
