My fellowship Journey: Hadijah Kyampeire

Any time before 4:00 pm EAT

Great, let’s wait for Suruchi and Sharif to see if they are okay with that time and date.

Thanks @hadijah315 am fine with the time , we can sync

1 Like

Thanks, @sharif for honouring the invitation on short notice.

1 Like

Documentation work

On behalf of the Dictionary manager, I have been working so closely with the Documentation team these last few months to improve the Get Started guide for both Technical and non-technical contributors, thanks to the teams’ guidance and feedback, I managed to greatly improve the document.

Also thanks to @bstuder99 for organizing the folder structure and directory of the team documents.

Another exciting event that just started with the documentation team was the monthly documentation workshops these have been great and fun with great ideas to expand and improve documentation across the community. Thanks, @kaylinbracey @jennifer, and @gracebish for the organization.

Mentor Office Sessions

For this past month, we have had great mentor sessions about feedback, I personally learnt a lot from Jennifer and the other member through sharing different experiences and I am happy to share that I have started working on implementing the Feedback Sandwich that I learnt from the sessions. Looking forward to more educative sessions like those. :point_up:

Separating Dictionary Manager Workflows

For the October sprint, I had a task to make separate workflows for the Dictionary Manager automated tests, at first I wanted to use tags as advised by @sharif and @kdaud but unfortunately I wasn’t successful, we had a couple of pair sessions with Sharif, Daudi, and Suruchi to try and get tags to work but it looks like we were missing something, however, we plan to come back to using tags once we figure that out. cc @kdaud @sharif.

Automated tests and data level testing

For the past month, I have been focused on writing cypress and cucumber tests for the importation process from the Dictionary Manager to the OCL Subscription Module and then doing a data field level testing between the OCLApi and the RefAppApi to confirm that the concepts are correctly imported. I am happy to share that it is 95% done and passing well.

It was a challenging and learning experience for me, thanks to the people who were there to answer my questions and guide me through this work. @ibacher @suruchi @sharif @grace .

Dictionary Manager work sessions

Last week we had two days of dedicated work sessions and an open QA session for the Dictionary Manager and the OCL team, this was a very great experience. I got the chance to have pairing sessions with @suruchi and @ibacher about some of the tickets that were stressful, through the sessions we made great progress and were able to finish the tickets shortly after. Thank you to our PMs(Grace and Suruchi) for organizing that and thank you to our Senior talent and the OCL team who were there to answer any of our questions.

Below is a screenshot of the automated tests for OCLOMRS-1061. and the ReadMe badge for the workflow badge.

Note the data field testing will not be seen in the browser since it’s not a UI interaction but you can check them up on the pull request.

For the next month and a half, as I conclude my fellowship journey, I intend to continue with the Dictionary Manager technical work, mentorship sessions, and possibly start on the documentation work for ticket management on the Dictionary Manager Squad.


Happy new year 2022 to all of you :fireworks: . We have finally come to the end of our fellowship which started in April 2021 and I am glad to say it was such an amazing journey of learning and sharing knowledge.

Great thanks go to everyone who made this possible for us, the community leads and organizers @jennifer @grace @burke @michaelbontyes @ball @dkayiwa @ibacher, and all the other stakeholders, thank you so much for giving us such a great opportunity.

Great thanks to @ibacher our senior Engineer for always helping us and guiding us both technically and professionally on how to improve our coding skills.

To the Dictionary Manager squad @grace @ibacher @suruchi @jwnasambu @chanu1993 , thanks for being a great team, together we achieved great things and improved the Dictionary Manager App. Let’s continue building and improving the Dictionary Manager Application.

I also had a chance to work with the QA squad because we had to implement automated tests for the Dictionary Manager, thanks to @sharif and @kdaud for being there whenever we needed you and helping us understand the QA concept.

Besides coding, I also had a chance to work with the Documentation team and learned how to write technical documentation that can help both technical and non-technical contributors to get started with the projects we have in OpenMRS. Thanks, @bstuder99 @jennifer @kaylinbracey @gracebish for the guidance and feedback.

Lastly, Special thanks to Suruchee for being a great mentee, friend, and team player.

I am looking forward to continuing the development of Dictionary Manager and other projects in the community.


New Fellowship starts today :fireworks: :hugs:

Hello everyone, I am excited to share the news of a new fellowship journey which I am starting today as a Fellow under the mentorship of a senior Engineer @zacbutko . I am looking forward to learning new skills and building my engineering career with his guidance.

I would like to extend special thanks and appreciation to the fellowship board and management team for giving me this opportunity to participate in this fellowship. @jennifer @grace @christine @paul @zacbutko thank you so much.

