...
- qWeek: (~ Weekly) Review Collaboration Roadmap
- qMonth: Review ohri tickets in Jira
- qQuarter: Review what's already going on in the OpenMRS community roadmap here
The plan re Agenda for Next Technical Check In:
- Packages update
- Dispensing update
- Lab orders update
- Assessment update (feature comparison/gap analysis and Modules review)
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:
- 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
...
Collaboration Roadmap
Color Legend: Status |
---|
| |
---|
subtle | true |
---|
colour | Yellow |
---|
title | PIH |
---|
|
Status |
---|
| |
---|
subtle | true |
---|
colour | Grey |
---|
title | Ampath |
---|
|
Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
Status |
---|
| |
---|
subtle | true |
---|
colour | Blue |
---|
title | OpenMRS Inc |
---|
|
BE = Backend FE = Frontend |
| Done/Resolved
| Now
What We're Working on Today | Next
Next Priorities* |
Programmatic |
|
Panel |
---|
| Concept Validation with Sites & CDC HQ program teams Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
|
Panel |
---|
| HIV HTS & C&T Prototype Validation with Sites & CDC HQ program teams Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
|
Panel |
---|
| COVID Prototype Validation with Sites & CDC HQ program teams Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
|
Panel |
---|
| COVID Prototype review: Clinical OMRS Community SMEs (TAP Call - Dec 15) Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
|
|
|
Technical |
Panel |
---|
| OHRI Demo Bug Clean Up Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
|
|
Panel |
---|
| DB Flattening - get reporting working with new paradigm Meeting w/ PIH re PETL. Interested in SQL approach. Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
Status |
---|
| |
---|
subtle | true |
---|
colour | Red |
---|
title | PRIORITY |
---|
|
|
Panel |
---|
| COVID Prototype review: Packaging Technical Review (TAC Call - Dec 13) Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
|
Panel |
---|
| Service Delivery Queues Requirements: Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
Dev: Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
Core Dependencies: Cohort Module (BE), Patient List Functionality (FE) |
Panel |
---|
| COVID Dashboard Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
Core Dependencies: Cohort Module |
Panel |
---|
| COVID Package widgets Status |
---|
| |
---|
subtle | true |
---|
colour | Green |
---|
title | UCSF |
---|
|
- COVID Assessments
- COVID Tests
- COVID Vaccinations
- COVID Outcomes
Note: Applying OMRS Package schema depends on microfrontending architecture (lerna monorepos) |
Panel |
---|
| Migration Plan & Materials Overview done by Status |
---|
| |
---|
subtle | true |
---|
colour | Blue |
---|
title | OMRS Inc |
---|
| here Packaging architecture being defined by Status |
---|
| |
---|
subtle | true |
---|
colour | Blue |
---|
title | OMRS Inc |
---|
| here Status |
---|
| |
---|
subtle | true |
---|
colour | Red |
---|
title | SHARE? |
---|
|
|
|
Panel |
---|
| Prep to microfrontend UCSF-OHRI Repo to be created into a lerna monorepo Eudson lead review to i.d. any dependencies? R/v with Narupa, JJ, others? What core needs are missing that are needed in Community Code / Shared Assets? Status |
---|
subtle | true |
---|
colour | Red |
---|
title | Blocker |
---|
|
|
Panel |
---|
| Embedding Pt Chart Features into Forms Status |
---|
subtle | true |
---|
colour | Red |
---|
title | Blocker |
---|
| Unclear who will lead design
(Problem: Current silo between Form-Entered vs Widget-Entered Allergies, Drug Orders, Conditions, Appointments, Immunizations) |
Panel |
---|
| Leverage existing squad work Test Results Drug Orders Service Summary & Enrollment Vital Signs ...and more |
|
- Updates/To-do check ins
- 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
- 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 |
---|
|
-