Summer of Code 2025

Growth Chart App for O3

Medium

• Growth Charts are a common need in Primary Health Care for children (pediatrics). Growth Charts are available in O2, but never yet added to O3.

• With more and more implementers using O3 for care that involves infants, babies, and young children, we need Growth Charts in O3!

React

@Anjula Samarasinghe

Implement Stricter Typescript configuration

Medium

This project aims to enforce stricter TypeScript configurations across OpenMRS repositories, ensuring developers follow best practices for strong typing. The primary goal is to eliminate the use of any, enforce strict type safety, and refactor existing code to comply with these rules.

By implementing stricter TypeScript settings and refining type definitions, this project will enhance code maintainability, reduce runtime errors, and improve the overall developer experience.

React, Typescript

@Christopher Lumu

@Anjula Samarasinghe

Integrating Data Filter for Data Segregation / Multi-tenancy

Large

Data Filter is a powerful module that uses Hibernate’s filtering APIs to add additional where clauses to various SELECT statements. The use-case for this is to allow system-wide filters to be applied to the data added. Currently Data Filter includes a default set of filters that restrict the availability of data on patients to a set of locations a user has access to. The point of this project would be to expand on these capabilities to add things like: an administrative UI for associating users and patients with specific locations, additional rules to account for the various modules used in the O3 RefApp, templates for additional rules that may be useful (i.e., tie the ability to see obs with certain codes to certain privileges).

Java, Hibernate

@Joshua Nsereko

@Wyclif Luyima

Support for horizontal scaling of OpenMRS instances

Large

In the scope of the project would be (depending on the progress we make using other contribution channels):

1. Adjust codebase across core and O3 modules to use a new storage service described here.

2. Adjust code in core and O3 modules to use distributed caching

3. Experiment with Hibernate Search using OpenSearch as backend instead of a local Lucene index.

Java, Hibernate

@Rafal Korytkowski

Improved Appointments Calendar View

Medium

We have an appointments calendar that is meant to give an overview of appointments. Unfortunately, it is currently less useful than it should be. A few things we need to address: the ability to drill-down into, e.g., monthly, weekly, and daily views; the ability to see all appointments, not just the number per service, instead of changing screens when clicking on a day or service, the app should likely display a modal; the calendar view should not be hard-coded around the Gregorian calendar, but support the various calendars from the @internationalized/date package.

React

TBA

Service Queues

Medium

We have a service queues app in O3, which is functional, but needs some attention, both to the frontend design and to the backend APIs that are used to populate it. The goal here would be to fix various UI issues and improve the overall performance and reliability of the queue module. The Service Queues view is incredibly useful for managing outpatient clinics, allowing users to track who is waiting for service, how long they’ve been waiting for etc.

React, Java

@Ian Bacher

Forms Migration Tool: Help HTML Form users switch to using O3 React Forms

Medium

• Many OpenMRS implementers have used HTML Forms (HFE) for many years. Some organizations have dozens or even hundreds of OpenMRS forms encoded in HTML. This makes it intimidating to consider moving to O3, since O3 uses a custom Form Schema.

• There was a previous community project with scripts that help convert HTML forms into the O3 Form Schema for the Angular Form Engine. This did not convert 100% of the form into the new schema, but got most of it done (60-80%) so that it is faster for a team to work on the transition.

• This project needs to be (1) updated to enable implementers to convert HTML forms into the newer React Form Engine schema, and (2) documented to explain how to use it.

Improved Appointments Calendar View

Medium

We have an appointments calendar that is meant to give an overview of appointments. Unfortunately, it is currently less useful than it should be. A few things we need to address: the ability to drill-down into, e.g., monthly, weekly, and daily views; the ability to see all appointments, not just the number per service, instead of changing screens when clicking on a day or service, the app should likely display a modal; the calendar view should not be hard-coded around the Gregorian calendar, but support the various calendars from the @internationalized/date package.

React

TBA

Appointments

Medium

Scheduling appointments is an important function of an EMR. Unfortunately, the RefApp is currently stuck on an older version of the appointments module. What we would probably want to do here is (unfortunately) fork the appointments module to get the various fixes the OpenMRS community needs, update to the latest version of the module.

Java, Hibernate, Spring

TBA

Dynamic EHR: Custom Home screen (and other screens) based on User roles, locations and other values. (doc)

Medium

We would like to show UI elements on the O3 home page and other pages that are most relevant to the user. Currently, there is ability to do so based on User privilege. However, this is limiting and not general enough. We would like to define what to show based on other values, such as Location, currenting displayed Visit / Encounter, etc…

More generally, this can be solved by having a way to write custom logic (in the form of a reduced set of JavaScript expressions) to define whether an Extension should be shown. There is actually something (what?) similar in O2 already. We should be able to inject dynamic variable

React

Archiving voided data

Large

Voiding in OpenMRS is a form of soft-deleting. We basically set a binary column to 1 and attempt to ignore data at various points. Voiding data is meant to mark it as invalid for one reason or another (e.g., an obs has been superceded or data was recorded against the wrong patient). This is very useful, because voided data can be easily restored, but over the long term (especially with “immutable” objects likes obs), this causes some OpenMRS tables to grow to contain far more voided data than non-voided data. To address this, we should add a mechanism to archive voided data with the possibility of restoring it.

Better way to receive feedback from clinicians / users