Wiki Spaces


Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack


Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents

titleHelpful Links

Where: TAC calls at

When: See the Community Calendar at or this GCal event

Notes: Find this page at

Parking Lot: Topics for Subsequent Meetings

  1. Feb 2023:
    1. GSOC mentors
    2. Form Engine Discussion
    3. Encounters Modelling given O3 Components
    4. CQL Engine & CDS Alerts: Work done last quarter and plans forward - Grace
    5. F/U on Encounter Concern
    6. Daniel - present Backend & API Roadmap, get feedback

Meeting Notes

Goal of this meeting: Review technical/platform/product decisions; response to issues coming up from community and help set/endorse clear technical direction.
Zoom link:

titleDetailed Table of Contents

Table of Contents


Attendees: Daniel, Grace, Hadijah, Anjula, Rafal, Romain, Juliet, Vineet, Burke, Mike, Mark, Piumal, Dennis, Ian, Eudson, Fred, Jayasanka, Pius, Joshua, Herman, Joshua

Form Engine Discussion

  • 90% of what's in React Engine is what Angular Engine already supports, with a few additional features that Angular Eng didn't have. If we stop needing to support Angular out of the box, we can reduce the app shell file size ++ (b/c we currently embed ++ files we need to run Angular) - would no longer need this in all distros!


  • TAC Blessing: Approved (smile) With following requirements: 
    • Not Block O3 RefApp Releases: For now we will continue using Ampath in the RefApp. 
    • Schema: Need definition people can reference and make comments/PRs to. E.g. HFE Schema tag references has proven ++ valuable: HTML Form Entry Module Reference 
    • Technology Audit: e.g. formik has died off (was major react library for years) - if we're using assets like this we should test running w/ alternative(s) like React Form Hooks (& a few hours refactoring if needed) → UCSF will start looking at the cost of changing, next week
  • Next steps: UCSF team will start this work; tickets will be created on what needs to be done, including work to generic-ize some of the Fx originally made specific for OHRI
    • Start creating roadmap & tickets & MVP definition on dedicated call - e.g. O3 backlog review

Encounters Modelling given O3 Components

  • Bahmni addressed this by having time-outs for Encounters; if same provider does an action on a patient in a location within the time limit, all those actions they took get bundled within the same encounter. Mekom finds this does not work well. Agreement that this is not the approach we'd like. 
  • Or: Chart tracks some encounter-context → Burke's proposal to add "Encounter Session




  1. Standups: 
    1. Vineet - fixes on Patient Summary, enforcing visits to order drugs, fix to Address Hierarchy bug that was clearing fields
    2. Suruchi - CQL & ANC project work
    3. Ian - Rest authentication issue i.d.'d by Bahmni, fix for recent Security issue reported, pr reviews
    4. Dennis - releases on esm repos, cohort builder app, improvement to how obs grabbed from encounter get displayed in 
  2. Vision for 1 Form Engine: Intro & Heads up for next week’s deep dive - @grace & @eudson
  3. MedicationRequest blockers: Mapping MedicationRequest.validityPeriod.start and MedicationRequest.authoredOn from an OpenMRS order, see Duration and auto-expire date on orders - #14 by mogoodrich - @mogoodrich
    1. We will move forward with the suggestions in this ticket:
      serverOpenMRS Issues
      1. order.dateCreated maps to MedicationRequest.authoredOn (and vice versa)
      2. order.dateActivated maps to MedicationRequest.dispenseRequest.validityPeriod.start (and vice versa)
    2. Empty Encounters - Vineet
      1. Concern: Each clinical encounter should ideally be attached to a single OMRS encounter, so everything a clinician does for a patient is documented in the same encounter. Should be clear which encounter they're working within. 
      2. Plan: 
        1. Design Call: This encounter issue is something we need to bring up on a design call, because I’m unsure what the UI flow should be, but we need something similar to what we do with starting a visit.
        2. TAC Call f/u and confirm technical plan
  4. FHIR valueSets: Best practice ways to tag and refer to FHIR Value Sets? Global properties that reference uuids? ESM configs that reference uuids? some sort of tags? - @mogoodrich
    1. questions about the current mapping of concept sets to value sets (FM2-450) - resolved
  5. New O3 Release Cadence Kick-Off: what we want to include in the first new release this year for O3 → Deferred to O3 Planning call (1hr after this call)


Attendees: Jayasanka, Grace, Burke, Suruchi, Rafal, Dennis, Daniel K (all OMRS), Ian (Brown), komit (?), Steven Wanyee (intellisoft), Eudson Bambo, Wamz, Amos (all UCSF/OHRI), jonathan thembo (vol), Mark G (PIH), Joshua N (vol), Vineet (Mekom), Fred (ICRC Service Centre), Hadijah (Mekom), Kenneth Ochieng (IntelliSOFT)


Share recording w/ all, inc. Amos

    • Release Dockerization - Raff
      • Documentation to follow to come. Updates on Talk. And in 2 wks. Anncouncemtn of these images being available. Mark (PIH) and Fred (ICRC) and Amos (UCSF/OHRI) want to use.  

    • OSV-Scanner decision - Grace & Daniel
    • O3 Release flow  - getting to Beta
    • Config separation → Ian to look into splitting off config from distro
    • O3 Performance issues - Dennis & Jayasanka
      • Bundlesize analysis of esm-core: 
      • esm-patient-chart:
        • The good news: We have bundle size monitoring set up for all our repos. Big question now is how to tackle this problem. This is Dennis' next focus. 
    • Date Config - Grace