Very excited about this new journey :raised_hands: .

More updates will be coming in…


Congratulations @hadijah315

1 Like

Thanks @abertnamanya

Congratulations :confetti_ball: @hadijah315

1 Like

OpenMRS Frontend Dev Fellowship Journey 2022.

I got the opportunity to be part of the OpenMRS fellowship as a Frontend Dev mainly working on 3.0 app and getting familiar with MicroFrontends. We had an official kick-off last week where we were onboarded on how the classrooms will be working. I am so excited to use the classroom platform it is so organized and helps one to properly keep the progress of their work in a given timeline.

I had my first call with my mentor @zacbutko who gave me pointers on how to get started and told me about some ongoing work that I can contribute to.

What I plan to do in my first month

  • Use the template repo, build on it and add my own small MF in order to get familiar with how components are used and how data is fetched from the API.
  • Weekly calls/syncs with my mentor.
  • Attend squad calls and design calls to get more knowledge of what is happening around the application development.
  • Collaborate with @lumuchris256 during development since we have aligned goals and share the same interest.
  • Revise and document my fellowship goals.

Month 1 of the fellowship(April-May):

In my first month of the frontend dev fellowship, I have been able to learn a lot and I have been able to achieve or start on my goals for the first 2 months.

Getting started with building Microfrontends based on the template repo:

  • I implemented the OpenMRS admin info page using carbon design tables and styles, I accomplished that in two PRs i.e PR1 and PR2. Thanks to my mentor for reviewing my work and advising me on the best practices that are used on the 3.x, this helped me to prepare well to start contributing to the main repo.

Working on the esm-patient-management-repo: (Patient Visit Header)

  • After getting familiar with how microfrontends work, I was ready to dive deep into the actual codebase. With the guide from my mentor, I picked a big feature for Patient Visit Header which we want to add to the patient chart page and have some actions and patient info easily accessible at the top nav.
  • Thanks to @dkibet for starting on this feature. I started with making some enhancements to the header like adding functionality for the Start Visit button, catering for long names, and using the right teal color as per the zeplin mocks and ticket description.
  • Implementing the visit header close button as expected: The close button on the visit header is meant to take the user back to their previous page or fall back to home if there is no previous page.

What I plan to do next

  • Continue working on the visit header, there are many more implementations needed like adding the patient status and visit type.
  • Weekly syncs with my mentor.
  • Squad calls and showcases.
  • Continue to build and update my goals.

Thanks to @zacbutko @ibacher @dkibet @dkigen for the technical support towards my fellowship journey.


Month 2/3 (June-July):

I made a lot of progress in my fellowship journey in the second and third months. I extended my knowledge by working on more than one module.

Part 1: openmrs-esm-patient-chart-repo.

  • Worked on the dashboard left NavLink making it style differently for the active/clicked link.



Part 2: openmrs-esm-core-repo.

  • Added a global class that can be accessed in other modules to apply the same styles.




  • Had a few pairing sessions with fellow devs.

  • Squad showcase of my work.

  • Weekly syncs.

  • I also had a trip for 3 weeks, I was able to work for a few days and took others off.

Up Next:

  • Planning my fellowship project.
  • Getting involved in appointments work or any other high-priority work for the application.
  • Attend more of the coffee breaks with the FE team, the first one I attended was great :heart: .

Thanks to; My mentor @zacbutko for always directing me, @ibacher for PR reviews, and guiding me to improve my skills, @cduffy for design and style guidance, @nikeshbalami for guiding us through this fellowship journey. Fellow devs @jwnasambu @deb and @irenyak1 for the great collaboration.


Nice to read this about your progress in your fellowship. Welcome back Hajati, and all the best in your journey.

1 Like

Thanks, Irene :heart:

End of July(Beginning August)

Hey all, I am excited to announce to you my proposed fellowship project :hugs:.

3.x Appointments module:

  • For my fellowship project I will be focused on the appointments module which has already been started on by the Palladium team and some other senior devs in the community. I chose this with the guide and discussion with my mentor @zacbutko because it is one of the most valuable features that is needed in our applications. Below is a background I based on to go ahead and choose appointments as my focus project and a link to the entire proposal document.


The appointments module application serves to create/ improve the doctor-patient handling management system that will help doctors in their work and will also help patients to book doctor appointments and reports. The system allows doctors/clinicians to manage their booking slots online. Patients are allowed to book empty slots online and those slots are reserved in their name.

The project also addresses the problem of tracking the patient history, with an appointment system, it becomes easy for both the patient and the clinician to review the patients’ medical history when the patient visits again.

