/
Previous View of Product Roadmap (2024)

Previous View of Product Roadmap (2024)

Vision

Strategy Themes - and the 4S’s (Stable, Scaleable, Sustainable, and Secure)

Better Care through Better Information.

Stronger digital health ecosystems in countries.

Improve healthcare for millions of people in challenging environments around the world, by empowering Healthcare Workers with the tools they need out-of-the-box.

🎁 Ready for Implementers to scale their work. (Stable)

  1. 📋 Feature-rich EMR for Outpatient management.

  2. 🏃 Easier deployment. Set-up wizard to get you started; tooling to make life easier when you scale.

  3. 📊 Sample Reports & some Clinician-friendly Data Viz

  4. 🏥 Facility-Wide. Growing into Inpatient care. Prioritizing integrations with non-EMR care areas, like Labs, Pharmacy, Inventory, and Billing/Insurance.

  5. ✅ Tested, Trusted Releases. Rapidly see your bug-fixes & new features in global releases. Mandatory test coverage; test automation in PRs and pipelines; regular release cadence with clear notes and stable versions #'s.

🧑‍⚖️ Ready for eHealth Leadership. (Scaleable)

  1. 🏛️ Aligned with Government eHealth Leaders' initiatives (eg HIE, UHC, charge-capture)

  2. ☁️ Cloud-Friendly. Without leaving last-mile sites behind.

  3. 🔒 Invest in Security. (Secure)

  4. 🔥 Invest in Standards, like FHIR.

🤝 We Build Together. More ready & responsive than ever. (Sustainable)

  1. Squads. Work mainly happens through Squads, with Global Support Team support as-needed.

  2. 📖 Docs, 🎓 Academy. Documentation is mission-critical to working together and growing our community.

  3. Vibrant Community: Events and local networks. In-person and virtual connection opportunities. Build local/regional communities.

  4. Dedicated Mentorship Time. We mentor change agents.

Flexible Content for Whole-Patient care. (Scaleable)

  1. 🩺 Ready-to-Go Content.

  2. ✏️ Non-Dev Friendly Content tooling. Form building, clinical terminology management, content sharing. Increase what can be done where there’s not as much dev support available.

  3. 🛑 Decision Support that optimizes for pt safety.

  4. 🈶 In Many Languages. Scale through Translation, a translator community.

Product Roadmap

About: This is a dynamic space, open to feedback; a home-base where anyone, especially day-to-day Implementers interested in the OMRS roadmap, can see at a glance some key initiatives going on around our community: what's happening, who's putting resources in, what needs more support, and where there are specific opportunities to join.

Subscribe to Updates: To follow new Roadmap additions or changes, subscribe to this page. Short Link to this page: om.rs/product

Contact: Have an interesting initiative you want to see on the Community Product Roadmap? Contact Director of Product @Grace Potma at: grace@openmrs.org and/or Community Coordinator @beryl at: beryl@openmrs.org. We'd love to hear about your priorities and current focus areas!

Criteria: How items get on this Community Roadmap

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)  

Done

Recently completed (<1yr)

Now

Actively being worked on, in-progress

 Next

Emerging as strong community priorities

❄️ Icebox

Ideas and needs, but no active work yet

Done

Recently completed (<1yr)

Now

Actively being worked on, in-progress

 Next

Emerging as strong community priorities

❄️ Icebox

Ideas and needs, but no active work yet

3rd party pen test completed of the O3 RefApp. Included OWASP Top 10 review. Compliance Certificate achieved!!

OMRS IncUW DIGI PIH Fellow

MVP of this is done and available. (Requires server that provides IPS’s, can test using HAPI community’s test instance; this successfully demonstrated this functionality works to receive data from a system that knows nothing about OpenMRS at all). Which will help connect patients’ histories across sites and share data when there is more than one health information system creating relevant clinical data.

Wiki | Talk | GitHub

UW DIGI

Major Liquibase upgrade that gains better security and stability

OMRS Inc Volunteers

Major breaking changes happening in Java community. Support for Java 17 in OMRS core also gains us greater security.

OMRS Inc Volunteers

OMRS IncUW DIGI

Talk Post

