Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
OpenMRS is a flexible, modular, multi-layered system, and one of its strengths is that its platform can be used in many different configurations. As a result, "OpenMRS" can mean many things.
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.
There are two ways to start using OpenMRS, depending on your needs and available resources:
Some of the advantages to using a distribution that already exists are:
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.
An OpenMRS distribution that is intended for a specific clinical or geographical use case, or a non-patient-care use case. For example, a standardized country specific distribution or one targeted at a specific disease epidemic.
A configuration of OpenMRS that is technically built like a Distribution, but is only intended for use by one specific consumer. If you are not the specific target of this distribution, you wouldn't probably use it directly, but as a developer or implementer you may learn a lot from studying or forking it. However, there may be opportunities to collaborate with the teams working on these distributions if you wanted to create a replica of their clinical and technical environments.
|OpenMRS Reference Application||General Purpose|
Maintained by the OpenMRS community, this distribution demonstrates how the platform's capabilities can be used to build an EMR. You could use this out-of-the-box as a facility EMR, but it (currently) doesn't have the complete EMR feature set.
|Bahmni||General Purpose - Hospitals and Large Clinics|
Maintained by the Bahmni Coalition, Bahmni is an out-of-the-box EMR and Hospital Information System that can be configured without programming. It integrates OpenMRS with Odoo and OpenELIS to provide out of the box and ready to deploy, inetgrated solution that covers hospital workflows
|eSaude||Targeted - Mozambique||Developed by the Mozambique regional OpenMRS community, eSaude. A tailored distribution of OpenMRS to provide point of care clinical patient registration and healthcare workflows on tablets for the MOH public health facilities.|
Targeted - Kenya
Developed by I-TECH, KenyaEMR is a tailored distribution of OpenMRS which meets the requirements laid out in the Kenya Ministry of Health document: 2011 Kenya EMR Standards and Guidelines.
|UgandaEMR||Targeted - Uganda|
UgandaEMR is the custom implementation of OpenMRS in Uganda which is mandated by the Ministry of Health.
To be added to this page, at a minimum your distribution must:
If these criteria are met, and you want to share your work with others, please post to this Talk category and tag your post with "distributions", edit this wiki page directly, or reach out to Darius Jazayeri and Jan Flowers.
Not sure how to categorize your Distribution? Here's some examples:
If you have built a Distribution of OpenMRS that meets the criteria above, we'd love to include it on our official list of distributions, on this page. We want the OpenMRS community to have access to many options, and be able to find the best one for their use case. We hope that you'd like to list your distribution here.
Established distributions can take advantage of OpenMRS infrastructure:
Are you an implementer or user who is having trouble accessing a Distribution's support or code that is listed on this wiki page? Post your questions on OpenMRS Talk on in the #software category.