One topic today would be discussing various UI test automation frameworks and recommendation for Bahmni@next (lead by @Soumya)
Another topic for today would be to talk about possible first increment for Bahmni@next
During the PAT call we discuss the following possible first increment option for Bahmni@next.
First Increment Goals
⇢ Uplift user experience (backed by user research and feedbacks)
⇢ Validate the architecture
⇢ Gain enough experience to estimate for rest of Bahmni@next
⇢ Reuse OMRS 3.0
Simple (less rewarding)
⌲ Mostly rewrite
Medium (more rewarding)
⌲ Uplift UX and add more features to exiting Medication tab
Medium (average rewarding)
⌲ Migrate entirely to React and MF architecture with UX improvements
Complex (more rewarding)
⌲ Augment current Orders features with a new ‘Orders Cart’ experience
While the registration option feels most safe but it does not help with all the goals we want to achieve with our first increment. One important goal is to get some early feedback on our Architectural approach and also be able to gain enough expertise in order to estimate and create backlog for rest of Bahmni@next for more community contribution in 2022.
Considering the goals we converged in the call that Medication would be a good first increment. There is a possibility that we might learn that this is way too complex for the first increment - in which case we will bring it back to the community and huddle to refactor our approach.
Please share your feedback or comments or opinions if you have any. Thanks!
@n0man thanks so much for this excellent post. Extremely clear and helpful.
Just a quick FYI re. Appointments since this seems of interest w.r.t. the Bahmni@next/3.x roadmap: FWIW, as you can see on the OMRS product roadmap below Palladium hopes to leverage Bahmni Appointments and create a 3.x Appointment booking/management experience. So there may be some shared interest there in the very near future. (CCing the technical team lead on that, @aojwang)