OMRS Inc

  • Created Release QA Team, for careful manual review of EMR before every release

  • Protocol here

OpenMRS Inc PIH Palladium Intellisoft Mekom Volunteers

  • The latest version of the O3 EMR loads faster on low-resource devices

  • The latest version of the O3 EMR uses substantially less bandwidth (which is especially helpful for places that pay for bandwidth use). 

100% of code strings were translated into French in Q3 2024!

Implementers can now be trained on the User-Friendly Builder through the new Virtual Academy Course: O3 Form Builder

Improved how EMR displays numeric values that are out of range: more clear and consistent across whole application.

Archived hundreds of out-of-date pages and improved Wiki Information Architecture (Article)

 

Cloud/Cluster Deployment Guidelines on Wiki Cloud/Cluster Deployment

  OMRS INC UW DIGI

Improvements merged; Migration guide for Implementers here

Status: Rolling OUt 

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

  OMRS INC  Fellows

Ability to print things from the EMR, e.g. HIV Clinical Summary

 GSOC '22  PIH

Via Ozone Interop Layer. (Odoo already existed)

Mekom Palladium-Ke

Tech Definition & Schema

Plug-In Technology completed and working. Globally reusable templates and kits for disease- or service-specific areas, that plug into OpenMRS, with concepts/terminologies, forms, and apps (e.g. HIV Package).

Wiki | Talk Forum | ___

UW DIGI OMRS INC

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). users don't have to leave a form to record data in these components.

UCSF-TAP OpenMRS INC UW DIGI METS

HFE forms can now be opened in the O3 Form workspace!

PIH

i18n Date Picker: Ethiopian Calendar + more

OMRS INC  ICAP-ETHIOPIA UCSF-TAP UW DIGI

O3 Labs v2: Order, Status

UCSF-TAP UW DIGI

O3 Labs v2: Order, Status

UW DIGI UCSF-TAP 

O3 Labs v2: Result

UCSF-TAP OMRS INC SONDER

O3 UI to enable Phamacists to review drug orders and mark dispensing status. Now live in Sierra Leone!

Support things we don't currently support in OMRS data model - e.g. pt phone numbers (current support is fragile) - Completed through a GSOC project

 GSOC

Moved from Hibernate API to JPA (Java Persistence API) which attracts talent because this is far more commonly used by backend engineers worldwide (since older technology is not as exciting to work on).

OMRS Inc

OMRS Inc Volunteers

 

UW DIGI OpenMRS Inc

Separate RefApp software releases from Content releases → means demo data will need to be bundled separately, available like an Add On, and versioned

Currently, there are no clear guidelines for Implementer BAs/PMs on how to wisely create, manage, and edit concepts / terminology.

Contact Person: @Veronica Muthee

OpenMRS Inc

Upgrade OpenMRS.org with better content and more modern UI.

Palladium

Interested: PIH

Often, pharmacies (especially at smaller sites) do not have a particular drug or drugs that the patient needs. In this case, the Pharmacist needs to print the prescription so the patient can take this to a different public or private pharmacy to receive that drug.

OMRS Inc UW DIGI

Make OpenMRS-collected data easier to use for Researchers and Program Decision Makers. (1) Translate OpenMRS to the OMOP Common Data Model and (2) set up a re-useable tooling pipeline for data to be extracted.

Wiki: https://openmrs.atlassian.net/wiki/x/AYBpDw

UW DIGI OpenMRS Inc Volunteers PIH

Swagger Docs Update: Updating this to use latest version of Swagger, to make more useful → Gives reliable docs for devs on what our REST API can do (instead of maintaining manual docs, auto-generate a library)

PIH MEKOM Sonder

Retrospective Data Entry to enable management and editing of past visits & encounters, chart corrections, etc., in O3 UI.

Status: In Design 

PalladiumMETSUCSF-TAP

See Billing Squad details on the Squad Dashboard.

METSPalladiumUCSF-TAP

See Inventory Squad details on the Squad Dashboard.

OpenMRS Inc Volunteers

Bring into 1 place all config & devops & dev & setup docs. Make easy to find.  

OMRS INC