With an appointment system, the patient doesn’t have to visit a hospital and wait for any available doctor to see him/her since they will already have an appointment scheduled for a specific date and time.

My Fellowship Project Proposal(subject to improvements).

Thanks to; @grace for guiding me and giving me more information I need to perfect my proposal and get started with coding. And the Palladium team for welcoming me to contribute to building the module.

I am looking forward to getting started :raised_hands:


Hello everyone, with the guidance from @nikeshbalami and @grace I made improvements to my proposal. Here is version 2 of the proposal, looking much better :slightly_smiling_face:.


Hello everyone, it’s the end of August and a lot has gone on in August.

I started working on my focus project for the fellowship i.e Appointments. I have so far not worked on many tickets but I have been able to understand and explore more about the Appointments module thanks to Cynthia and @grace .

I successfully implemented the creation of an appointment. PR I have worked on some other small fixes on the patient chart. Looking forward to the new work on appointments.

Thanks to @mksrom @zacbutko @vasharma05 @ibacher and everyone for the support.

Exciting events I am attending:


End of fellowship phase 1 :hugs:

Hello everyone, the beginning of October marked the end of my fellowship journey phase 1 and I would like to share with you some of my achievements in the past 5 months.

First of all, I would like to extend my great thanks to the fellowship management team for giving me the opportunity to be a frontend fellow developer on the 3.x. Thanks, @jennifer @grace @dkayiwa @nikeshbalami @christine and everyone for putting trust in me to be part of the fellowship.

In other special thanks, I would like to thank my mentor @zacbutko for guiding and grooming me through this fellowship to become a better engineer. @ibacher and @bistenes for the mentorship through PR reviews.

I will give highlights of some of the major work that I have worked on, more details will be in the attached slides and the Loom video.

  • Patient visit header.
  • Patient chart left Nav highlighting.
  • Appointments module specifically creating an appointment and viewing appointments.
  • Home Today’s Appointments widget.
  • Ability to mark a patient as deceased or Alive. (Worked on it with @jnsereko )

Overall, this fellowship journey has been a great experience for me, I have learned a lot from the amazing people around the community.

Lastly, thanks to fellow developers for great pairing sessions, debugging sessions, and reviews which always help us become better in what we do. i.e @vasharma05 @jwnasambu @dkigen @dkibet @minimalist @deb @jnsereko @achachiez and @wyclif.

I would like to also mention that I was given an extension through the end of the year :smiling_face_with_three_hearts:, so I will be extending my fellowship up to December.

  • I will continue to focus on development on 3.x, making some improvements to various parts of the application.

Looking forward to sharing more in the coming months.

Slides with details of my fellowship reflections.

Loom video


End of my 2022 fellowship journey.

Hello everyone, I am excited to inform everyone that December 31st marked the end of my 2022 fellowship journey which started in April.

These past 9 months have been one of the best months in my career journey, I was working as a frontend fellow dev on the OpenMRS 3.x and it has been an amazing experience :slightly_smiling_face:, I am somehow sad it has come to an end but non the less I will continue as a frontend engineer on the OpenMRS 3.x.

OpenMRS fellowship orientation

In November and December, we had very amazing sessions concernig the fellowship and guiding all interested fellows and fellow mentors. I learned a couple of skills from those sessions

  • How to become a good open-source contributor.
  • How to define and identify development goals.
  • How to structure them as smart goals.
  • Consider both technical and non-technical skills, among others. They were very good sessions that enlighted most of us on how to develop well-structured professional goals and plan to achieve the best skills. Thanks, @erica, and @jennifer for organizing that program for us.

Development and squad syncs

  • I have been actively contributing to the OpenMRS 3.x frontend modules. I had a chance to extend to some modules which are not in React, it was both a challenge and an opportunity for me to learn new frameworks like Angular for the form-entry-app and the form engine.
  • Having coffee break syncs with squad members where we unblock and guide each other in development work.

I can’t summarize all my commits, achievements, and experiences but most of them are in the previous posts and do reflect on my fellowship learning plan.

I would like to end with special thanks to the fellowship management @jennifer @christine @erica , mentors @zacbutko @ibacher @grace @dkayiwa @dkigen , fellows @jnsereko @suruchi @kdaud @tendayi.mutangadura, OpenMRS 3.x squad members @vasharma05 @jwnasambu @deb @jumagits , and the community at large for the opportunity, mentorship, dev pairing, and syncs respectively which have contributed much to my career growth.

Looking forward to being part of the 2023 fellowship :palms_up_together: :slightly_smiling_face:.

Happy 2023 ! :fireworks: