Service Providers

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.  

An organization that has the commitment and capacity to perform software development, advising, and/or implementation work using and promoting products in the OpenMRS ecosystem.

Why Are Service Providers an Important Part of the OpenMRS Ecosystem

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

Types of Service Providers

List of Service Providers 

FAQ

Can I add my distribution to this page?

To be added to this page, at a minimum your distribution must:

1. be based on a currently-supported version of the OpenMRS Platform
2. works leveraging the platform APIs, not just sharing the data model
3. include instructions to install and upgrade it as a unit
4. 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.
5. 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?

Not sure how to categorize your Distribution?  Here's some examples:

• Do you intend for health facilities anywhere in the world to use your system without drastic customization? This is probably a General Purpose Distribution.
• Targeted at a specific geographic region, e.g. KenyaEMR or Mozambique's eSaude? This is a Targeted Distribution.
• Targeted at a specific disease, e.g. Ebola or MDR-TB? This is a Targeted Distribution.
• Is your distro built for one specific customer, and would need extensive modification or forking to be used by someone else, e.g. PIH-EMR? This is an Implementation Specific Distribution.
• Do you have a collection of OpenMRS modules and configuration, but no automated installer? This is not actually a distribution.
• Want advice on how to package things as a distribution? Post to the developers Talk category and ask!

Why become an official Distribution?

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.

Benefits include:

• Implementers will be more likely to install it
• Developers will be more likely to look at your code and harvest portions into the core platform, lessening the amount of code you have to maintain yourself
• Participating in the OpenMRS community will make your Distribution more recognizable and you'll end up with better access to knowledge and contacts

Established distributions can take advantage of OpenMRS infrastructure:

• hosting forums as a category on OpenMRS Talk
• leveraging our translation community on Transifex

Having trouble contacting a distribution?

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.