OpenMRS Core

OpenMRS Core is a free, customisable core platform for patient-based electronic medical records, helping clinics and hospitals securely store, organise, and…

  • Business & Finance
  • Tools & Utilities
OpenMRS Core is a free, customisable core platform for patient-based electronic medical records, helping clinics and hospitals securely store, organise, and manage patient health information.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

64/100 Good

Maintained
100last commit 4 days ago
Popular
661,996 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM
GitHub stars
1,996
Open issues
354
Last commit
2026-11-17
Latest release
2.8.10
Activity
declining

Checked 4 days ago - source: GitHub (openmrs/openmrs-core)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 8 CPU core(s), 500 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Check service URLs and ports first OpenMRS runs at http://localhost:80/openmrs/spa, Odoo ERP uses port 8069, OpenELIS uses port 81, and Keycloak (the login/SSO service) uses port 8084. Checking these first stops you from opening the wrong port or thinking the app failed when it is just on another address. source
  • Try the demo before local setup You can open https://dev-his.openmrs.org and sign in with jdoe / password to see the interface. Without seeing the demo first, you may not recognize the expected login or main screens and could think your local install is broken. source
  • OpenELIS lab is optional The OpenELIS lab service is optional, so if you are not connecting lab results you can leave it out. That way you do not spend time troubleshooting a service you do not actually need. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which OpenMRS-related service ports should I check first when the app seems unavailable?

OpenMRS is expected on port 80 under the OpenMRS SPA path, Keycloak SSO uses 8084, and OpenELIS uses 81. Checking these first can prevent opening the wrong port.

Is the OpenELIS lab service required for a basic self-hosted OpenMRS setup?

No, the OpenELIS lab service is optional. Leave it out if you are not connecting lab results.

How can I verify the expected OpenMRS interface before debugging a local install?

Try the demo first and sign in with jdoe / password. This helps you recognize the expected login and main screens.

What APIs can I use to integrate OpenMRS with other systems?

OpenMRS exposes REST and FHIR APIs for integration with other end-user tools and systems.

What kinds of administration problems are covered in the OpenMRS troubleshooting documentation?

The documentation covers installation, Tomcat, compilation, high CPU utilization, and memory errors.

Answers sourced from openmrs.org, context7.com, openmrs.atlassian.net

Community

Collected 48 days ago - public community threads