Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 15 Next »

3 Steps to Review our Collaboration Status: 

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

Other Assets:

  • 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


Questions for This Week

  • Programmatic work: Gap Analysis framework to share? Lead similar approach of __ EMR vs OHRI & 3.x Demo?
  • OHRI as library/package/toolkit vs as distribution
  • "Programmatic side" - who is responsible for what? e.g. PATH for implementation - what does that mean for validating work thus far? 


Collaboration Roadmap


Color Legend: PIH AMPATH UCSF OPENMRS INC

BE = Backend FE = Frontend


(tick) Done/Resolved

(plus) Now

What We're Working on Today

(lightbulb) Next

Next Priorities*

Programmatic

Concept Validation with Sites

UCSF


Technical

UI Review: 3.x Demo vs OHRI Demo

Comparison of existing 3.x Demo/Community Assets vs OHRI Demo OMRS INC

OHRI Demo Bug Clean Up

UCSF 

Service Delivery Queues

Requirements: UCSF

Dev: UCSF

Core Dependencies: Cohort Module (BE), Patient List Functionality (FE)

COVID Dashboard

UCSF 

Core Dependencies: Cohort Module

Dictionary Manager Useage & Feedback

UCSF OMRS INC

Core Dependencies: Cohort Module

Drug Dispensing

BLOCKER - UCSF design? (PIH did requirements; ready for Dev)

PM: PIH OMRS INC

Design: SHARE?

Migration Plan & Materials

Overview done by OMRS INC here

Packaging architecture being defined by OMRS INC here

SHARE?

Embedding Pt Chart Features into Forms

BLOCKER Unclear who will lead design

(Problem: Current silo between Form-Entered vs Widget-Entered Allergies, Drug Orders, Conditions, Appointments, Immunizations)

Leverage existing squad work

Test Results

Drug Orders

Service Summary & Enrollment

Vital Signs

...and more

Database Flattening 

#ohri Jira Tickets List

key summary type created updated assignee reporter priority status

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels