Page Comparison

Next Generation Implementer Tools for OpenMRS 3

Redesigned config tools for O3

Advanced

350 hours

Non-tech users can set up a 3.x EMR in a friendly, no-code UI, similar to designing a website. Empowers local team members to set up and config their EMR themselves. More detailed user stories and requirements documented here. Project plan documented here.

Scope: technical work on the redesigned config tools for O3.

*Design is done because Ampath/@jdick graciously contributed designs and user testing, sample designs, and @bistenes gave a lot of architectural and technical input but then had to set the project aside.

React

Javascript

Typescript

Responsiveness & Tablet-based Needs for OpenMRS 3

Priority frontend UX changes to improve responsiveness

*Cancelled due to mentor availability*

Medium

175 hours

We have a ton of designs for 3.x that show how the frontend UX should change based on screen size or device (e.g. large desktop, small laptop, or tablet). Much of this responsiveness still needs to be implemented consistently throughout the application.

Watch this video for more information.

React

Javascript

Typescript

Next Generation Form Builder UI for the OpenMRS Community

Ampath Form Builder replaced with a React based module

Medium

175 hours

We could continue to use existing Ampath Forms Engine but replace the Ampath Form Builder with a react based module (instead of the angular one).

The Ampath Form Builder UI is pretty easy to use and build forms quickly, but it’s buggy and could be so much better.

(Demo of the current WYSIWYG user experience of this builder here: OpenMRS WYSIWYG Form Builder Demo - YouTube 1)

React

Javascript

Typescript

Redo Legacy UI Cohort Builder 

Re-do  legacy ui cohort builder in 3.x

Medium

175 hours

React

Javascript

Typescript

Improving 3.x E2E Tests

3.x E2E automated tests written and ready for use

Medium

175 hours

Current tests are less reliable because they are not very stable. Sometimes they pass, but there is still a chance that they will fail. Also, tests suddenly start to fail when there are new changes in the implementation. We need to look into ways to improve the reliability of tests.

Run tests against Pull requests

Currently, we don’t have a mechanism for running tests against Pull requests. As a result, no failures can be detected until the changes are merged and someone run the tests manually. It makes it difficult to detect root courses as well as to engage developers. We need a proper way to run these tests against the changes in pull requests.

Improve developer engagement

The contributor should collaborate closely with the O3 squad to identify new workflows, design tests, and write them.

We need to find solutions to the above while identifying other ways to make things easier for developers.

Automated software testing

CI/CD Pipelines

Containerized applications

Single-page applications and Micro-frontend architecture

OCL Subscription Module for OpenMRS 3

OCL module functionality available as a microfrontend

Medium

175 hours

The OCL Module is the last remaining OMOD that depends on the (effectively deprecated) OWA Module. We want to be able to remove the OWA Module from our 3.x RefApp distro, and currently it’s just the OCL Module preventing this.

@ibacher has already set the groundwork by setting up an ESM monorepo and skeleton of the work on GitHub

React

Javascript

Typescript

Migrating from OpenMRS ID  to KeyCloak

• Potential sustainable ID system solution identified
• Proof of concept set up
• Roadmap for migrating users to the recommended OpenMRS ID system. 
  

Medium

175 hours

Our current ID system is beyond its end of life and unstable. This leads to significant interruptions for OpenMRS projects prioritized by users. A new OpenMRS ID system will reduce service interruptions, reduce infrastructure volunteer workload, and eliminate security vulnerabilities.

We would like the user 'handle' to be shared across Jira, Confluence and Discourse. The new ID system should either be free for open source projects, or extremely cost-effective for the amount of users we have. We are open to hosting open source tools, using cloud projects, or using Atlassian ID directly as OpenID or similar. 

DevOps

Authentication and SSO

IT Strategy

Building a Testable FHIR Implementation Guide

• FHIR2 Module Implementation Guide with testable resource templates, example resources, and profiles. 
• Integratede testable IG fixtures with FHIR2 module integration tests.
• Piloted the use of TestScript, TestReport, and other components of the FHIR Implementation Support Module in testing the FHIR2 module capabilities. (see more)

Medium

175 hours

In an effort to validate the capabilities of the OpenMRS FHIR2 Module using standard FHIR structures, we're proposing a project to develop the OpenMRS FHIR Implementation Guide(IG) into a testable IG that connects the contained technical specifications with the testing packages for the FHIR2 module.

FHIR Implementation Guides (IGs) provide a standard way of documenting FHIR services, and our primary goal is to align the FHIR2 module documentation with this standard, using the available best practices for IG development. This github repository currently houses the skeleton IG for the FHIR2 module, of which a compiled version is viewable at  https://fhir.openmrs.org. You can see more about the FHIR2 project on the wiki page: OpenMRS HL7 FHIR Solutions.

FHIR

Advanced

350 hours

It's time to clean up our SDK and improve the developer experience.

Advanced

350 hours

-Android 
- Java
-Kotlin
-MVVM Architecture
-JUnit Testing
-Architecture Components
-Android Jetpack Libraries