Wiki Spaces


Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack


Page tree
Skip to end of metadata
Go to start of metadata

Quick Start Links

Want to get started contributing fast? Here are the key links for you to know. More about how to Join Us below.

view DEMO SITE  u: admin p: Admin123

Where to find work

checkbox Live Tickets Dashboard   backlog Team Jira Board   configure Key GitHub Repos


new-edit Designs Ready for Development  

How to Work with the Designs

video-filled Zeplin how-to for devs   camera Styleguide (Re-useable Styled Components)

Dev Quick-Start Guides

add-item Slots Explained   video-filled Dev Tutorials   info Dev Guide

Want to contribute? Join our squad! 

  1. Review the high-level guidance on this page
  2. Intro: Introduce yourself at our Squad #microfrontends Slack channel (Note: You will first need to create an OpenMRS Slack account by going to
  3. Dev Guide: Use our Dev Guide to get started. Look for answers there.  info Dev Guide  If you are still unsure about a question, ask our squad in the #microfrontends slack channel.
  4. Find Intro Tickets: Intro tickets you can use to start contributing are available here:  checkbox Open Issues to Get Started This dashboard shows the latest Intro and Non-Intro tickets that need to be taken on to support the MicroFrontend work. This also shows the different features (via Epics) that are currently underway. 
    1. Note: To view the designs in detail, you'll need an invite to our Zeplin account. Ask Grace Potma& Eric Achillah for help - @grace & @Eric on Slack. Make sure you also review our short How to Use Zeplin video.
    2. Please assign tickets to yourself before starting work. This helps avoid confusion and accidental duplication of work. Double-check the ticket's Epic for other related work before working on things outside the described scope of the ticket - you may accidentally be replicating a feature someone else is already working on.
  5. Meet Us! Join our weekly Squad calls on Thursdays (info under Where You Can Find Us above) (GCal invite here). 
  6. Sprints: Become part of our regular sprints. This will happen naturally as you join our calls, though you don't need to join all calls in order to participate. Here is our active board. We use epics to break down features and widgets, and we typically work in 3-week sprints.  board Active Sprint Board backlog Squad Backlog & Sprints

Project Overview

We are working on 3 main goals that will unlock better frontend collaboration across OpenMRS:

(1) Plug-and-Play Frontend Architecturemakes it possible for frontend feature development to be shared across teams, organizations, and distributions

(2) Implementer Tooling: makes it easier for non-developers to configure the product to the needs of their organization or site

(3) A friendly, modern, consistent User Experience: with a professional UX framework, this further unlocks frontend feature-sharing, and creates a 3.0 option of the OpenMRS RefApp





Strategic Fit for OpenMRS

video-filled Why Microfrontends?

info High-Level Strategy

info SPA Proposal Explained

info Detailed Technical Vision

Decision Making Process

We use an RFC (Request For Comments). Major decisions are made through GitHub pull requests where anyone can comment.

info OMRS Frontend RFC

All GitHub Repos related to this project:

graph-line Overview of GitHub Activity

Where can you find us ?

On Slack

Slack Channel:

(Join our Weekly Calls to become part of our focused Microfrontend Squad) 

Weekly Squad Call

Thursdays at 4pm UTC / 9:30pm IST/ 7pm EAT / 5pm CET / 11am EST / 8am PST.

 Join info:

What Happens On These Calls:

  1. Dev Demo: latest work done (if it’s the end of a sprint, we also do the full sprint demo)
  2. Dev Discussion: Any blockers or things to clarify
  3. Product Priorities: We clarify any epics or issues that need more ownership or to be prioritized
  4. Design Updates: We wrap up by looking together at the latest design work, so we know what designs are soon to be ready for development 

Recordings and Notes from our regular squad meetings are here: Micro Frontend Squad Notes


Project owners:

Jonathan Dick (AMPATH)

Grace Potma (OpenMRS)

Dimitri R (Mekom Solutions)

Team members:

Florian Rappl (Smapiot & Mekom Solutions)

Nikita Malyschkin  (Smapiot & Mekom Solutions)

Brandon Istenes (PIH)

Dennis Kigen  (AMPATH)

Donald Kibet (AMPATH)

Burke Mamlin (Regenstrief)

Ivange Larry Ndumbe (Mekom Solutions)

Samuel Male (Mekom Solutions)

Romain Buisson  (Mekom Solutions)

Mike Seaton (PIH)

Daniel Kayiwa (OpenMRS)

Eric Achillah (AMPATH)

Jonathan Teich

@Ciaran (Sonder Design & AMPATH)

More Information

(1) Plug & Play Architecture: The frontend stack we're building on using Micro Frontends

Extensible, configurable and independently deployable frontend features. Get your frontend live and updated fast. Frontend architecture designed for extensible and configurable apps and widgets.

video-filled Tutorial

configure GitHub

info Dev Guide

Microfrontends are in-browser javascript modules (ESMs) that provide application UI. To see available microfrontends including links to their documentation pages, check out all our Microfrontend repos here:

Core Microfrontends

These are microfrontends that are part of openmrs-esm-core. They are tightly coupled to the base application.

(2) Implementer Tooling: Tooling we're building to make MFE easier for implementers to configure

video-filled Demo

configure GitHub

(3) Building a Friendly, Modern UX in RefApp v3.0

Create a better means for building out a shared UI. Modernizing the entire RefApp frontend, using Carbon Design System for UI consistency and faster dev value. Needs to become a Point of Care application, that’s modern, friendly, and works well on tablets. 

We are working on a re-design of the patient chart, starting with end-to-end support for HIV Outpatient Workflows; pilot plan ~ April 2021 at Ampath.


new-edit Designs Ready for Development

time Designs in Progress

Our Design System:

info Carbon Design System

info Rationale for Carbon

Our Simple Style Guide for reference:

camera Styleguide (Re-useable Styled Components)

video-filled How to Use Zeplin in Dev Work