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.

3.x Address Hierarchy Component

Status:

i18n Date Picker: Ethiopian Calendar + more

Status:

3.x Appointments

Investigate and bring over bahmni appointments into 3.x esm; remove atomfeed dependencies. Incorporate w existing Appointments module in 3.x. 

For Facilities: Configure what appointments are provided, and how they can schedule pts. stats, lists. Workflow review. 

For Providers: Handling Mother-Child appointments smoothly (same date). Create, edit, update, scheduling decision support (1 day instead of 3 days in a row), cancel. 

Smaller scope way to intro 3.x. 

Status:

Service Delivery Queues & Clinic Workflow Queue & Clinic Dashboard improvements

A 'snapshot' of active visits and patient priority levels. Goal is to improve clinic workflows / service delivery queues, and team communication, starting with Outpatient clinic workflows. 

Status:

Offline Mode for CHWs/Outreach

Registration, Forms ready for field use offline

Status:

Medication Dispensing

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

Designs:

Status:

Configurable Lab Results table view

Configurable extension to show labs of interest in a table (timeline) view. (e.g. "Just HIV-Related Labs")

Status:

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. 

Status:

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: 

Lab Orders

Status:

Lead:

Use case & design input from 

3.x Performance Enhancements

Status:

Referrals

3.x UI to send and receive referrals. (Discussion topic coming for all orgs on Feb 14 3.x design call.)

Status:

Edit Existing Forms

Status:

Group Sessions / Group Visit Management

3.x feature for Group Sessions, starting with Mental Health group sessions. Aka Bulk Data Entry, Line List style, Tabular data entry view. 

Status: 

First Form-Embeddable Widget: Address Hierarchy

Status:

ICAP-Ethiopia: OHRI/3.0 Go-Live (~ July 2022)

Embedding Allergies/Conditions etc in Form Workflows

Status:

Lead:

Use case & design input from: TBC (new)

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: Mekom, ICRC (in H2)

High Risk Patient Package

Package for collaborative care for higher-risk HIV patients. 

Status:

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)

Use Case Gathering: Offline Mode for Sites

Rules Engine

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

Interested: Ampath, ICRC, Mekom

Print

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

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)

Autosave a Form Draft

Interested: _______

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. 

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.

Using OCL/Dictionary Manager to manage all PIH concepts

Status:

musa solomon derrick

3.x Form Builder: UgandaEMR pilot

Easier way of generating forms, via UI. Provide label names + connect pre-defined concepts –> generates JSON file. Finding way to deploy JSON file (Hx of using XML).

EMR Packages: Tech Definition & Schema

A way to add content (forms, concepts, custom widgets etc) to easily add new program areas to your EMR (e.g. Maternity Package)

Input from:  

Status:

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. 

Status:

OCL OpenMRS Import feature

An answer to "How do I get my legacy metadata into OCL?"

Status:

OCL Module: Diff Check workflow

"Here's what will change" UX/UI when subscribing. 

Status:

OCL Module: Automated tests for different data types

Iniz support for Reports

 Interested: PIH

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.

FHIR Requirements analysis for Ethiopia CDR & API improvement work

Status:

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

FHIR API Support for Terminology Services

Currently dependent on REST API for all things concept or terminology related

Needed for 3.x dynamic patient list queries to be entirely FHIR based.

3.x test results depend on hybrid of FHIR & REST due to this.

Support for OpenMRS Attributes

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

Odoo integration for Physical Rehabilitation

e.g. Creation of prosthesis and financial / patient billing

Odoo for Pharmacy

Odoo integration for Billing

Odoo integration for Bed Management

API to get obs for Concept Trees

E.g. for Lab Filters/hierarchies. Method to get set of obs based on a concept tree. 

Actively being used in the new Lab Trees feature!

Data Model to support Service Delivery Queues

Support for dynamic vs static lists of patients.

Platform 2.5 Release

• Support for Tomcat 7-9.
• Make Orders, Allergies, Diagnoses, and PatientState form recordable and encounter-able. 
• Administration via REST. 
• User settings: store larger strings in DB.
• Groundwork for future ReferralOrders support.

REST API Test Coverage

Thorough Test Coverage: Live OpenMRS QA Dashboard

Automated Workflow Tests applied throughout products

RefApp 2.12 Release

38 of 42 modules updated. Includes the SPA module that unlocks Microfrontend capability.

Dockerizing development and deployment of OpenMRS

Best practices for OMRS development and deployment. Key to enabling Packages vision and CI. 

Embracing Greater Modularization of the Platform

Breaking core into modules, & trying to improve upgrade process

Support Referral Orders

Event Bus

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 

 Interested: Ampath, UCSF?

Access Control List support

Order Templates

E.g. Common Rx's

Interested: Ampath

Order Sets

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

Additional Security Automated Test Coverage