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.

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.

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.

4. 🔥 Invest in Standards, like FHIR.

🤝 We Build Together. More ready & responsive than ever.

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.

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.

Wiki

• Completed review of existing automated tests and drafted new test coverage tickets for manual tests that can be automated

• New proposed tests for automation

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

• Protocol here

• 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

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

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

Via Ozone Interop Layer. (Odoo already existed)

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 | ___

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.

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

i18n Date Picker: Ethiopian Calendar + more

O3 Labs v2: Order, Status

O3 Labs v2: Order, Status

O3 Labs v2: Result

• React Form Engine feature parity with existing O3 Engine

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

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).

• Further improvements to Community infrastructure and services used to keep OpenMRS community online and supported.

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

• proposed tests for automation

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)

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

Status:

See Billing Squad details on the Squad Dashboard.

See Inventory Squad details on the Squad Dashboard.

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

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

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

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

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

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

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

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

This will be a great addition to O3, 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

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

Talk post | Epic | Tech framework done

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.

3rd party pen test completed of the O3 RefApp. Fixes ongoing.

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

• 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.

Major Liquibase upgrade that gains better security and stability

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

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

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. 

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:

IPD Requirements Gathering

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

Offline EMR Use (No Internet/Power Loss)

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

GSOC project?

Backend Dev work complete; UI work next.

E.g. https://openmrs.atlassian.net/issues/O3-3856

Horizontal Scaling Bottlenecks

API Architecture Planning for new endpoints to reduce load from several particularly bottlenecked endpoints.

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)

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 EMR-distro like Billing, Inventory, Labs, and Data Viz). Plan is for a FHIR-based approach.

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)

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: _______

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?"

"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. 

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

Interested: PIH

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

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.

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