All of these items are:

• being conducted in a public community process, with involvement & investment from 2+ Organizations
• being shared with /omrs/5 facilitators, and are receiving some degree of dedicated support from OpenMRS Inc
• likely to provide wide community value (i.e. fit under the definition of "Shared Assets" for community)  

To suggest an item for the Community Product Roadmap, simply contact Director of Product Grace Potma (grace@openmrs.org) - we'd love to hear about your priorities and current focus areas.

Adopted Carbon Design

Updated 3.x Frontend to use 3rd party design system. Result: Faster design & development outputs. 

Share Frontend Widgets with Plug-and-Play Architecture 

Microfrontend framework completed; enables implementers to re-use others' frontend features. 

3.x Guide for Developers

Step by step guide to the new Design System & Microfrontend architecture. Will help Devs implement 3.x for their org, or contribute to Squad.

NCD Use Cases & Design Research

User Research, Designs, & Testing to validate and prepare EMR for NCD care context. E.g. NCD-specific widgets and sections of Patient Chart, NCD Peer Support.

Status: 

O3 RDE

   Retrospective Data Entry to enable management and editing of past visits & encounters, chart Registration App Re-Do

Reg page is one of first apps new users/devs look at, and wasn't meeting requirements or code expectations. This refactor makes it easier for implementers to adjust the Registration feature to add/change things as needed. eg handle site- or org-specific field requirements, accept mini-apps like address hierarchy

Orgs:

O3 Form Recommendations

Show & recommend specific forms based on information about Patient or Program Enrolment (eg show ANC forms for ANC visits); likely specified via Form Schema & executed via Form Engine

O3 Labs v2: Order, Status, Entry, Results

Interested:

Status:

React Form Engine feature parity with existing O3 Engine

Roadmap here

Status:

Medication Dispensing

2.x & 3.x UI to enable Pharmacists to mark drugs and fully or partially dispensed. 

Pilot plan in Sierra Leone for Oct 2023

Status:

Content Templates & Toolkits: Packaging and Ingestion Method

Angular Engine maintenance

Roadmap here

O3 Docs Harmonization

Bring into 1 place all config & devops & dev & setup docs

Interested:

Implement Tasks (to be driven by CDS)

Initial designs here; we would like to get these done. First legos to support decision support. 

IPD Requirements Gathering

Collecting requirements for inpatient care, e.g. Bed Mgmt, MAR.

Offline EMR Use (No Internet/Power Loss)

In-form Appointment Date Checker

Endpoint convention in OMRS to connect (e.g. "on this day, how many appointments already booked?")

Interactive Forms: Embedding Orders, Conditions...

