We're building a new frontend for OpenMRS via a collaborative process that leverages modern frontend technologies. These technologies will enable OpenMRS users and developers around the world to share more frontend functionality, reduce duplicated effort, and have a better user experience. 15-min overview video of the vision here.
O3 Resources to Know
Connect With Us
Want to contribute? Join our squad!
Strategic Fit for OpenMRS
Decision Making Process
We use an RFC (Request For Comments). Major decisions are made through GitHub pull requests where anyone can comment.
Where can you find us ?
Slack Channel: https://openmrs.slack.com/archives/CHP5QAE5R
(Join our Weekly Calls to become part of our focused OpenMRS 3.0 Squad)
Weekly Squad Call
Thursdays at 4pm UTC / 9:30pm IST/ 7pm EAT / 5pm CET / 11am EST / 8am PST.
Join info: https://om.rs/zoommf
What Happens On These Calls:
- Dev Demo: latest work done (if it’s the end of a sprint, we also do the full sprint demo)
- Dev Discussion: Any blockers or things to clarify
- Product Priorities: We clarify any epics or issues that need more ownership or to be prioritized
- 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: 3.x Squad Notes
Jonathan Dick (AMPATH)
Grace Potma (OpenMRS)
Dimitri R (Mekom Solutions)
Burke Mamlin(Regenstrief Institute)
Ciarán Duffy (Sonder Design & AMPATH)
Paul Adams (Sonder Design & AMPATH)
Florian Rappl (Smapiot & Mekom Solutions)
Brandon Istenes (PIH)
Developers, DevOps, QA, BA:
Nikita Malyschkin (Smapiot & Mekom Solutions)
Dennis Kigen (AMPATH)
Donald Kibet (AMPATH)
Emmanuel Nyachoke (Mekom Solutions)
Samuel Male (UCSF)
Romain Buisson (Mekom Solutions)
Mike Seaton (PIH)
Daniel Kayiwa (OpenMRS)
Eric Achillah (AMPATH, PM & QA)
Jonathan Teich (BA/Clinical feedback)
Ian Bacher (Brown) (Backend & FHIR support)
Bett Kipchumba (AMPATH) (Backend & FHIR support)
(1) Plug & Play Architecture: The frontend stack we're building on using Micro Frontends
Goal: Frontend architecture designed for extensible and configurable apps and widgets.
Our MF Framework is Single-SPA: We chose to use single-spa, the most popular microfrontends framework, as the basis upon which to build this new frontend architecture.
(2) Implementer Tooling: Tooling we're building to make MFE easier for implementers to configure
Goal: Enable both developers and non-developers to easily configure their distribution, and re-use that configuration rapidly.
(3) Building a Friendly, Modern UX in RefApp v3.0
Goal: 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. Our OpenMRS Reference Application 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.
We're currently in the process of implementing new designs that leverage the carbon design system for our reference application. (More on why we chose carbon here).
We're not starting from scratch though. Rather, we're migrating from an old set of designs (and an old style guide) to the new designs (and now migrating to use Carbon Design System as well - not all the Carbonizing work is done). As such, it should not be unexpected that gaps will be found in documentation, incomplete implementations, broken functionality and so on as we move to get everything back in order.
Our Design System:
Our Simple Style Guide for reference: