Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
This page needs to be reviewed
This is the OpenMRS, Ltd ("OpenMRS") OpenMRS License FAQ. It aims to answer the most common questions people have about using and distributing code under Mozilla Public License 2.0 (MPL 2.0) + Health-Related Additional Disclaimer of Warranty and Limitation of Liability.
If you see any errors in this FAQ, or have suggestions for further questions, please contact OpenMRS at firstname.lastname@example.org. Note that these answers do not represent our license. The explanations are not legal advice. If you need to know exactly what the OpenMRS license requires, you need to read and understand the license itself; if you need legal advice, you need to talk to a lawyer.
There are several factors that initially attracted us to an MPL-based license originally:
But we had to make several modifications to MPL 1.1 to meet our needs, meaning we weren't using an official OSI-approved license. When MPL 2.0 came it, it presented a great opportunity to migrate to a largely identical license that met our needs and no longer required us to make modifications to the license.
The Health-Related Additional Disclaimer of Warranty and Limitation of Liability is a tool afforded by MPL 2.0 that allows us to address our specific medico-legal needs without having to modify the license itself.
The binary form of the Original Code provided by OpenMRS already meet the requirements of section 3.2. You may distribute and use it under the terms of MPL 2.0.
If you are offering a warranty, however, you must make clear that it is offered by you alone (Section 3.5). OpenMRS offers no warranties on the Original Code or any other code we make available.
You may distribute any binaries you create under a license of your choosing, as long as it doesn't interfere with the recipients' right to the source under the MPL 2.0 (Section 3.2).
In addition, there are several obligations relating to your Modifications. You must
MPL 2.0 is not as "viral" as the LGPL or the GPL forms of public licenses. To determine the level, you must focus on the definition of a "Modification" in MPL 2.0 (Section 1.10).
What is a Modification? Any changes to MPL 2.0-covered files, or new files into which MPL 2.0-covered code has been copied, are Modifications and so fall under MPL 2.0. New files containing only your code are not Modifications, and are not covered by MPL 2.0.
Files which fall under MPL 2.0 because they are or because they contain Modifications must be made available as detailed in MPL 2.0.
MPL 2.0 + Health-Related Additional Disclaimer of Warranty and Limitation of Liability covers the core OpenMRS code and is used for all of the OpenMRS community-supported and distributed modules, but other modules are not required to be licensed under MPL 2.0. In fact, modules do not have to be open source. You are free to create a closed-source module and distribute it under any license you wish. Module authors who are uncertain of how to license their module are encouraged to make their modules open source and, unless they have some reason to use a different license, use the same licensing as OpenMRS, but this is not a requirement for modules.
Sure. The most fundamental goal of the OpenMRS Community is to improve the health of people in resource-constrained environment by providing a common platform upon which people can meet their local needs. One of the only ways that truly sustainable solutions can be created is for local solutions to be self-sustaining. If you become proficient in installing, customizing, and/or maintaining OpenMRS implementations, you could, for example, build a company to provide local service to those implementations around you. The little bits of work you do in improving the platform along the way can be combined with many others around the world to benefit everyone, including meeting your own needs.