OpenMRS Academy

S

LEVEL 1: OpenMRS Fundamentals

Module 3: Overview of OpenMRS

Learning objectives

• Explain the main OpenMRS products and key features of each;
• Describe the difference between the OpenMRS Platform and OpenMRS Distributions;
• Describe how the OpenMRS Community functions;
• Discuss how the OpenMRS code of conduct and community conventions create a positive community experience;
• Navigate the Wiki to find information on different projects;
• Sign up to the OpenMRS Community and receive a Community ID;
• Make an introduction by posting on the Talk channel and start interacting with the Community;
• Identify OpenMRS initiatives around the world.

Introduction

What is OpenMRS?

• Data from OpenMRS is increasingly used to inform the public health decisions needed to achieve the UN Sustainable Development Goals, measure progress towards UNAIDS’ 95-95-95 targets for HIV epidemic control and achieve universal health coverage.
• The Open Medical Record System (OpenMRS®) was created in 2004.
• An open source medical record system platform for resource constrained countries.
• Countries use the OpenMRS platform and modules to create a customized EMR system in response to actual needs on the ground.

​

Open source software means

• those who develop it make the source code freely available
• anyone else can view, copy, learn from, alter, or share that code

Open source software does not necessarily mean there is no cost for

• Customization
• Deployment
• Maintenance

​

• OpenMRS software code is open source

​

• Some costs are usually associated with customizing, deploying, and maintaining OpenMRS

​

​

What is Open Source?

Quick Walkthrough of the OpenMRS Reference application

Login Page, type in demo.openmrs.org

Use the following credentials to access the system:

Username: Admin

Password:Admin

Homepage…...

Registration Page set-up to have validations

Patient search available by name or Unique Id

At a glance patient summary for quick decision making

Comprehensive capture of patient vitals

Capturing Patient diagnosis from a curated list...

Sample view of reports that can be generated from the application.

Demo Video

Overview

• What is OpenMRS?
• A Java-based, web-based electronic medical record.
• In the backend of this web based application is a robust data model, an API and concept dictionary which are fundamental components of the application.
• Key terms to understand here are:
• Data model: is an abstract model that organizes elements of data and standardizes how they relate to one another and to the properties of real-world entities.
• Backend: website or software program that users do not see.
• Application Programming Interface (API): software intermediary that allows two applications to talk to each other
• User Interface (UI): is the set of controls and sensory channels through which a user can interact with software.
• Concept dictionary: list of all the medical and program-related terms.

​

​

OpenMRS Architecture

UI

​

​

​

​

​

API

​

​

​

​

​

Backend &

data model

Modules

• With the OpenMRS Platform and concept dictionary, countries and organizations can use ready-to-use community modules, develop their own, and build their own customized electronic medical record system to meet their implementation needs.
• Modules can be easily added or removed from the system.
• Modules have full access to the system and can modify or enhance the behavior of the system.
• Modules also provide a mechanism for adapting OpenMRS to local needs.

​

​

Short Video on how to a sample add a module

Key features

1. Central Concept Dictionary: Definitions of all data (both questions and answers) are defined in a centralized dictionary, allowing for robust, coded data.
2. Security: User authentication with complex password support. Support for roles, privileges to separate what user can and cannot do. Users can also login through a single-sign on system like CAS for centralized enterprise authentication.
3. Patient Repository: Creation and maintenance of patient data, including demographics, clinical observations, encounter data, orders, etc.
4. Multiple identifiers per patient: A single patient may have single or multiple identifier numbers like passport number, national id, medical record number, etc.
5. Flexible Data entry: With the FormEntry module, clients with InfoPath (included in Microsoft Office 2003 and later) can design and enter data using flexible, electronic forms. With the HTML FormEntry module, forms can be created with customized HTML and run directly within the web application.

Key features (2)

