Skip to content
buildbay.
OpenMRS logo

OpenMRS

openmrs · Health & fitness

GitHub stars

1,931
—Collecting 30d data

Stats updated

1,928 stars on Sep 27 to 1,931 stars on Oct 1, up 3.5 measured star snapshots

What is OpenMRS?

OpenMRS provides a shared clinical data model and modular platform that implementers can shape for different countries, programs, languages, and levels of care. The core records patients, visits, encounters, observations, concepts, programs, forms, and permissions; reference distributions add modern clinical workspaces and integrations without forcing every deployment into one fixed workflow.

OpenMRS is an open-source, patient-based medical record system designed to give providers a customizable electronic medical record. Its global community focuses on supporting care delivery in resource-constrained settings.

Core capabilities

  • Model patients, encounters, observations, concepts, programs, forms, and roles
  • Compose localized EMR distributions from core, backend modules, and frontend modules
  • Integrate clinical systems through REST, FHIR, reporting, and shared standards

A model built for local variation

OpenMRS separates reusable clinical concepts and platform services from the exact forms and workflows of one facility. Implementers can define identifiers, locations, encounter types, programs, concepts, forms, roles, privileges, and translations for a particular setting while keeping a common patient-record foundation.

  • clinical model
  • localization
  • forms
  • concepts

Core platform and composable distributions

The Java core supplies the domain model, services, database migrations, and module framework. Reference distributions layer backend modules and modular frontend applications for registration, appointments, queues, charts, forms, orders, results, programs, wards, and other workflows, allowing a deployment to choose its product surface.

  • Java
  • modules
  • microfrontends
  • distributions

Standards support an ecosystem

REST and FHIR APIs provide integration boundaries for end-user applications and other health systems. Reporting, cohort tools, form engines, laboratory workflows, registries, and community-built modules can operate around the shared record, which helps national programs and individual facilities extend the platform over time.

  • FHIR
  • REST
  • reporting
  • interoperability

Where it fits

Use cases

  1. 01

    Deploy a localized clinical record

    Configure concepts, forms, languages, identifiers, locations, roles, and workflows for a health program or facility rather than forcing local care delivery into a single vendor's fixed data and interface model.

  2. 02

    Coordinate longitudinal patient care

    Record visits, encounters, observations, diagnoses, medications, conditions, orders, results, appointments, and program enrollment so care teams can work from a patient history across repeated contacts.

  3. 03

    Connect an EMR ecosystem

    Use REST and FHIR APIs, reporting tools, backend modules, and microfrontend extensions to connect registries, laboratories, analytics, patient-facing tools, and locally developed clinical workflows.