OpenMRS Reference Application Distro
OpenMRS Reference Application Distro is a self-hosted, pre-configured OpenMRS 3.0 deployment for clinics that want a ready-to-run electronic medical record…
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.
63/100 Good
- Maintained
- 100last commit 3 days ago
- Popular
- 42125 GitHub stars
- Easy to install
- 250 install platforms, install notes, Docker image
- Light to run
- 1016 GB minimum RAM
- Security check
- 95no serious findings, CI, tests
- GitHub stars
- 125
- Open issues
- 31
- Last commit
- 2026-11-17
- Activity
- declining
Checked 3 days ago - source: GitHub (openmrs/openmrs-distro-referenceapplication)
Resources & Compatibility
Minimum requirements: 16 GB RAM, 8 CPU core(s), 500 GB disk. ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Use the demo before local install Open https://dev-his.openmrs.org and sign in with jdoe/password to see a working system; this gives you a known-good reference when your local pages or login look wrong. source
- Check local ports after starting After the stack is running, the main app is usually at http://localhost:80/openmrs/spa, with Odoo at http://localhost:8069, OpenELIS at http://localhost:81, and Keycloak at http://localhost:8084. If any page fails, check that Docker published those ports and your firewall allows them. source
- Keep frontend and Odoo env vars Keep SPA_CONFIG_URLS (the list of frontend configuration files) and ODOO_ADDONS (the Odoo add-on modules) set as documented. Without them, the web app may not find its settings and Odoo may be missing modules you need. source
- Quick start Start the stack with docker compose up, then open http://localhost/openmrs/spa for the OpenMRS 3.x UI. source
Fetched 42 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Which local ports should I check after starting the Dockerized OpenMRS stack?
The main app is usually on port 80 under the /openmrs/spa path, with Odoo on port 8069, OpenELIS on port 81, and Keycloak on port 8084. If a page fails, check that Docker published the ports and your firewall allows them.
Which environment variables should I keep when deploying the frontend and Odoo?
Keep SPA_CONFIG_URLS set to the list of frontend configuration files and ODOO_ADDONS set to the needed Odoo add-on modules. Without them, the web app may not find its settings and Odoo may be missing modules.
Where does the backend image get its reference application Initializer configuration?
It is drawn from the distro sub-directory in the repository. That directory includes a full Initializer configuration intended as a starting point for the reference application.
Have users reported trouble installing the reference application from scratch?
One forum user reports several unsuccessful attempts to install the reference application from scratch with OpenMRS Core 2.5.x and 2.6.0.
Answers sourced from context7.com, github.com, talk.openmrs.org
Community
Collected 48 days ago - public community threads