🌐 Translation Guide (Docs) ✅🤖 Review all Automated Test Coverage (QA) ✅🧯 Created Release QA Protocol & Team OPENMRS INC PIH PALLADIUM INTELLISOFT MEKOM VOLUNTEERS 🏎️ 📲 Loads Faster on Low-resource devices 📶 Reduced Bandwidth usage 🇫🇷 French Translation of O3 EMR 100% of code strings were translated into French in Q3 2024! ⚠️ Upgraded Abnormal Range UI Improved how EMR displays numeric values that are out of range: more clear and consistent across whole application. Mass Wiki Update (Docs) Archived hundreds of out-of-date pages and improved Wiki Information Architecture (Article) 🏋️ Automatic Load & Performance Testing ☁️📖 Cloud Hosting Guidance & Kubernetes Testing (Docs) Cloud/Cluster Deployment Guidelines on Wiki Cloud/Cluster Deployment 🏎️ O3 Performance 5x Faster OMRS INC UW DIGI Improvements merged; Migration guide for Implementers here. Status: ROLLING OUT ⛳️ CDS: O3 Patient Flags Initial designs here; we would like to get these done. First legos to support decision support. OMRS INC FELLOWS 🖨️ O3 Basic Printing Support Ability to print things from the EMR, e.g. HIV Clinical Summary GSOC '22 PIH 🔗 ERP Next Integration Via Ozone Interop Layer. (Odoo already existed) MEKOM PALLADIUM-KE 📦 Content Packages v1 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 🗂️ Embed Orders, Meds, Allergies, Conditions in Forms 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 HTML Forms supported in O3 HFE forms can now be opened in the O3 Form workspace! PIH 📆 13 Calendars Supported in O3 Date Picker 🧺 Order History UI (for all kinds of orders) 🥼 Lab Tech Dashboard (Lite) 🧪 Simpler Test Results View O3 Labs v2: Result UCSF-TAP OMRS INC SONDER 🚒 Stable Form Engine in ReactJS, with modern RHF library UCSF-TAP OMRS INC UW DIGI METS-UG 💊 Pharmacy & Dispensing (Lite) O3 UI to enable Phamacists to review drug orders and mark dispensing status. Now live in Sierra Leone! 🤖 Support for more OMRS Attributes in FHIR API 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! 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 ✅Infrastructure Tech Debt Improved (DevOps) | 🎁 Separate Content Versioning 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 🔥🧐 Translating OpenMRS to the OMOP CDM (Common Data Model) 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 ✅🤖 Enhance O3 E2E Automated Test Coverage (QA) 📖 🤖 API Docs: Use Swagger to Auto-Generate API Docs 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) 🎁 📝 RDE: 🧐 Better Historical Visit view PIH MEKOM SONDER Retrospective Data Entry to enable management and editing of past visits & encounters, chart corrections, etc., in O3 UI. Status: DESIGN COMPLETE 💰 Billing (Lite; for small sites) PALLADIUMMETSUCSF-TAP See Billing Squad details on the Squad Dashboard. 📦 Inventory, Stock, & Commodity (Lite; for small sites) METSPALLADIUMUCSF-TAP See Inventory Squad details on the Squad Dashboard. 📖 O3 Wiki & Docs clean-up OPENMRS INC VOLUNTEERS Bring into 1 place all config & devops & dev & setup docs. Make easy to find. 🛒 Expand Orders: Add Referrals, Procedures, and Materials MEKOM 3.x UI to order Referrals, Procedures, and Materials in the order basket. 🎗️HIV Care & Treatment: Content Package 🛏️ IPD: Bed Management & Ward Management PIH MEKOM UI to manage location and status of patients across beds in wards, including Moms/Babies, and multiple patients in 1 bed. 📝 Form Builder Technical Debt 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. 🔎🔥 National Registry Patient-Lookup & Auto-Population 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 👶🍼 + 👵♿︎ CDS: Age-Based Range Support & beyond 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 🔥 IPS Support Part 1: Ingestion & Display 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 UW DIGI ⏰ Performance Enhancements: Backend & API 📊 Superset HIS integration Ozone team is open-sourcing the integration between OpenMRS and Superset. MEKOM 🎨 Icons & Pictograms throughout EMR 🎁 Automate EMR-distro releases (Smoother O3 RefApp releases) 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 ⏱️ Platform 2.7 Release with 2x-faster platform for development & start-up time! 🔒 CyberSecurity 3rd Party Penetration Test 3rd party pen test completed of the O3 RefApp. Fixes ongoing. OMRS INCUW DIGI PIH FELLOW ☕️ Java Upgrades: Java 17 Support Major breaking changes happening in Java community. Support for Java 17 in OMRS core also gains us greater security. OMRS INC VOLUNTEERS ✅🤖 Easier Test Writing tool ⬆️ Liquibase upgrade Major Liquibase upgrade that gains better security and stability OMRS INC VOLUNTEERS | ✅🏋️ Fix API Performance Issues (locations & visits) Fix issues with API performance, found via Automatic Load & Performance Testing. (Speed of loading: Locations, and Visits view) 💊+🧪+🛌 Order Sets 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 🩺 Make Clinical Views clearly configurable 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 🔧 Fix Generic Encounter Widget 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 IPD Requirements Gathering Collecting requirements for inpatient care, e.g. Bed Mgmt, MAR. PIH MEKOM UCSF MSF 🛜 Offline EMR Use (No Internet/Power Loss) 📊 OpenMRS Reporting UI 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 📊 Data Visualizer in the EMR (Lite) 📖 Docs: How to Configure the Registration Page ✅Password Change in O3 Backend Dev work complete; UI work next. ☁️ Triage & address Horizontal Scaling Bottlenecks Horizontal Scaling Bottlenecks API Architecture Planning for new endpoints to reduce load from several particularly bottlenecked endpoints. SEEKING OPEN ⏱️ Improve Demo Data Module performance implications 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 Dynamic/Production run-time Module System & simplify class loaders 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. 🔗 HIS Distro: Needs Consistent Endpoints & Data Formats 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.
FUNDING NEEDED Translation Support built-in to Form Builder | 🐛 Bug Fix Bulk RDE Bulk Retrospective Data Entry is regressed and unuseable in the O3 EMR distro. Very helpful for RDE so should be resurrected. Interested: ICRC ⩙ Content Reconciliation (Overlaps in package contents) 🚨 Easy Switch Path from EMR-distro to HIS-distro 🔖 Form Recommendations 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 in Registration workflow "Prevent Pt Duplicates" flow in Registration Page. Possibly should include merging pts. Should leverage pt-duplicate-detector in core. 💬 Team Communication 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) 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) 💾 Autosave a Form in draft Interested: _______ NOT STARTED 🇺🇳 Easy ICD 11 Integration ➗ Calculations Module review Palladium recommends this OMOD be reviewed as it becomes key in CDS / patient flag calcs and reporting. Enhance Cohort Builder in O3 Currently not obvious in UI and underutilized. 🔒📖 Document how to setup SSL (Docs) 🔥 IPS Pt 2: Generate an IPS from OpenMRS OCL OpenMRS Import feature OCL OpenMRS Import feature An answer (and clear documentation) to "How do I get my legacy metadata into OCL?" REGENSTRIEF FELLOWSPIH (testing) 𝛥 OCL Module: Diff Check workflow "Here's what will change" UX/UI when subscribing. (Possible GSOC Project) 🔥 Triage Gaps found in FHIR API Gaps Review 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) 🗺️ 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 UCSF-TAP REGENSTRIEF 📊 Iniz support for Reports 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. OPENMRS INC CHT NOT STARTED 🔥🔗 FHIR API Support for Terminology Services 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 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 Angular Engine deprecation |
Done
Now
Next
E.g.