OpenMRS Partner Badges: What and How to Qualify
Feedback on our Partner Badges is extremely welcomed and appreciated! To share your feedback, contact community@openmrs.org or share on Talk.
What are OpenMRS Partner Badges?
A way to celebrate, recognize, and reward! OpenMRS Partner Badges are one way we recognize and reward member organizations who work hard to participate well in our community and open software process.
A way for decision makers to evaluate prospective organizations. Clear badges also give partners and their prospective clients or funders some evidence of organizations' proficiency at working in our community. While not all partners are businesses/vendors, we believe in elevating enterprises who are working especially hard to be good community members - because when those partners thrive, so does our community!
Where do I find the list of awarded organizations?
The list of organizations awarded badges is on the OpenMRS website Partners Page at: om.rs/partners
Each organization also has it’s own page in this OpenMRS wiki to help openly communicate who they are, what they do, and what great things they have contributed to our community. These pages are designed to help admins, partners, and viewers to understand the strengths of an organization’s contributions, or where they may have room to grow. These pages are available under: Organizations & Service Providers
How does an Organization get awarded a Partner Badge?
This part needs work/clarity, and we want it to be very clear and fair.
Important caveats:
Case by Case: Every organization is a bit different. Thus, badges are considered on a case-by-case basis by a community stewardship team (such as the OpenMRS Community, Product, and Engineering leads, with consultation with other partners and community leaders).
Descriptions of Badges
Badge | Description |
|---|---|
| OpenMRS Transformative Leader Your organization is known for how you set up your priorities to create value both for the community and your business or team. Your team openly leads community-facing initiatives, projects, or work. They influence the community’s strategic product, technical, and/or community engagement directions and guide others on using community conventions. |
OpenMRS Established Contributor Your organization thinks about how your priorities can create value for the community and actively identifies areas of alignment with other organizations and the community. Your team is aligned with the community’s strategic product, technical, and/or community engagement directions and has adopted technical community conventions. | |
OpenMRS Proficient Contributor Your organization is familiar with contributing to the community in multiple ways, such as through contributing requirements and feedback, forum involvement, and notable project contributions. You seek ways to continue to grow in community contributions. | |
OpenMRS Emerging Contributor Your organization thinks about ways your organization’s contributions can affect others in the community and the OpenMRS ecosystem. Representatives from your tech team participate, share, and learn about community priorities and needs by attending community events and occasionally joins and observes squad/team meetings. | |
OpenMRS Implementer Your organization's primary focus is working with local stakeholders to customize and deploy a local version of OpenMRS at health facilities. You keep local OpenMRS implementations running so providers can use OpenMRS data to improve care. |
Examples of Activities Strong Partners Do
Here are a few examples of ways strong partners contribute to the OpenMRS community. Partners with Transformative Leader badges typically do all of these things.
Example Activity | Type | Description | Examples |
|---|---|---|---|
Active on Community Forum | Non-Code | Members from your org often share their priorities and answer questions on OpenMRS Talk or Slack. |
|
Active in Community Teams and/or Squads | Non-Code | Members from your org often attend and contribute to community calls, such as the Platform Team call and O3 Squad call. Contributes may range from feedback on emerging work to questions or problem-sharing. |
|
Code Contributions | Code | Members from your org frequently contribute technical work, as evidenced by the Contributors' section in Release Notes. | PIH contributed to each release in Platform 2.8.0 and 2.7, EMR 3.4, 3.3, and 3.2 (2024-2025). |
PR Reviews | Code | Knowledgeable members of your organization review PRs (to OpenMRS repositories) contributed by other Organizations |
|
Technical Testing of Releases using Distribution | Code | Your team uses your dev / test distribution environments to perform technical testing of releases. | SolDevelo contributed to the Platform 2.8.0 release by testing Platform 2.8-beta against their distribution, and sharing problems found (2025). |
GSOC Project Mentorship | Code | One or more software developers on your team provide mentorship for a GSOC project. |
|
QA: Community | Non-Code | Manual QA / Testing of Community Releases. |
|
Feature Requirements & Field Testing / Pilots | Non-Code | Rigorous requirements sharing / feedback to Squads on feature development | Palladium contributed substantial BA time to informing the Home Page v2 redesign (2025). |
Blog Contributions | Non-Code | You author or co-author article(s) for the OpenMRS blog. | EMR4All wrote a blog on their experience joining the community and their technical approach to very-low-resource OpenMRS deployment (2025). |
Job Board Posts | Non-Code | Your org posts opportunities on the OpenMRS Job Board as much as possible. This is important to nurture our ecosystem of volunteer or promising contributors, especially from low-resource settings, looking for relevant work. |
|
Stories from the Field | Non-Code | Your members proactively share real-world experiences from Implementation. For example:
|
|