3 Steps to Review our Collaboration Status:
- qWeek: (~ Weekly) Review Collaboration Roadmap
- qMonth: Review ohri tickets in Jira
- qQuarter: Review what's already going on in the OpenMRS community roadmap here
- qWeek: (~ Weekly) Review Collaboration Roadmap qWeek: Review ohri tickets in Jira
The plan re
Other Assets:
- OHRI Packages Content Inventory
- UI Review: A side by side comparison of 3.x Demo vs OHRI Demo Sept 2021
- Shared Assets Doc: Explains Shared Assets vs Package-Specific Assets, and breaks down OHRI examples.
- Architect Role Descriptions: OpenMRS recognizes the need for the roles spelled out in this document. Shared Assets require a pretty high-skilled developer, architect level person, to design them before a mid-level dev can work on them. Mid-to-junior devs need this kind of support in order to successfully work on shared assets. OpenMRS has some dev/5’s like this but not enough. The roles described in this document aim to address that gap.
- Analytics Team needs: A detailed proposal for what team resources would be needed to thoughtfully address OpenMRS reporting challenges at scale.
- OHRI Wiki Roadmap
To-Do's:
- Grace & Eudson 1:1: Plan re MF-ing/code breakdown; how Nirupa can support
- 2022 Priorties:
- Schema: address features that extend the schema; whether these need to be part of the standard
- MF-ing/code breakdown
- DB Flattening approach
- Interoperability with DISI
- Form Engines: review of strengths (lower priority; even reconcile)
Collaboration RoadmapColor Legend: BE = Backend FE = Frontend | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
What We're Working on Today |
Next Priorities* | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Programmatic |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Technical |
|
|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Done/Resolved
Now
Next- Questions for This Week
- Updates/To-do check ins
- Package: Next step for packaging OHRI packages: draft package content; draft package schema
- Goals for Nirupa / plan for working together with Nirupa
- Shared Asset Topics
- Dispensing Module
- Lab Orders
- Homepage & program dashboard
- Access Control/permissions
- Automatic Patient Lists
- PM Check-ins
- Follow-up items
- Need: OCL: Concept Support in Iniz (Support for Concept Name, Synonyms)
- TODO: Grace f/u with team working on this
- Cohort Module Next Steps
- Need: OCL: Concept Support in Iniz (Support for Concept Name, Synonyms)
- Follow-up items
- Discussion Topics
- Packaging reports
- Sri & Fitti
- OHRI Package things: OMRS not expecting to maintain (Shared Assets yes, OHRI package-specific widgets no.)
- OHRI as library/package/toolkit vs as distribution → Suite of tools available to various sites
- "Programmatic side" - who is responsible for what? e.g. PATH for implementation - what does that mean for validating work thus far?
- #ohri Jira Tickets List
Jira Legacy server OpenMRS Issues columnIds issuekey,summary,issuetype,created,updated,assignee,reporter,priority,status columns key,summary,type,created,updated,assignee,reporter,priority,status maximumIssues 30 jqlQuery labels = ohri AND resolution = unresolved serverId 45c5771b-fa4b-3e43-b34a-c19dc45ccc95