3 Steps to Review our Collaboration Status: 

1. qWeek: (~ Weekly) Review Collaboration Roadmap
2. qMonth: Review ohri tickets in Jira
3. qQuarter: Review what's already going on in the OpenMRS community roadmap here
4. qWeek: (~ Weekly) Review Collaboration Roadmap
qWeek: Review ohri tickets in Jira

Agenda for Next Technical Check In: 

• Packages update
• Dispensing update
• Lab orders update
• CBS & LIS integrations → FYI on ongoing work
• Assessment update (feature comparison/gap analysis and Modules review)
• Algorithms and Flags: Can we review approaches for each
• Confirm alignment on Clinical Views; JSON config idea
• Update on Branding
• Update on Generic Widget
• Diagram

UgandaEMR: Cervical CA screening use case for 3.x; plan to do gap analysis. Plan re. migration path: 3.x first; ohri next

Other Assets:

• * New * OHRI Packages Content Inventory https://docs.google.com/spreadsheets/d/1eUcR_ygvL0Pxt26Q7iSwa9XJceVHWNihY-VXw0o2ij8/edit#gid=0 
• 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

...

• PM Check-ins
  • Updates/To-do check ins
    • Next step for designs:
      • homepage
      • permissions
      • dispensing module
    • Next step for packaging OHRI packages
    • Plan for working together with Nirupa
    • Lab Orders
    • Need: OCL: Concept Support in Iniz (Support for Concept Name, Synonyms)
      • TODO: Grace f/u with team working on this 
        • https://github.com/mekomsolutions/openmrs-module-initializer/issues/140, https://talk.openmrs.org/t/how-concept-names-are-breaking-dbsync/34776/9?u=burke, https://github.com/mekomsolutions/openmrs-module-initializer/issues/141, https://github.com/mekomsolutions/openmrs-module-initializer/issues/136 
  • Cohort Module Next Steps
  • Packaging reports
  • Concept Codes across distros (map concepts across different distros semantically)
  • FHIR Module ticket - endpoint for encounters 
• 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
  • Move to lighterweight set; easier to merge / use things that will compliment implementers' distribution. Ability to pick and choose → microfrontends. Plan to split up - starting with form engine (Otherwise people have to take whole thing). May run into dependencies. 
  • "Programmatic side" - who is responsible for what? e.g. PATH for implementation - what does that mean for validating work thus far? 

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)

•   
•  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
  • 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

•