| Note | ||
|---|---|---|
| ||
This is a work in progress. See https://talk.openmrs.org/t/service-provider-program-draft-definition-and-terms/12865 for the current status. |
OpenMRS encourages organizations and consultants to grow their business by becoming service providers of technical, implementation, and maintenance support of OpenMRS products. Implementers around the world consistently come to OpenMRS in search of expert help with their implementations. We've created an OpenMRS Service Provider program to begin offering a list of resources that are available for these implementers to contact directly in order to find an appropriate fit to meet their needs.
What Is A Service Provider?
OpenMRS Service Providers are organizations or consultants that will implement the OpenMRS Platform, OpenMRS Modules, and/or the OpenMRS Reference Application for another organization, such as Ministries of Health, NGO's, Implementing Partners, and more.
Service Providers are an important part of the OpenMRS community ecosystem Facilitate
Increase implementation, development and local support capacity
Improve access to appropriate service providers for implementations
Develop a list of service providers who are familiar with OpenMRS and can support the OpenMRS platform and/or the Reference Application
Three classifications of Service Providers
Platform without Reference Application
Platform with Reference Application
Platform with a Distribution
Strengthen local economy through support for local or regional OpenMRS Service Providers
Ability to work with other OpenMRS and Reference Application service providers and partners
Increased need and visibility of service providers
------------------
Why Use a Distribution?
...
| Distribution | Type | Description | |
|---|---|---|---|
 | 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 ThoughtWorks and the Bahmni community, Bahmni is an out-of-the-box EMR and Hospital Information System that can be configured without programming. | |
 | 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. Learn more... |
 | Kenya EMR | 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. |
Other Distributions
- CHITS is a targeted distribution for Philippine primary care centers, based on the older OpenMRS 1.8 platform
- PIH-EMR is an implementation-specific distro deployed by Partner In Health
- UP Health Service (UPHS) is an implementation-specific fork of CHITS
...
- be based on a currently-supported version of the OpenMRS Platform
- works leveraging the platform APIs, not just sharing the data model
- include instructions to install and upgrade it as a unit
- be actively supported.
- At a minimum, one person available via some electronic format (email, skype, IRC, etc) and with the contact listed on the Distributions wiki page.
- have an open-source license and publicly-hosted code
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.
What type is my Distribution?
...