e.g. Starting an Order within a Form Workflow. Forms/notes become the centring piece for teams - we need to figure out how to represent not just data collection, but also embed widgets into the process (so that user doesn't have to click around the EMR to find the information they need while also trying to do a form). 

Interested: ICRC

Embedding Allergies/Conditions etc in Form Workflows

Status:

Lead:

Use case & design input from: TBC (new)

Rules Engine

(e.g. for Workflow State management; Clinical Decision Support)

Interested: Ampath, ICRC, Mekom

Autosave a Form Draft

Interested: _______

Patient Lists: Automated (Cohort Builder)

(1) Query for patients who meet a certain criteria, and (2) automated adding/removing of patients from this list (so it's automatically maintained). 

E.g. "show me all Patients who missed med pick up..."

E.g. "show me all Patients who missed their appointment..." 

+ Actions on that list (e.g. change patient status)

(Interested: Ampath, UCSF)

Referrals

3.x UI to send and receive referrals.

Status:

Bed Management

Team Communication

e.g. Notifications between team members (within UX of System wide / Global notifications; for 1 user but not about 1 patient)

OpenMRS Reporting UI

Create a UI that would be able to run an existing report with parameters (if applicable), select the output format and download it

Registration App Re-Do

Reg page is one of first apps new users/devs look at, and it's not meeting requirements or code expectations. Need to re-design, re-architect, & confirm requirements - eg to prevent pt duplicates, handle site- or org-specific field requirements & allow enable-whens, accept mini-apps like address hierarchy, handle Pt Lookup on Registration Page

handle National ID or Insurance system integration...

Status:

Merging the O3 Monorepos for better DevX

Reactify & Carbonize O3 Form Builder

GUI tool now available in the O3 RefApp admin tools!

Using OCL/Dictionary Manager to manage all UgandaEMR concepts

Iniz support for OCL & Dictionary Manager work

Copy & Customize a CIEL Concept

Able to re-use a CIEL (or other curated) concept instead of re-creating it manually: copy it and make the non-breaking changes you needed (e.g. change answers, add translations, etc). 

OCL Module: Multi-language support

Updating translations for concept updates or new subscriptions that have many languages.

Input from: UCSF, MSF

Dictionary Manager webapp (aka OCL for OpenMRS)

MVP live for production use. See: Intro video; and demo video. 

3.x OpenMRS Forms: Form Management for Non-Tech folks

A new Form Builder & Form Engine for OpenMRS, using open source code used by OpenMRS implementer for 5+ years. Allow non-coders to set up clinical forms. 

Lighter Deployment

Simpler deployment packaging (3.x RefApp will use a much lighter-weight set of modules)

OCL Module Improvements

• Bug fixes related to error messages

Designs for Implementer Tool: EMR Setup UI for Non-Tech folks

Designs to enable: Non-tech users can set up a 3.x EMR in a friendly, no-code UI, similar to designing a website.

UI Feature Improvements to Form Builder GUI

Ongoing fixes and improvements to the new O3 Form Builder GUI. Epic here. 

OCL Module: Automated tests for different data types

Using OCL/Dictionary Manager to manage all PIH concepts

Status:

Use mappings in a form instead of the concept UUIDs

Goal: Demo a form that’s defined and rendered through mappings (not UUIDs). Eg if a country maps to OHRI concepts → Need ability to map

Shared Basic Lab Dictionary with OpenELIS

Collaborated with OpenELIS to establish a shared Basic Lab dictionary collection in OCL, with CIEL codes mapped to LOINC. Public here.

Advocacy with other Global Goods to adopt OCL to decrease Implementer dictionary maintenance headaches

Significant progress in 2023: large presentations and 1:1 demos at: OpenHIE in Malawi (May), GGIS Summit in Tanzania (June). Result: 2 Global Goods newly working to adopt OCL; 2 others actively considering.

FHIR 101 Documentation Improvement

Clarify OMRS' strategy and tooling for FHIR, how to find supported resources, and what to do to add more. Public here.

FHIR Gaps Review

Using 3.x RefApp, check for areas where REST API is being used where FHIR either could be used or needs support (Done, Doc Here)

FHIR Module Upgrade 

Added support for Immunizations.
Note: The FHIR Module already enables the export of OpenMRS data into FHIR format, to help integrate with other systems use FHIR. 

DHIS2 Connector Module

Posts aggregate data from OpenMRS to DHIS2, and gives implementers a User Interface for an easier-to-set-up OMRS to DHIS2 pipeline, that doesn’t need manual code fixes every time there’s a change to reporting indicators. Fixed so this can work in production systems, added automatic data sending, and added support for custom period types.

Scale-ready ETL Pipeline to FHIR-based tools: Ampath pilot of Analytics Engine.

Integration Catalog

On OMRS website, help answer the question “Does OpenMRS integrate with…” and give implementers practical resources to follow if they need somewhere to get started. Draft here. 

Mapping OpenMRS Order statuses to FHIR

Send a case report from OMRS system to a central repo. 

Send data to Central Repository for Case Based Surveillance

Send a case report from OMRS system to a central repo. 

Lab Viral Load Data Exchange

Based off of FHIR IG. Proof of concept completed. More to be done for full data exchange of lab request and case report.

FHIR Implementation Guide (IG) - Supporting OHIE Facility Registry IG

Goal: Finish & genericize the ITECH FHIR IGs built for Labs, Lab Workflows, and Facility Registries

Identity & Facility Management

Get iSantePlus Client Registry & Facility Registry workflows set up with FHIR in iSantePlus working in OMRS-core (using FHIR-based workflows)

Lab Exchange

Get iSantePlus lab exchange module to work in OMRS-core (connects to id & facility mgmt to i.d. right pt and right facility) (using FHIR-based workflows)

DB Sync

Medic Mobile / CHT Reference Integration

A sample integration, both flow and tech, that implementers can easily re-use. Working ad-hoc with CHT Lead Architect on this.