Backend done; UI in progress. We previously had no auditing around views, or changes: if a form was filled out multiple times, we'd only have information on the first time and the most recent update.

Talk Thread: https://talk.openmrs.org/t/new-audit-log-system-for-openmrs-seeking-feedback-and-suggestions/43137

Mekom

3.x UI to order Referrals, Procedures, and Materials in the order basket.

PIH Mekom

UI to manage location and status of patients across beds in wards, including Moms/Babies, and multiple patients in 1 bed.

OMRS INC

Ongoing fixes and improvements to the new O3 Form Builder GUI; Substantial refactoring to simplify and improve codebase. Adding Markdown editing. Epic here. 

UW DIGI OMRS INC UW DIGI-CIV OHRI/UCSF Palladium

Pt lookup on Registration page. National ID / HIE / CR Client Registry / MPI Master Patient Index system integration via FHIR Protocol.

Todo: Backend Module & right API

Demo Video | Forum

OMRS INC

implemented ability to change a range depending on a given variable (eg age, sex) in flexible way; can be done with bare minimum change of data model. Also implemented in our data model FHIR’s obs reference ranges which enables OpenMRS to receive reference ranges from an LIS system (instead of disregarding this). Obs Interpretation: Based on those ref ranges, can apply whether this is Normal, Low, Critically High, etc. This is now part of the data stored in the DB. Overall this means that Pediatric and Elderly lab/vitals range differences now supported, warning flags now supported better.

Wiki Docs

UCSF Mekom

A sample software distribution that demonstrates how integration of OpenMRS with external systems can be achieved. https://github.com/openmrs/openmrs-distro-his

 

ICRC

Goal: identify needed improvements and additions to the FHIR2 Module, so OpenMRS is interoperable with other solutions.

How: Using the Android FHIR SDK from Open Health Stack to set up an outreach app that exchanges data with OpenMRS EMRs via FHIR.

OMRS INC

In the patient chart, when you go into “Past Visits”, that list can be slow to load. Jayasanka is working to improve this.

MSF / Madiro

Ozone team is open-sourcing the integration between OpenMRS and Superset.

Mekom

Talk post | Epic | Tech framework done

OMRS Inc Volunteers

Automating: QA Release build, run E2E tests on all repos when esm-core is released, stricter typechecking. To Do: Test with 3.2-rc, then update O3 Release Guide Docs.

UW DIGI OMRS Inc Mekom

Horizontal Scaling Bottlenecks

API Architecture Planning for new endpoints to reduce load from several particularly bottlenecked endpoints. Complex, highly fragile work.

Wiki, Talk

SEEKING Open

Use MPI integration to find and record patients, and exchange health records through central DB(s). May involve tracking patient consent for data-sharing.

Palladium Contact: @Donald Kibet & @Kennedy Makombe

A combination of Bed Management (ward app) + unique forms + ADT (admit body, discharge to family, transfer for investigations)

Palladium Contact: @Antony Ojwang & Fredrick kioko

Interested: PIH

Fix issues with API performance, found via Automatic Load & Performance Testing. (Speed of loading: Locations, and Visits view)

Problem: Users have too many choices to pick from (e.g. drug orders, labs, diagnosis options, etc). User-based favorites can improve the UX and speed.

Contact: @Grace Potma

Wiki: ___ Epic: ___

OMRS Inc

Often clerks need to print an ID card after registering a new patient.

Interested: PIH, Madiro

Interested: PIH

Order Template Modelling E.g. Common Rx's 

GitHub Example

Interested: UCSF, PIH, Mekom

Support for Sets of anything that's order-able (e.g. COVID assessment set can contain Meds, Labs, Referrals...)

Interested: PIH, Mekom, Sonder, OpenMRS Inc, FAIMER

Clinical Views

Ability to add specialized program- or condition-specific views. Ideally, able to update config easily to add more - e.g. represent clinical view w/ JSON structure. 

UCSF  OMRS INC

Generic Encounter Widget 

Reuseable version of a common widget, powered by config that's easily editable (e.g. if you want to change columns & data shown in a table)

Orgs: SEEKING OMRS INC

IPD Requirements Gathering