6. Data export: Data can be exported into a spreadsheet format for use in other tools (Excel, Access, etc.), including aggregation HMIS systems like DHIS2.
7. Modular architecture: An OpenMRS Module can extend and add any type of functionality to the existing API and web application. 200+ available modules.
8. Support for complex data: Radiology images, sound files, etc. can be stored as “complex” observations.
9. Cohort management: The cohort builder allows you to create groups of patients that match a “criteria” for data exports, reporting, analysis etc.
10. Localization/internationalization: Multiple language support and the possibility to extend to other languages with full UTF-8 support.

​

At a global level, OpenMRS reaches more than 12.6 million patients at almost 5,500 health facilities in 32 countries - five times the number of sites than we first tallied in 2016.

2019

5,485 sites

& 12.6 million patients

2016

1,149 sites

& 5.1 million patients

Title Here

OpenMRS Distributions

• Two ways to use OpenMRS:
• Start from an existing distribution, configure and adapt it to your needs.
• Develop a custom application on top of the OpenMRS Platform.

​

• What Is A Distribution?
• A particular configuration of the OpenMRS Platform, OpenMRS modules, content (concepts, forms, reports, etc.) and (optionally) other integrated applications, that can be installed and upgraded as a unit.

​

• ​

Advantages of Distributions

Advantages to using a distribution that already exists are:

• Leverage work that has already been done to address workflows (Hospital Management, etc.), regional needs (Kenya, Mozambique, etc.), and specialty service areas (TB, etc.);
• Collaboration opportunities with other developers and implementers working on similar use cases;
• A broader user base of the same distribution can lead to improved code quality, additional features, and shared QA work.

​

Benefits of distributions

Benefits of becoming an official distribution include:

• Implementers will be more likely to install it;
• Developers will be more likely to look at your code and harvest portions into the core platform, lessening the amount of code you have to maintain yourself;
• Participating in the OpenMRS community will make your Distribution more recognizable and you'll end up with better access to knowledge and contacts.

Types of distributions

• General Purpose Distributions: An OpenMRS distribution that intends to serve the worldwide audience of clinics, hospitals, governments, NGOs, etc., who want a patient medical record for purposes of clinical care.

​

• Targeted Distributions: An OpenMRS distribution that is intended for a specific clinical or geographical use case, or a non-patient-care use case.

​

• Implementation Specific Distributions: A configuration of OpenMRS that is technically built like a distribution but is only intended for use by one specific consumer.

Title Here

General Purpose

OpenMRS Reference Application

• The OpenMRS Reference Application distro demonstrates how the OpenMRS platform can be used to build a facility EMR
• Community developed starter sets of metadata and terminology.
• Good starting point for implementing OpenMRS in a facility

​

Bahmni

• Bahmni is an easy to use, open-source EMR and Hospital Management System for healthcare providers in low-resource settings.
• Its goal is to provide an out-of-the-box solution for hospitals and large clinics, that can be configured with zero programming.

​

Targeted

• eSaude
• The eSaude distribution is developed and is managed by the eSaude community, a regional community based in Mozambique.  
• It was built to meet the requirements of the Mozambique MISAU (Ministry of Health) for HIV Care & Treatment and Maternal and Child Health.  
• KenyaEMR
• The KenyaEMR is a tailored distribution of OpenMRS
• Meets the requirements laid out in the Kenya Ministry of Health document: 2011 Kenya EMR Standards and Guidelines.
• UgandaEMR
• UgandaEMR is the custom implementation of OpenMRS in Uganda which is mandated by the Ministry of Health.
• Includes HIV testing and treatment for adults and children and SMC, along with mandated ministry reports for facility management.

Welcome to the OpenMRS Community

Com·mu·ni·ty /kəˈmyo͞onədē/

1. a group of people living in the same place or having a particular characteristic in common. "the scientific community"

​

• a feeling of fellowship with others, as a result of sharing common attitudes, interests, and goals. "the sense of community that organized religion can provide"

​

​

​

​

​

OpenMRS - 2020

Community of Practice

A Community of Practice brings together people with a shared problem, interest, or passion. This group of people get together to create a solution by:

