Brainstorming GSoC 2026 Project Ideas

Hey @shyam.dev welcome.

As you are intrested in backend you can definitely see the given below blog post and choose project as per your tech stack.

Hi @jayasanka, I’m Teshan, and I’m very interested in the GSoC project ā€˜Integrate O3 with the Authentication module.’

I’ve been reading through the OpenMRS Wiki and the O3 documentation. I’m currently trying to set up the development environment locally to get a better feel for the codebase. Do you have any recomendations?

Looking forward to contributing!

Hi everyone, I’m Crosse, a CS student from Maryland. I have experience with React, TypeScript, and full-stack development (Django, MongoDB). I’ve been contributing to the p5.js website repo recently for GSoC and wanted to explore OpenMRS as well.

The Native O3 Frontend for the Audit Trail project caught my eye since the backend API is already built and it’s mainly React/TypeScript frontend work which is where my experience is. I’ve built role-based dashboards before (healthcare job board project) so the concept of building admin facing UI for viewing logs feels familiar.

I’m going to start setting up the O3 dev environment and looking through the audit log module. Any tips on getting started would be appreciated.

Hi everyone,

I’m really excited about the Integrate O3 with the Authentication module project idea. I’ve been setting up OpenMRS locally, which involved cloning the Authentication module repository, building it, and replacing it inside my local server setup so that the system picks up the locally running authentication module. I also used a .omd snapshot to initialize the database and test the setup. It took some time to get everything working smoothly, but now the system is up and running, and I’m eager to dive into both the frontend (React/Typescript) and backend (Java) aspects.

@jayasanka, could you advise if there are specific patterns or examples you’d recommend for handling the ā€œfake redirectā€ responses so that O3 can properly process TOTP validation?

Looking forward to your guidance!

Thanks, Sudesh

Hi @teshan,

I recently went through the setup process for this project as well, so sharing what helped me.

  1. Clone both the O3 frontend and the Authentication module repositories.

  2. Build the authentication module using Maven. After building, you should see a file like authentication-2.3.0-SNAPSHOT.omod inside the target folder.

  3. Move that .omod file to your local OpenMRS server’s modules directory so the server can load the locally built authentication module.

  4. If you don’t already have a local OpenMRS server, you can create one using the OpenMRS SDK with Maven (mvn openmrs-sdk:setup) and follow the setup guide.

This worked for me when testing the authentication module locally. If I missed something or if there’s a better way, please feel free to correct me.

Hope this helps!

Hi everyone!

I’ve already introduced myself in the introductions thread, but I wanted to formally express my interest in a specific GSoC 2026 project idea.

I’m particularly interested in the Improved Appointments Calendar View project. As someone with a strong frontend background in HTML, CSS, and JavaScript, I feel this project aligns well with my skills and is something I’m genuinely passionate about improving for clinicians using OpenMRS.

To get started, I’ve already been engaging with the community — I recently submitted PR #240 (feat(O3-5125): add keyboard navigation for tutorial steps) as my first contribution to the openmrs-esm-user-onboarding repository. This helped me get familiar with the O3 codebase, the contribution workflow, and the React-based frontend architecture.

I’d love to connect with the mentor for this project ( @bawanthathilan ) and any community members who can point me in the right direction — whether that’s related tickets to explore, documentation to read, or anything else that would help me put together a strong proposal.

Thanks so much for the warm welcome so far — this community has been incredibly supportive!

Best, Verosha

Hi OpenMRS Community!

My name is Shana Ibatuan. I am a computer science student with experience in Java interested in applying for GSoC 2026 with OpenMRS.

I’m fairly new to open source but I’ve been going through the openmrs-core repository and setting up my local development environment. I have 1–2 years of experience with Java and I’m genuinely excited about the mission behind OpenMRS.

I’m currently looking for an introductory JIRA issue to make my first contribution. Could anyone point me toward a good first issue that’s unassigned and ready for work?

I’d also love some guidance on which GSoC 2026 project ideas would be a good fit for a backend Java developer who’s new to the codebase.

Thank you!

Also, is there a way for me to get JIRA access?

Hi @kmakombe @dkibet,

I’ve been thinking more about the filtering approach for the Smart Notification Feature and wanted to share an idea.

Static critical thresholds alone will still cause alert fatigue for chronically ill patients. For example, a chronic kidney disease patient will always have elevated creatinine. If we just check ā€œis creatinine > 4.0?ā€, the clinician gets an alert every time that patient’s labs come back even though it’s completely expected. That’s the exact noise we’re trying to avoid.

What if the filter service also checks the patient’s active conditions before firing a notification? Something like:

  • Query the patient’s active conditions using ConditionService

  • Compare against configurable suppression rules stored as global properties (e.g., notification.suppress.creatinine = kidney disease, renal failure)

  • If the abnormal value is expected given an existing diagnosis, suppress the alert and log it for audit

This way the system asks not just ā€œis this value abnormal?ā€ but ā€œis it abnormal for THIS patient?ā€

I got this idea from the McGreevey et al. (2020) paper on reducing alert burden, which specifically recommends tailoring alerts to patient characteristics. The project wiki also mentions ā€œExpected Abnormal Results → No interruption neededā€ but doesn’t specify how to implement it.

Would this be feasible within the GSoC scope, or better suited as a later enhancement? Happy to hear your thoughts.

Hi everyone, I am a GSoC 2026 applicant working on the Improved Appointments Calendar project. I have been reviewing PRs and studying the codebase actively. Unfortunately I am facing a GitHub account restriction that is preventing me from forking repositories and submitting PRs before the deadline tomorrow. I have contacted GitHub support but have not received a response yet. Could a mentor please guide me on how to proceed or if there is any alternative way to submit contributions?

Hi @everyone,

I’ve been gone through the official GSoC project ideas and wanted to show my proposal.

My proposal focuses on improving patient data interaction and usability, particularly around how clinicians explore and interpret data. I believe this aligns closely with areas like improving UI/UX and interaction in modules such as Service Queues or similar O3 frontend improvements.

I would really appreciate any mentor’s guidance on whether aligning my proposal more explicitly with one of these ideas would be better, or if I should focus on a specific module.

Yours sincerely

Hi Everyone,

The proposal submission period is now over. Thank you to everyone who took their time to contribute and submit a proposal.

After the mentors have reviewed them, all accepted projects and students will be announced by April 30, 2026. You can find the program timeline here.

In the meantime, feel free to continue exploring, contributing and engaging with other community members.

1 Like