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
Specifically, the priorities identified were:
- Pick a Date for the next EMR Release! Share your thoughts at: O3 EMR (RefApp) 3.6: What should be our target Release Date?
- Billing Module - bug fixes to make stable; don’t increase scope much.
- Hackathon work cleaned up and merged in (Allergies in Orders; Procedure Widget; Sticky Note….)
- Next Step: PR reviews by senior community members
- 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.
- 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)
- Next Step: Audit Log wrap-up - @wikumc & @nsalifu; Swagger - @chibongho & @capernix ; Translation builder unit test coverage - @nethmi & @shettybharath
- 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
- 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.
- Follow up with @chibongho @bistenes @dkigen to see what they need
- 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
- 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)
- @tendomart to help spread the word
- Age-based Lab reference ranges examples (HB/ALP) (and documentation)
- @veronica working to get this into the next release
- Epic for remaining accessibility tasks
- @tendomart to create
- 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)
- @dkigen to create