Page Comparison

...

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

...