• identifying common solutions,
• sharing their ideas, experience and knowledge, and
• using shared spaces and tools.

​

​

Domain: Our Mission

The mission of OpenMRS is to improve healthcare delivery in resource-constrained environments by coordinating a global community that implements and creates a robust, scalable, user-driven, open-source medical record system platform.

​

​

People: Who Cares About it?

OpenMRS coordinates and grows a global community of:

​

​

​

​

​

• developers
• implementers
• business analysts
• technical writers

• subject matter experts
• quality assurance testers
• project managers
• stakeholders

OpenMRS Users:

Health care workers using OpenMRS data to improve patient care in a country’s health facility

OpenMRS Implementers:

• customize distributions
• deploy OpenMRS at health facilities at the country-level

OpenMRS Community: Build & maintain

• the OpenMRS Platform
• the Reference Application
• shared community modules

People: How is our community organized?

OpenMRS Inc

​

Executive Team

Board of Directors

Where people come together to work on a solution to a shared problem

Entity that represents the community’s legal and fiscal interests.

People supporting community collaboration, direction, + infrastructure

OCL for OpenMRS Squad

​

​

​

​

Jon Payne | OCL

​

​

​

​

Michael Bontyes | MSF

​

​

​

​

Muhima Mohamed | MSF

​

​

​

​

Ellen Ball | PIH

​

​

​

​

Mark Goodrich | PIH

​

​

​

​

Hadijah | OpenMRS Community Dev

​

​

​

​

Ian Bacher | Brown University

​

​

​

​

Burke Mamlin | Regenstrief

​

​

​

​

Suruchi Dhungana | OpenMRS Fellow

​

​

​

​

Andrew Kanter | Columbia University

​

​

​

​

Grace Potma | OpenMRS

​

​

​

​

Irene Nyakate | OpenMRS Community Dev

​

​

​

​

Juliet Wamalwa | OpenMRS Community Dev

​

​

​

​

Laure Kpea | MSF

​

​

​

​

Swedhan Gunaskaren &

Kirity Mahanty | ThoughtWorks

​

​

​

​

Jennifer Antilla | OpenMRS

​

​

​

​

Lincoln | Andela

Where collaboration happens

Explore our Strategic Framework and Dashboards

• What’s happening
• Who’s putting in resources
• What needs support

Participate in more Virtual Events

Come to a Squad or Implementer Showcase

​

Strategic Framework for Coordination can be found on our Wiki, with live links to our Product and Community Engagement Dashboards

An at-a-glance of:

​

Our current top

Strategic Directions

for community engagement

​

​

Non-technical opportunities to support/invest

Community Engagement Dashboard

OpenMRS - 2020

An at-a-glance of:

​

Our current top

Strategic Directions

for platform/products

​

Technical opportunities to support/invest

om.rs/productdashboard

OpenMRS - 2020

Practice: What and how we build things together

​

Community Conventions

At the end of the next 10 minutes, what can you expect to know about our community conventions?

• Describe three types of shared community practices
• List the different community communication tools
• Use the right community communication tool for your purpose
• Explain how decisions are made in our community
• Give three examples of decisions that reflect OpenMRS decision making plays

Community: Short and Long Term Value

Assessment/Exercises

• In your small group, pick one of the following community groups:
• Technical Action Committee
• COVID-19 Response Squad
• Analytics Engine Squad
• Quality Assurance Support Team
• Navigate to the OpenMRS Wiki and Talk
• Answer the questions on the next page about your group

​

​

Assessment/Exercises

• What is the purpose of this group?
• Where and how do they communicate?
• What are they currently discussing or working on?
• Have they presented their work through a Design Forum, Lightning Talk, Squad Showcase, or other community session?

​

Assessment/Exercises (option 2)

• In your small group, identify a question, problem, or challenge about OpenMRS that interests you.
• Search Talk and the OpenMRS Wiki to find past or current information about a committee, squad, or team in the community
• Discuss what you found
• Present your findings to the group

OpenMRS Global Goods

Thank you!