OpenMRS Reference Application 3 Backend

OpenMRS 3.0 Reference Application Backend is the self-hosted backend for the OpenMRS 3.0 Reference Application, a web-based medical record system.

  • Development
  • Productivity
  • Tools & Utilities
OpenMRS 3.0 Reference Application Backend is the self-hosted backend for the OpenMRS 3.0 Reference Application, a web-based medical record system. It provides the backend services, application programming interface (API), and data access used by the OpenMRS frontend and related health IT integrations. It is intended for health IT teams deploying the OpenMRS 3 Reference Application who want a tested starting point for local or production use.

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.

70/100 Good

Maintained
100last commit 16 days ago
Popular
42123 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
100256 MB minimum RAM, runs on ARM
GitHub stars
123
Open issues
30
Last commit
2026-11-05
Activity
declining

Checked 15 days ago - source: GitHub (openmrs/openmrs-distro-referenceapplication)

Resources & Compatibility

Minimum requirements: 256 MB RAM, 40 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 these local web ports are free The local install expects OpenMRS at http://localhost:80/openmrs/spa, Odoo at port 8069, OpenELIS at port 81, and Keycloak at port 8084. If those ports are already in use or blocked, you may not be able to reach the app, login, lab, or ERP parts. source
  • Set frontend and Odoo environment variables Set SPA_CONFIG_URLS and ODOO_ADDONS in the environment before starting, because the OpenMRS web app and Odoo use them to know which config pages and ERP modules to load. If these are missing or wrong, the web UI may load incompletely or Odoo may start without the modules you expect. source
  • OpenELIS lab integration is optional Only start the optional OpenELIS Docker Compose service if you need lab functionality, and make sure its lab settings point to the correct local or remote server. If you enable it without matching settings, lab pages or test results may fail. source
  • Start the app Use Docker Compose to start the reference application, then open the OpenMRS 3 UI at /openmrs/spa and the legacy UI at /openmrs. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the openmrs-reference-application-3-backend Docker image include a database?

No. It provides only the OpenMRS backend. You must provide a database for OpenMRS yourself.

Which local ports need to be free for the local install?

OpenMRS is expected on port 80 under /openmrs/spa, Odoo on port 8069, OpenELIS on port 81, and Keycloak on port 8084. If those ports are in use or blocked, the app, login, lab, or ERP parts may be unreachable.

Which environment variables should be set before starting OpenMRS and Odoo?

Set SPA_CONFIG_URLS and ODOO_ADDONS. The OpenMRS web app and Odoo use them to load config pages and ERP modules, so missing or wrong values can cause incomplete startup behavior.

Is OpenELIS required for the lab integration?

No, OpenELIS lab integration is optional. Start the optional OpenELIS Docker Compose service only if lab functionality is needed, and point its lab settings to the correct local or remote server.

Is there a self-contained option that includes a database and demo data?

Yes. A self-contained ZIP archive includes an embedded database and application server, with an option to install demo data for sample patients. Expand the archive and run the .jar file to start the Reference Application.

Answers sourced from context7.com, hub.docker.com, openmrs.org

Community

Collected 47 days ago - public community threads