Collecting further requirements for inpatient care, e.g. MAR. PIH  MEKOM UCSF MSF

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

METS

METS

GSOC project?

Backend Dev work complete; UI work next.

Currently the DD Module causes slow startup times because of how patients are being created & data loaded. Idea: Generate the data once in it's own docker container instead of generating every time we start an instance. Largely coming from appointments module. The real fix is content packages, so we can remove the Demo Data from the base distro so everyone doesn't have to run the Demo Data when they start up the application. (Only 50 pts, but slows down startup by ~10 minutes; additional errors coming from Bahmni Telecom module)

  Not Started 

Remove because this feature is significantly underused and slow (it's faster to stop, add an OMOD, and re-start your instance than it is to upload an OMOD on-the-fly at run time), and because the OMOD upload fx has security implications. The hope years ago was that Spring support would make this a more stable, performant feature, but this didn't happen, and it is very underused.

In order for the EMR-distro vs HIS-distro vision to work, the way data is served-up to the frontend needs to work smoothly & function the same way - otherwise neither application will be sustainable (especially with HIS-Lite fx being added to the EM🔥R-distro like Billing, Inventory, Labs, and Data Viz). Plan is for a FHIR-based approach.
Funding Needed

 

 

Bulk Retrospective Data Entry is regressed and unuseable in the O3 EMR distro. Very helpful for RDE so should be resurrected.

Interested: ICRC

  • Dealing with concept overlaps, i.e. the same concept being a bit different in 2 different packages

 

Show & recommend specific forms based on information about Patient or Program Enrollment (eg show ANC forms for ANC visits); likely specified via Form Schema & executed via Form Engine. Very challenging engineering - would need context, workflow engine. In meantime the Tabbed Table Component from OHRI helps meet this user need to some degree. Future ideal is "If patient is [obs] = X and [visit type] = Y, then show these foms".

"Prevent Pt Duplicates" flow in Registration Page. Possibly should include merging pts. Should leverage pt-duplicate-detector in core.

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

 

not started

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)

 Open not started

(Interested: Mekom, ICRC, UCSF)

Interested: _______ not started

 

Palladium recommends this OMOD be reviewed as it becomes key in CDS / patient flag calcs and reporting.

Currently not obvious in UI and underutilized.

 

 

OCL OpenMRS Import feature

An answer (and clear documentation) to "How do I get my legacy metadata into OCL?"

Regenstrief FellowsPIH (testing) 

"Here's what will change" UX/UI when subscribing. (Possible GSOC Project)

Map OpenMRS Order statuses to FHIR

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

UCSF Regenstrief

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

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

  UCSF-TAP Regenstrief

Interested: PIH Open

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

OpenMRS Inc CHT Not Started

Goal: To expose OMRS Concept Dictionary through the FHIR API. Currently dependent on REST API for all things concept or terminology related. E.g. Needed for 3.x dynamic patient list queries to be entirely FHIR based; to convert all calls into individual concepts.

Open Not Started (Interested: UW ITECH, CIEL)

Event bus so that when things happen, they trigger a new process(es) to start. (e.g. patient finishes visit, needs to be moved from one Service Delivery Queue to another) - see OHRI example outlined here re Patient State vs Workflow State 

Roadmap here

   OMRS INC

 

Ian has a vision of having a Demo version of the RefApp that, in addition to using an OMRS DB, also pulls data from an external demo FHIR store. This would create something similar to the his-distro, but specifically for showcasing FHIR interoperability, such as IPS data exchange.

 

UW DIGI

  • Test Automation coverage requirements tool in progress to make it easier to write tests for our code. Should make it easier to write unit tests. Slow grind being done by Ian.

 

 

 

 

 

 

 

 

 

 

 

 

 

Timeline estimates: (e.g. Q1/Q2/H1/H2 etc) are subject to dynamically changing resources in our opensource community. They refer to a calendar year timeline (eg Q1 ends and Q2 starts when April begins, etc).

Product strategy: Adopted from Gibson Biddle’s DHM Model. Sustainable, Stable, Scaleable, and Secure are our main themes; however, good product strategy answers the question, How will your product delight users & community members, in hard-to-copy, sustainability-enhancing ways?”