I disagree with Darius’ advice. An implementer should participate in a LibreHealth project or team, if their needs are met by LibreHealth.
In that other thread, I said who our user is. “Knowing thy user” is probably the most important commandment of information systems. Our user is the last-mile clinician and patients, whose central focus is patient care. We want to get out of the way of our users, which means that we make design choices that will focus on usability and ease of use, over flexibility. The openmrs-platform wants to be everything for everyone. Its focus is flexibility.
openmrs reference application is a “reference application” (for reference purposes) with example code that can be used by others who want to use the platform. @djazayeri himself has confessed a few times of whether it is usable and meets the need of implementers. Should its development continue to move forward. IMHO, it is good for example code, but not a product. Its server-side architectural choices have been abandoned by the openmrs developers, but since it is the latest minimum viable product, I assume many implementers are building on top of that and continuing to develop modules on an abandoned stack.
lh-toolkit is forward looking toolkit/toolbox. It is a product that can be (after the LTS 2.0) customized by a user who doesn’t need to know HTML, CSS, JS, SQL. I feel like openmrs architects want to adopt standards after they become defacto. Our objective is to contribute to the process by which a standard becomes defacto. We will also not create our own frameworks, or try to build our own standards.
librehealth-EHR is a product that has same user-target of clinicians like the toolkit, but with billing and reporting that matches government requirements. The plan is that it integrates with lh-toolkit and uses components from toolkit.
lh-radiology is a product that is a fully open-source Radiology Information System (RIS) that is usable out-of-the-box for radiology departments, from radiology ordering, scheduling, imaging, reporting etc. There is no FLOSS RIS out in the world. This product will likely use toolkit components too, along with tight integration with other components.
Besides the projects that create their products, we also have teams. For a user (implementers, clinician or patient), we have a support system through teams. Education and university, Diversity and inclusion, documentation are teams that will provide cross-cutting support to the projects. So from an implementers perspective, if you are implementing a product to train your students, the Education team will provide support with training, capacity building. If you have fewer women (only one among the many target groups) in your implementation, the diversity team will provide support through programs that help bring more women.
That is how from an implementer’s perspective LibreHealth is different.