C4GT - DMP 2026 Introductions

sugat · January 31, 2026, 10:00pm

Hey All! Welcome!
Post your introductions and questions/queries related to C4GT and DMP 2026 in this thread.
Thank you!

Gm_Aravind · March 14, 2026, 12:43pm

Hello everyone,

My name is Aravind, a final-year Computer Science student from India. I recently joined the Community Health Toolkit community. I am excited to learn more about the project and start contributing. I also watched a few YouTube videos of how this helps people, Community health workers.

I am currently exploring the CHT codebase while preparing for C4GT 2026. I noticed the recent DMP issues around Bikram Sambat support and advanced contact management APIs and they look very interesting.

I just started reading the documentation and exploring the repository to understand the architecture. If anyone has suggestions on good starting points in the codebase, I would really appreciate it.

Looking forward to learning from the community and contributing.

jkuester · March 16, 2026, 5:15pm

Hello @Gm_Aravind and welcome! The best place to start is our first time contributors guide. If you want to jump in and make a contribution, have a look at some of our Good First Issues! If one of those sounds interesting to you, just drop a comment on it and we will assign it to you.

sookwalinga · March 17, 2026, 11:14am

Welcome to the community @Gm_Aravind! You might also find it helpful to explore this course for a solid overview of configuring CHT applications. You can also subscribe to the CHT Event Calendar, it’s a great way to stay informed, learn, and connect with others.

In particular, the CHT Dev Hour is worth joining. It’s an open session where you can ask just about any CHT-related question and get real-time support from core maintainers and experienced contributors.

Gm_Aravind · March 18, 2026, 4:02am

Thanks a lot for the guidance, @jkuester. I will go through the first time contributors guide and start exploring the good first issues**.**

Looking forward to getting started and contributing.

Gm_Aravind · March 18, 2026, 4:07am

Thanks a lot for the guidance, @sookwalinga! I will go through the course and quickly check out the Calendar as well.

The Dev Hour also sounds really helpful as a new contributor. I will try to join one of the sessions soon.

Looking forward to learning and contributing.

vikrantwiz02 · March 25, 2026, 1:14pm

Hello everyone,

My name is Vikrant Kumar, and I am a 3rd-year B.Tech student at IIITDM Jabalpur. I am introducing myself as a first-time contributor to the CHT community as part of my preparation for C4GT 2026.

To familiarize myself with the project’s codebase and development workflow, I have started by addressing a few infrastructure and configuration issues. My current active PRs include:

PR #10756: Duplicate phone number validation broken when using “”
PR #10757: Updating staging environment URLs to maintain consistency across services.
PR #10758: Configuring NODE_ENV in the Docker stack to ensure secure cookie handling by default.

Technical Background: Outside of CHT, I serve as a lead developer for the Fusion ERP project at my university. My core experience lies in full-stack development using Django and React.

I am eager to learn from the core team and contribute more extensively as the C4GT program progresses. If there are specific high-priority areas or issues suited for a new contributor with my background, I would welcome your guidance.

Best regards,

Vikrant Kumar

Github: vikrantwiz02

Megha · March 26, 2026, 6:31am

Hi everyone

I’m Megha, a BTech student interested in contributing to the Community Health Toolkit and applying for C4GT 2026.

I’ve set up the project locally and have been actively contributing. Recently, I worked on telemetry-related changes and submitted the following PRs:

Implementation PR: https://github.com/medic/cht-core/pull/10728
Documentation PR: https://github.com/medic/cht-docs/pull/2166

Additionally, I’ve contributed a couple more PRs:

I’m currently exploring the codebase further and would love some guidance on:

beginner-friendly issues to work on
how to better prepare for C4GT

I’d really appreciate any suggestions or advice from the community.

Also tagging for visibility on the related work.

Thanks!

yuv · March 27, 2026, 12:12pm

HI @Megha , welcome to the CHT Community. It’s great to see you already contributing to CHT. You can find beginner friendly issues labeled good first issue. You can search with same tag on our other repos like cht-android, cht-conf, and many more. Our documentation site has great resources on each of these tools.

You can also subscribe to CHT Event calendar and join us in upcoming CHT events virtually.

yuv · March 27, 2026, 12:13pm

Hi @vikrantwiz02 , welcome to the CHT Community. It’s great to see you already contributing to CHT. You can find beginner friendly issues labeled good first issue. You can search with same tag on our other repos like cht-android, cht-conf, and many more. Our documentation site has great resources on each of these tools.

