Top Product Priorities for next 1 Month: Community Discussion

Development
1

This week we will have a session to align on priorities for the next 2-4 weeks - seizing the momentum coming out of the conference!

Join us: This Sept 25 Thursday at 6pm EAT / 3pm UTC / 8:30pm IST / 11am EST Link: https://om.rs/zoomopenmrs

Info: In this open community call, we’ll brainstorm and then plan what priorities we’d like to focus on for the next 2-4 weeks.

Some ideas include:

  • O3 running on Platform 2.8
  • ⁠Billing Module Bug Fixes
  • ⁠Hackathon work cleaned up and merged in
  • ⁠GSOC work finished and merged in
  • ⁠Workspace system finished
  • ⁠Printing work from Madiro added
6 Likes
2

Thanks so much to everyone who joined last week!

Here’s the slide we used as a whiteboard: Product Focus Areas for next 2-4 Weeks - Google Slides

image
image1920×935 213 KB

Specifically, the priorities identified were:

  1. Pick a Date for the next EMR Release! Share your thoughts at: O3 EMR (RefApp) 3.6: What should be our target Release Date?
  2. Billing Module - bug fixes to make stable; don’t increase scope much.
  3. Hackathon work cleaned up and merged in (Allergies in Orders; Procedure Widget; Sticky Note….)
    • Next Step: PR reviews by senior community members
  4. Printing Gaps: Specify Printing in OMRS: SolDevelo worked w/ Madiro; would like to solve remaining gaps; Printing Ready-Work: work from Madiro added to community EMR
    • Next Step: Tech Huddle next week: Gaps, What tech is ready - @pwargulak @jnsereko did this end up happening? Or would you like me to book a focus session? We can also use this week’s O3 squad call too.
  5. Remaining GSOC 2025 work finished and merged in (eg Audit Log, & Immunization concepts; unit test prs for Translation Builder) (SWAGGER API still needs more months)
  6. Improve release code freezing processes: Was part of hackathon; work needs testing & finishing. Problem: When releasing, multiple rc’s. Bugs = have to re-release modules, which bring in other new non-release-planned features = testing complexity. Don’t want to stop deployment; allow people to still push to main; instead have dedicated release branch. Need to test this workflow. Demo repo for testing and demo-ing.
    • Next Step: Testing by @esther & team
  7. Finish the Workspace system: has been pending for a while, let’s get it done; it’s holding back ability to move forward with procedure orders etc.
  8. O3 EMR running on Platform 2.8
    • Next Step: Create branch on EMR distro w/ P2.8, see how tests react to that change - Jaye
  9. Platform 3.x planning: more cmty engagement (eg in Talk thread suggestions); have modules use a new branch for 3.0.0-snapshot where work can occur (prepare branches in modules)
  10. Age-based Lab reference ranges examples (HB/ALP) (and documentation)
    • @veronica working to get this into the next release
  11. Epic for remaining accessibility tasks
  12. Epic for remaining dev i18n tasks as intro tickets (esp as it’s nice for people just getting started to think about accessibility and i18n)
3 Likes
3

Thanks @grace Epic already created at Jira

waiting for @pwargulak and @SolDevelo to add more clarities on the various tasks as some folks are already beginning work on the same

2 Likes
4

I created the branch and fixed modules to work with 2.8.x a few months back, see GitHub - openmrs/openmrs-distro-referenceapplication at 3.x-core-2.8 . It’s being built and published to Dockerhub as well.

There’s one issue that I’m aware of with O3 and 2.8.x: TRUNK-6319

1 Like