Fix the Fast Data Entry feature (GSOC 2025) : My Journey

Fix the Fast Data Entry feature (GSOC 2025): My Journey

Hey everyone,

Figured I’d document my journey here while working on Fix the Fast Data Entry feature for Google Summer of Code 2025 with OpenMRS. This way, maintainers and reviewers can track my progress, and I have a record of my learning.

What I’ve Done So Far

  • Set up my OpenMRS ID.
  • Got access to Wiki and JIRA (I now have the power… and also a hundred tabs open).
  • Set up the repos locally and wrestled with the codebase until it (sort of) made sense.
  • Completed the “Intro to OpenMRS 3: For Developers and Technical Teams” course (10/10 would recommend).

After digging through all the issues, Fix the Fast Data Entry feature stood out as the most interesting (and least terrifying) to me. So, here we are.

Who Am I?

  • Dinesh Tyagi (a.k.a. dkt_o1, dinesht_04)
  • 3rd-year B.Tech C.S. student at VIT Bhopal
  • Health Informatics specialization
  • Been studying EHRs, EMRs, and CDWs for almost two years now :sob:

That last part is kind of a joke, but also a very real reason why this project feels like the perfect fit. Excited to contribute, learn a lot, and probably question my life choices a few times along the way.

I’ll keep updating this thread as I go. Stay tuned.

2 Likes

Progress Update - [11/3/25]

Today, I made some progress in understanding the GSoC proposal requirements and started exploring JIRA to find React-related issues. Here’s where things stand:

  • Looked into the eligibility requirements for submitting a GSoC proposal to OpenMRS.
  • Started navigating JIRA, but it’s taking some time to get familiar with the system (I’M LOST).
  • Searching for React-related issues where I can contribute, though I haven’t found the right one yet.
  • Going through each project one by one to understand how OpenMRS functions.

Even if I don’t immediately find a suitable issue, this process is helping me gain a clearer understanding of OpenMRS and its structure. Getting to know about all the projects (the name atleast) is pretty cool. I’ll keep refining my search and hopefully find a good starting point soon.

Assigned this issue to myself. Nothing to it but to do it. Let’s Go! ( didn’t know I have the power to assign issues to myself :sob: )

Happy Holi everyone!

Made some significant progress on this issue:

  • Tested the API on Thunderclient to check normal and error responses.
  • Integrated the API into the front-end so that the component receives and displays the data. --Created a new hook - newVisitsApi() (I know not a very creative name) hook which calls this api and retrieves all the light data required for the initial render.
  • Need to implement logic to call useInfiniteVisits() only when the user clicks the Tests, Medications, or Encounters tab and store and handle all the data locally. Now that Holi celebrations are over, I’ll be spending more time coding, Cheers !
1 Like