The OpenMRS Platform underlies every implementation of OpenMRS. We, as a community, have committed to releasing new versions of the platform at least once per year.
So, where should we go with the OpenMRS Platform? Here is a vision for the Platform. In summary:
1. Maintain one Platform for all needs
Implementations & distributions may build completely different solutions using the platform, but we continue to all share the same platform.
- If something is not used by the vast majority of implementations/distributions, it probably doesn’t belong in the platform.
- Limiting the Platform to widely shared components decreases the chance of organizations needing to run a custom version of the platform and, thereby, maximizes the opportunities for collaboration.
- The Platform should expand to include widely used services that are not currently part of the Platform.
2. The Platform is the back-end.
Other than basic admin functions (e.g., module & OWA management), the Platform should focus on back-end services and not trying to provide a user interface.
- While we are creating OWA versions for most admin functions, the majority of these would be bundled in the Reference Application or easy additions to the Platform and not bundled with the Platform.
Given this vision, the goals for 2017 would be to incorporate a couple key services that most everyone is using into the Platform (e.g., ID generation and selected features from the EMR API module to start).
We’d love to hear your thoughts & feedback on this vision for the Platform.