Why OpenMRS

OpenMRS is a real, open-source electronic health record system deployed in over 40 countries for more than 20 years. It is not a toy project or a proof of concept — it is production software that clinicians depend on every day.

Across its core and modules, OpenMRS spans nearly half a million lines of Java — 1,200+ files, 182 JPA entities, 13 Maven modules — the kind of complexity that accumulates when a system does its job well for a long time. Modern frameworks sit underneath — Java 21, Spring 7, Hibernate 7 — but legacy application patterns sit on top. The path forward exists, but it is buried under years of accretion.

We chose OpenMRS because it mirrors the reality inside many companies built over the past 25 years: systems that were innovative when they launched, that still run, that teams are proud of — but that have become harder to change with confidence. If your system feels like this, you are looking at a peer.

20+Years
493KLines of Java
1,200+Source files
40+Countries

What you are about to explore is a real sprint output — not a mockup, not a pitch deck. Every claim was extracted from a live instance and verified against running code.

This Could Be Your System

The codebase has outgrown its documentation. Tribal knowledge is locked in the code. Your team knows exactly what they want to build — but legacy complexity keeps getting in the way. This is what it looks like when a system is finally, fully understood.

Millions of lines across hundreds of modules — the dependency graph has outgrown any single person's mental model
Modern frameworks underneath, but legacy patterns on top — the path forward is there, buried under years of accretion
Compliance and standards gaps that compound quietly until they can't be ignored
Every change carries risk when understanding is incomplete — your team deserves the confidence to move fast again

Please use your corporate email. Free providers (Gmail, Yahoo, etc.) are not accepted.