You can also subscribe to CHT Event calendar and join us in upcoming CHT events virtually.

santhosh-7777 · April 14, 2026, 3:57am

Hi everyone,
I’m Santhosh Teja Piridi, a CSE student from India and a contributor to the Community Health Toolkit. I’ve started contributing to CHT and recently opened PRs including medic/cht-core#10849 (improving error handling) and medic/cht-conf#806 (improving local-ip handling). I’m currently preparing for C4GT 2026 and exploring the codebase by working on smaller issues. I’ve also started looking into DMP 2026 projects like Bikram Sambat support and advanced contact management APIs, which seem really interesting. I’d appreciate guidance on what to work on next and how to align better for C4GT. Thanks!

Ved-Patel · April 23, 2026, 10:24am

Hey everyone!

I’m Ved, a second year CSE undergrad from India! I love contributing to open source, and found CHT from an Open source programme C4GT!

I was working on extensions in cht-conf so far!

As I was not able to contribute a lot (in CHT, I’ve many other open source contributions in different orgs though), but I’m genuinely interested in contributing to CHT through C4GT!

Please anyone from the team guide me over the Proposal review process, how can I make a winning proposal and get accepted as I don’t have many significant contributions till date, am I needed to contribute more or write a more detailed proposal?

Appreciate any responses/suggestions regarding the same!

Thanks in advance

jkuester · April 24, 2026, 3:17pm

@Ved-Patel welcome to the CHT community! Thank you for the contributions you have made and your interest in contributing further!

I do not have a lot of info regarding the details of how proposals are submitted/processed on the C4GT side. But, here is what I can share from the Medic perspective.

This year we are supporting two DMP projects:

github.com/medic/cht-core

[DMP 2026]: Enhance Bikram Sambat support in CHT

opened 04:36PM - 10 Mar 26 UTC

sugat009

DMP 2026

## Ticket Contents The CHT has basic [Bikram Sambat (BS) calendar support](http…s://docs.communityhealthtoolkit.org/bikram-sambat/) used in [app forms](https://docs.communityhealthtoolkit.org/apps/reference/forms/app/#bikram-sambat-datepicker), but several quality-of-life issues make it incomplete for users in Nepal and other regions using this calendar system. The current date picker is minimal (no calendar view, no month navigation), the Reports tab filter still shows the Gregorian calendar even when the language is set to Nepali, there is a bug where dates convert incorrectly when no month is selected, and [targets/UHC counts](https://docs.communityhealthtoolkit.org/building/targets/) reset on Gregorian month boundaries instead of Bikram Sambat month boundaries. This project is a collection of improvements to make Bikram Sambat a first-class calendar experience in the CHT. The work can be done incrementally (one issue at a time). ## Goals & Mid-Point Milestone - [ ] Understand the existing Bikram Sambat date picker implementation and the [`bikram-sambat`](https://github.com/nickshanks/bikram-sambat) library - [ ] Fix the bug where the date picker defaults to Baisakh (first month) when user hasn't selected a month, allowing incorrect date conversion - [ ] Upgrade the Bikram Sambat date picker with proper calendar view (month/weeks), month/year navigation, "today" button, and clear option - [ ] Integrate Bikram Sambat calendar into the Reports tab date filter (currently shows Gregorian even in Nepali mode) - [ ] Add configuration to align target/UHC count resets to Bikram Sambat month boundaries instead of Gregorian months - [ ] Write unit tests and e2e tests for all changes - [ ] **Goals achieved by mid-point milestone:** Date picker bug is fixed, date picker is fully upgraded, and Reports tab date filter uses BS calendar, with unit tests ## Expected Outcome - A fully functional Bikram Sambat date picker with a proper calendar view, navigation controls, and parity with the Gregorian date picker UX - The Reports tab date filter displays the Bikram Sambat calendar when the platform language is set to Nepali - The date picker no longer silently defaults to Baisakh when no month is selected - A new configuration option (e.g. in `app_settings`) that allows target/UHC counts to reset at the beginning of BS months instead of Gregorian months ## Implementation Details The Bikram Sambat date picker widget lives in: - `webapp/src/ts/` (Angular webapp components) The [nepali-date-picker](https://github.com/opensource-nepal/nepali-date-picker) ([demo](https://leapfrogtechnology.github.io/nepali-date-picker/demo/)) can be used as reference for the improved date picker UI. For the date picker bug: the widget currently converts the date even when the user hasn't selected a month, defaulting to Baisakh. The fix should either require month selection before conversion or handle the missing month gracefully. For the Reports tab filter: the date filter component needs to detect when the platform language is Nepali and render the BS calendar instead of Gregorian. Date range conversions between BS and Gregorian will be needed for the underlying CouchDB queries. For target/UHC alignment: currently targets are stored with an identifier that includes `YYYY-MM` for the Gregorian month. The [`uhc.visit_count.month_start_date`](https://docs.communityhealthtoolkit.org/building/forms/configuring/uhc-mode/#settings) setting controls the day targets reset. A new configuration would override this to use BS month boundaries instead. Key technical consideration: an open design question exists around whether a BS month can ever start and end within the same Gregorian month, which could cause target document ID collisions. ## Product Name Community Health Toolkit: `cht-core` ## Organization Name Medic ## Domain Healthcare ## Tech Skills Needed Angular, CSS, Docker, JavaScript, Mocha, Node.js, TypeScript ## Organizational Mentor @sugat009, @jkuester ## Complexity High ## Category Frontend, Localization

