Page Comparison

Talk post | Epic | Tech framework done

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

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.

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

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

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

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

Interested: PIH, Madiro

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

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

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

Status:

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

See Billing Squad details on the Squad Dashboard.

See Inventory Squad details on the Squad Dashboard.

Backend Dev work complete; UI work next.

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

We added a new Referral order type; work on the frontend for that remains to be done.

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

Horizontal Scaling Bottlenecks

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

Wiki, Talk

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

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

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

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.

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

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

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

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.

Wikum working on Iniz support for this.

Wiki Docs

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

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

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

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.

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 (and IMB for Oncology is a helpful use case), Mekom, Sonder, OpenMRS Inc, FAIMER

Clinical Views: Need Config structure, and logic (eg “enable when patient is female and pregnant…”)

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 part 2

Collecting further requirements for inpatient care, e.g. 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?

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.