msf-ocg / lime-emr-project-demo

A demo of OpenMRS 3.x EMR using configurations (not a distro)

MSF-OCG LIME EMR Project - OpenMRS 3.x demo

A Generic Light Modular EMR using

Integration with

                          

Technical documentation of the project

https://msf-ocg.github.io/LIME-EMR-project-demo

Quick start

Package the distribution and prepare the run

docker compose build

Run the app

docker compose up

Ambitions and success criteria

• Integrated – with OpenMRS ecosystem and community roadmap
• Innovative – leveraging modern technology and approaches
• Sustainable – using well maintained and documented tools and practices
• Open – using open-source software and licenses allowing for reusability
• Data driven – quality information will be available to the right people when they need it
• Quality of care – address tangible needs from health care workers and patients
• Relevant – content and patient flows representative of use cases defined healthcare workers
• Harmonized – content is following global standards such as ICD, SNOMED, etc.
• Portable – agnostic architecture, containerization, and orchestration
• Adaptable – content and configuration management that can easily be updated
• Recoverable – recommendations for a solid backup and recovery strategy
• Testable – automated testing and reporting whenever possible
• Secure – architecture and practices to meet GDPR and HIPAA regulations
• Reliable – recommendations to support redundancy, failover, and monitoring by design
• Interoperable – to support Health Information Exchange (HIE) and standards such as HL7 FHIR
• Collaborative – share information, insights, strategies and deliverables within the community
• Achievable – taking in account the overall roadmap and challenges of implementers

lime-emr-project-demo's Issues

Upload attachment in visit notes is not working

Right now, it seems impossible to upload an attachment in visit notes:

Docker Compose best practices for Dev and Prod

What are the best practices to follow to use Docker Compose in Dev and Prod? (cache, replica, specific settings, restart, cleanup, CPU, deploy, logs, etc.)

Anonymize an OpenMRS database dump

Requirements

• Identify PII (registration, users, providers, etc.) and sensitive data (notes, comments, pictures, scans, etc.) stored in an OpenMRS database dump
• Write a script to de-identify personal data and anonymize sensitive data
• Using existing open-souce, maintained, and configurable solutions is allowed

Role-based navigation and features

Assuming 3 roles in the EMR: registration, nurse, and doctor. Each of them can only see specific features based on the table below:

Role	Navigation and features
Registration	Register, Search, Appointments
Nurse	+ Service Queues, Patient chart
Doctor	+ Forms, Notes, Lab order

How to configure the the navigation and features they can access to based on their role?

Role-based forms

Assuming that some clinical forms should only be available to specific providers, how would you assign specific roles such as nurse, oncologist, surgeon, and gynecologist to specific forms?

It would prevent some roles to see or fill out forms that they should not have access to.

A configurable approach to backup OpenMRS database and patient files

Requirements

• Setup a routine backup process (ex. nightly) for the production database and patient files (ex. attachments, x-rays, etc.)
• Being able to configure the backup time and the destination folder
• Backup process should consider potential active connections
• Backup size assumption is between 500 Mo and 1 Go
• Generate a log file in case of errors
• Using an open-source tool that handles such requirements is allowed (ex. Xtrabackup, Percona, etc.)

A process to restore OpenMRS database and patient's file backups

Suggest a way to effectively and safely restore OpenMRS database and patient file backups. Using an open-source tool that handles such requirements is allowed (ex. Xtrabackup, Percona, etc.)

Unknown column 'queueentry5_.queue_coming_from' in 'field list'

Hello @michaelbontyes , this is thrown when setting up LIME-EMR-project-demo locally. Could be coming from backend config.

Make diagnosis fields not required in the visit notes

In visit notes, a diagnosis is required. It means that for each note, a diagnosis will be added to the visit summaries.

Instead, make the diagnosis fields of the visit note not required.

Secrets and Vault

How to store database and OpenMRS secrets for all environments (dev, staging, uat, prod) without exposing them publicly in the Github repo?

Print today's appointment

Leveraging the work started through the GSOC 2023, add a button on the appointment dashboard to print today's appointment (A4 format).

Database redundancy

We're looking for database redundancy in case of any failure.

The scenario is:

1. The main OpenMRS database is continuously and automatically synced to a secondary database as master-master or master-slave architecture.
2. The main OpenMRS database the backend uses is failing - not responding anymore.
3. The OpenMRS backend automatically switches to the secondary database to keep EMR operations running.
4. Once fixed, the backend switched back to the primary database / normal behavior again.

Requirements and assumptions:

• OpenMRS 3 is running on Docker-compose
• Databases (MariaDB) instances are running on Docker-compose on the same network, but potentially on different devices/laptops.

Task:

• Modify the docker-compose and create necessary configuration files to add that functionality

Modify the visit summaries in the patient chart

In the "Encounter" tab of the visit summaries in the patient chart, remove "Lab results" and "Notes" encounters as they are already available in the "Tests" and "Notes" tabs.

Also, rename "Encounters" tab by "Consultation".

Add more of Read steps by steps to setup this locally

cc @michaelbontyes

Environment-based Docker images

In the OpenMRS Docker-Compose, find a way to select the right OpenMRS frontend image to use (dev, qa, main) depending on the current hostname.

Logic if hostname ends with:

• D -> Docker OpenMRS frontend image tag should be dev
• T -> Docker OpenMRS frontend image tag should be qa
• P -> Docker OpenMRS frontend image tag should be main