Hi @mksd, thank you for sharing some initiatives that you and your team are working on, this is exciting because it sounds like there’s a lot of overlap here.
To directly answer your main question about whether we referring to Ref App 3.0? The answer is, it’s complicated.
There are a lot of conversations in the community about next steps for development (and this is awesome), but I think overlapping conversations are happening.
-
Some conversations are focused on functionality that needs to be added to Core or to Ref App now (or last month)! Very high priority issues that are required to meet deliverables that implementers have committed to, to patch bugs in the current system, or development projects that are already underway.
-
Other conversations are focused at additional functionality that implementers would like to see built out in the next 6-18 months. Trying to identify what are high value and high priority items across the community to solve anticipated deliverables.
-
And finally, other conversations are focused on developing a compelling and comprehensive vision of where OpenMRS can be in 2-5 years. This is a conversation where we allow ourselves to step back and re-imagine how we can position OpenMRS as a community of EHR thought leaders with a cutting-edge software package that demonstrates that. Something that addresses the anticipated needs of the OpenMRS community, its stakeholders, and is so wonderful to use and develop with that it places OpenMRS systems on the map as the go-to EHR.
At one point or another, each of these different conversations have been called ‘OpenMRS 3.0’ or ‘Ref App 3.0’. Which obviously is a bit confusing!
The undertaking that Tobin Jonathan and I are focused on is primarily the third category - working with the community to bring together a comprehensive vision, and strategy to get us there.
However, the future is not a distant dream. I believe there is a way we can start slowly building as a community (in the very near future) towards our larger long term goals while concurrently addressing the immediate and short term deliverables (category 1 and 2).
I’d like to propose a way we can do this in a detailed Talk post early next week.
I’m also interested to learn more about the large project your working on. Have you started to compile some documents summarizing the features you are planning to build out. It would be interesting to see where it overlaps with other groups working on similar functionality.
-Greg / Tobin