github.com/medic/cht-core

[DMP 2026]: Add API endpoints for advanced contact management operations

opened 04:32PM - 10 Mar 26 UTC

sugat009

DMP 2026

## Ticket Contents Currently, the CHT (Community Health Toolkit) app allows use…rs to perform basic contact management tasks such as creating an editing contacts. Users with the proper permissions can also delete contacts, but _only if there are no child contacts associated with the contact to delete._ More [advanced contact management](https://docs.communityhealthtoolkit.org/building/contact-management/moving-contacts/) current requires a system administrator to use the [`cht-conf` CLI tool](https://github.com/medic/cht-conf). `cht-conf` can perform operations like [moving](https://github.com/medic/cht-conf/blob/main/src/fn/move-contacts.js), [merging](https://github.com/medic/cht-conf/blob/main/src/fn/merge-contacts.js), and [deleting](https://github.com/medic/cht-conf/blob/main/src/fn/delete-contacts.js) contacts in the hierarchy (note that the `delete-contacts` action in cht-conf is _recursive_ so that it also deletes all the child contacts). Having this functionality in `cht-conf` creates friction for users who cannot perform these actions themselves through the webapp, especially when dealing with duplicate contacts or reorganizing health facility hierarchies. It also forces services like [cht-user-management](https://github.com/medic/cht-user-management) to either re-implement these operations or else somehow leverage cht-conf under the hood to perform them. This project aims to add REST API endpoints in `cht-core` for these actions. The work can be done incrementally (one action at a time), giving it a limited initial scope with room to expand. The goal is simply to have api support for these operations. Updating the webapp to actually give the user access to these operations is _out of scope_. ## Goals & Mid-Point Milestone - [ ] Understand the existing `cht-conf` move/merge/delete contact logic - [ ] Implement the delete-contacts API endpoint with support for recursive hierarchy deletion - [ ] Implement the move-contacts API endpoint for relocating contacts between parent hierarchies - [ ] Implement the merge-contacts API endpoint for combining duplicate contacts and reassigning all linked documents (reports, tasks) to the surviving contact - [ ] Write API documentation for all new endpoints in [cht-docs](https://github.com/medic/cht-docs) - [ ] **Goals achieved by mid-point milestone:** Delete-contacts and move-contacts API endpoints are functional with unit and integration tests ## Expected Outcome New REST API endpoints available in `cht-core`: - `DELETE /api/v1/contact/:uuid` (or `POST /api/v1/contact/:uuid/delete`) for recursively deleting a contact and its children in one step - `POST /api/v1/contact/:uuid/move` for moving a contact (and its subtree) to a new parent - `POST /api/v1/contact/:uuid/merge` for merging two duplicate contacts, reassigning all linked documents to the surviving contact These endpoints replace the need to use the `cht-conf` CLI for these operations, enabling them to be performed programmatically or through the webapp. ## Implementation Details The existing `cht-conf` implementations serve as the reference for the core logic: - [`cht-conf/src/fn/move-contacts.js`](https://github.com/medic/cht-conf/blob/main/src/fn/move-contacts.js) - [`cht-conf/src/fn/merge-contacts.js`](https://github.com/medic/cht-conf/blob/main/src/fn/merge-contacts.js) - [`cht-conf/src/fn/delete-contacts.js`](https://github.com/medic/cht-conf/blob/main/src/fn/delete-contacts.js) New API controllers should be added in `api/src/controllers/` following the patterns established by the existing person, place, and report controllers. Key technical considerations: - TODO these actions may involve long-running processes. We need to determine if we should block our REST response until the process actually completes (our typical approach for existing endpoints) or if we should implement some kind of "polling" pattern where we queue the operation and then immediately return a reference to it. Then the consumer can poll a `/api/v1/operation` endpoint to get the status (and know when it completes). - Permission model should follow the `hasAny` pattern (e.g. `can_delete_contacts` OR `can_edit`) - Delete must handle recursive cleanup of child contacts and all associated documents - Move must update parent lineage references across the entire subtree and linked documents - Merge must handle conflict resolution and reassignment of all linked reports and tasks to the surviving contact ## Product Name Community Health Toolkit: `cht-core` ## Organization Name Medic ## Domain Healthcare ## Tech Skills Needed Docker, JavaScript, Mocha, Node.js, TypeScript ## Organizational Mentor @sugat009, @jkuester ## Complexity High ## Category API, Backend

