O3 Growth Chart

dilankavishka · January 5, 2026, 2:23pm

Hello Everyone,

I’m writing to say how much the O3 Growth Chart project for GSoC 2025 interests me.

I see how important this capability is for paediatric care inside the OpenMRS environment after looking over the requirements. I’m thrilled to take the lead on this and am totally dedicated to seeing this project through to completion.

I’ve already written a thorough project proposal and started integrating the Growth Chart app with the O3 Patient Chart to gain a jump start. My objective is to develop a solution that satisfies our implementers’ clinical demands.

Here is a screenshot of the implementation so far:

I have attached my project proposal below. I would be incredibly happy to receive your guidance, feedback, and inputs to ensure the design and timeline align with the community’s vision.

Link to the proposal : https://docs.google.com/document/d/17Td-T_rgl3HrigjSVIb69Kc6Pny3ZoeRGzi715dXPe4/edit?usp=sharing

I look forward to arranging a meeting with the mentors to discuss the technical approach in more detail and start working on the next steps immediately.

Thank you!

@lumuchris256 @anjisvj @grace @jayasanka

akanter · January 5, 2026, 2:54pm

It would be great to have an updated version included in the O3 framework! Have you checked out the SMART on FHIR version here: Growth Chart

I would think that @ball would want to comment on this, too. My only recommendation would be to use black for patient data as the colors on the graph are quite distracting. Viewing data both in raw form and percent/z-score would also be helpful, but leave that commentary to practicing pediatricians

ball · January 5, 2026, 3:54pm

Thanks for bringing this up. Partners In Health uses the growth chart with OpenMRS RefApp2 for Haiti, Sierra Leone and other implementations. This was written for iSantePlus by Kaweesi Joseph (may his memory be a blessing) and others. The code has been awesome, bug-free, and flexible. It allows for multiple CDC or WHO growth charts. It is an excellent example of code written by the community and shared with all. A great example to start the new year. And even better to get this implemented with O3.

This 2019 thread discusses and includes screen shots: Growth Chart in RefApp

@fanderson @ddesimone @akanter @dilankavishka @mogoodrich @mseaton

dilankavishka · January 6, 2026, 3:46am

Thank you both for the incredibly insightful feedback! @akanter @ball

It is really motivating to hear how important this functionality is for the community and its history in implementations.

@akanter — Thank you for sharing the SMART on FHIR reference. I will definitely study it to ensure we align with industry standards. Regarding your design feedback.

@ball — Thank you for the historical context. It is an honor to work on modernizing a tool that has been so reliable for the community. I will closely review the 2019 thread and the original RefApp2 code to ensure the O3 version retains that same level of flexibility and bug-free reliability.

anjisvj · January 6, 2026, 4:14am

Hi @dilankavishka,

Great to see your interest in the growth chart project, and thanks for starting this thread and showing such initiative.

I’ll review your proposal and share feedback shortly. In the meantime, let’s set up a call to discuss the scope, expectations, and next steps together

dilankavishka · January 6, 2026, 8:37am

Hi @anjisvj,

Thank you so much! I really appreciate you taking the time to review the proposal.

I would love to hop on a call to discuss the project scope and next steps. Please let me know what dates or times work best for you.

Looking forward to it!

cc: @lumuchris256

anjisvj · January 10, 2026, 6:31am

Hi @dilankavishka,

Please let me know which time works best for you.

January 10th, 5:00 PM
January 10th, 6:00 PM
January 10th, 7:00 PM
January 10th, 8:00 PM
January 11th, 5:00 PM

0 voters

lumuchris256 · January 10, 2026, 6:57am

This is great .. catching up with the proposal and yes available over a call to discuss further @dilankavishka @anjisvj

dilankavishka · January 10, 2026, 1:17pm

Hi @anjisvj @lumuchris256 !

As we discussed in the meeting, we have finalized the scope for the initial stage of this project.

The Scope: For the first stage, the plan is to complete the process with the WHO Configuration.

Initiate the project (create the growth chart app).
Fetch patient demographics and observations:
- Patient details: Sex and Birth Date.
- Observations: Weight and Height.
Integrate official WHO dataset: Under this we will do the calculate the Z-scores part as well.
Create the Table View.
Create the Chart View.
Write E2E tests for the implemented parts.

My next steps :

Create the tickets under the main Epic for O3 Growth Chart.
Complete the first ticket to initiate the project.

Thank you for your time and the guidance you gave in the meeting!

cc: @ibacher @dkigen @ball

dilankavishka · January 11, 2026, 9:23am

Hi @anjisvj @lumuchris256 ,

I have created an Epic for this project and under that Epic I added six child work items based on the scope we discussed during the meeting

Epic Link : Jira

Could you please review the Epic and its child work items and let me know if anything needs to be corrected, refined, or changed?

@dkigen I would looking the guidance on the best approach for pushing the implementation to the main branch. I came up with 2 ideas.

Create a single feature branch (e.g: growth-chart) from main, implement each child work item incrementally in to that branch, and finally merge it into main.
Create a separate branch for each child work item from main and merge each one individually into main.

Could you kindly advise which approach would be preferred for this project?

cc: @ibacher @ball

dilankavishka · January 20, 2026, 10:36am

Hello!

I have started implementing this project and raised a few PRs for the work done so far. As @nethmi suggested during the PR review, I am now working to combine this work into a single PR.

I have two questions regarding this implementation.

Q1 - Feature flags

What is the recommended way to implement feature flags for patient chart features in O3? Should this be done via the configuration framework / app config, or is there an existing feature flag utility or pattern I should follow?

Q2 - Backend

My initial implementation placed the WHO standard data as static JSON within the frontend module, but during PR review it was pointed out that embedding this data as static JSON in the frontend is not ideal, and that initializer/content packages would be preferable for configurability. However, I’m unsure how best to approach this since there’s currently no backend module managing this metadata.

Could you advise on the recommended way to handle this challenge, particularly whether introducing a backend module?

PRs -

1. Initiate the project

2. Fetch patient data

3. Add WHO growth standards

platform @dkigen @dkayiwa @ibacher @jayasanka @wikumc @anjisvj @lumuchris256

Thank you!