On our end, once the DMP application process is complete we receive a list of candidates that have applied to work on these projects. Our candidate selection process is similar to what you might expect from any internship opportunity. We evaluate candidates based on all the information we have including the proposal, interactions on GitHub issues/PRs, here on the forum, as well as in various public CHT community meetings. It is not just about quantity, but also about quality.

Ved-Patel · April 25, 2026, 8:16pm

Thanks! @jkuester

I will try to align myself with the suggestions you’ve mentioned above!

And not to become a part of C4GT, I would love to be part of community for public good also!

Looking forward to be familiar with the team and community!

santhosh-7777 · April 26, 2026, 9:01am

Hi CHT Community,
I am applying for DMP 2026 to work on issue #10706 in cht-core(Add API endpoints for advanced contact management operations).
I have been studying the codebase and have a question aboutimplementation approach.
The hierarchy logic for delete, move and merge already existsin cht-conf inside:src/lib/hierarchy-operations/
My question:
When building the new REST APIs in cht-core (api/src/services/),should we:
Option A: Import hierarchy-operations from cht-conf as npm packageinto cht-core directly?
Option B: Rewrite the same logic inside cht-core, replacingJsDocs disk-writing with direct db.bulkDocs() calls?
Option C: Any other approach the team recommends?
The main difference I noticed is that cht-conf writes docs todisk first and uploads later, but the API should save directlyto CouchDB.
Would love guidance from the community before writing my proposal!
Thank you!

hendrixoz · April 27, 2026, 3:43am

Hey everyone!

I’m Atul, a CS grad and I found CHT from the Open source programme C4GT.I have been submitting PRs in cht-core repo.(#10934) and (#10926)

I already have experience in the medical software development and won hackathons in that regards.

I would really appreciate if anyone would guide me in making the proposal for the programme!

Appreciate any responses/suggestions regarding the same!

Thanks in advance

mrjones · April 30, 2026, 5:22pm

Thanks for introducing yourself and welcome to the forums @hendrixoz !

@sugat or @jkuester - can you advise @hendrixoz if there’s public guidelines for C4GT. As well, pulling in another forum post here which I assume is on the same C4GT topic, is there an upcoming meeting either of you know about?

I just wanted to know when the Q2 2026 meet is going to take place!

jkuester · May 1, 2026, 1:31pm

I don’t know any of the specific process details from the C4GT side of things. If the question is more regarding Medic’s approach to evaluating DMP proposals, then you can have a look at my response out on this thread: Introduction and seeking Guidance for C4GT

jkuester · May 1, 2026, 1:40pm

Sorry for the delayed response here! I somehow missed this thread. I think it is likely that we will need an Option C approach. It is not really feasible to use the cht-conf actions on the server-side and for similar reasons we will probably need more sophisticated batching/queuing logic in the new api code than is currently in place in cht-conf.

The main open design questions that I think we are still trying to figure out are:

What is the best RESTful pattern for triggering large async batched operations? Do we need another endpoint where consumers could check the status of the triggered operation?
How should all of this work with an offline-first architecture? If we move/merge a contact on the server-side, how can we ensure the move is not reset when an offline user syncs an updated version of the contact? (Or should we roll back the move in this case?) In a similar vein, if a contact is moved/merged on the server-side and an offline user syncs new reports for the contact’s old hierarchy, how should this be handled? Can any of this be handling without causing replication problems and requiring affected users to do a total re-sync?

hendrixoz · May 1, 2026, 1:40pm

Right,Thanks for the reply!