Meeting Notes

2024-12

Recording: O3 Squad Call_ December 5, 2024

Recording: O3 Squad Call_December 12, 2024

2024-11

Recording: O3 Squad Call_ November 7, 2024

Recording: O3 Squad Call_November 14, 2024

Recording: O3 Squad Call_November 21, 2024

Recording: O3 Squad Call_November 28, 2024

2024-10

Recording: O3 Squad Call_ October 3, 2024

Recording: O3 Squad Call_October 10, 2024

Recording: O3 Squad Call_October 17, 2024

Recording: O3 Squad Call_October 24, 2024

Recording: O3 Squad Call_October 31, 2024

2024-09

Recording: O3 Squad Call_ September 5, 2024

Recording: O3 Squad Call_September 19, 2024

Recording: O3 Squad Call_September 26, 2024

2024-08

Recording: O3 Squad Call_August 1, 2024

Recording: O3 Squad Call_August 8, 2024

Recording: O3 Squad Call_August 15, 2024

Recording: O3 Squad Call_August 22, 2024

Recording: O3 Squad Call_August 29, 2024

2024-07

Recording: O3 Squad Call_July 4, 2024

Recording: O3 Squad Call_July 11, 2024

Recording: O3 Squad Call_July 25, 2024

2024-06

Recording: O3 Squad Call_June 6, 2024

Recording: O3 Squad Call_June 13, 2024

Recording: O3 Squad Call_June 20, 2024

Recording: O3 Squad Call_June 27, 2024

2024-05

Recording: O3 Squad Call_May 2, 2024

Recording: O3 Squad Call_May 9, 2024

Recording: O3 Squad Call_May 16, 2024

Recording: O3 Squad Call_May 23, 2024

Recording: O3 Squad Call_May 30, 2024

2024-04

Recording: O3 Lab Squad Call_April 2, 2024

Recording: O3 Squad Call_April 4, 2024

Recording: O3 Squad Call_April 11. 2024

Recording: O3 Squad Call_April 18, 2024

Recording: O3 Squad Call_April 25, 2024

2024-03

Recording: O3 squad call_Mar 7, 2024

Another Mar 7, 2024 O3 recording

Recording: O3 Lab Squad Call_Mar 12, 2024

Recording: O3 Squad Call_Mar 14, 2024

Recording: O3 Lab Squad Call_Mar 20, 2024

Recording: O3 Squad Call_Mar 21, 2024

Recording: O3 Lab Squad Call_Mar 26, 2024

Recording: O3 Squad Call_Mar 28, 2024

2024-02

Recording: O3 Squad Call_Feb 1, 2024

Recording: O3 Lab Squad Call_Feb 6, 2024

Recording: O3 Squad Call_Feb 8, 2024

Recording: O3 Lab Squad Call_Feb 13, 2024

Recording: O3 Squad Call_Feb 15, 2024

Recording: O3 Lab Squad Call_Feb 20, 2024

Recording: O3 Squad Call_Feb 22, 2024

Recording: O3 Lab Squad Call_Feb 27, 2024

Recording: O3 Squad Call_Feb 29, 2024

2024-01

Recording: O3 Lab Squad Call_January 30, 2024

Recording: O3 Squad Call_January 25, 2024

Recording: O3 Lab Squad Call_January 16, 2024

Recording: O3 Squad Call_January 11, 2024

Recording: O3 Lab Squad Call_January 9, 2024

2023-12

December 21, 2023: O3 Squad Call Recording

December 14, 2023: O3 Squad Call Recording

December 12, 2023: O3 Lab Squad Recording

December 7, 2023: O3 Squad Call Recording

December 5, 2023: O3 Lab Squad Recording 

2023-11

November 28, 2023: O3 Lab Squad Call Recording

November 23, 2023: O3 Squad Call Recording

November 21, 2023 O3 Squad call recording

November 16, 2023 O3 Squad call recording

November 14, 2023 O3 Lab Squad call recording

November 9, 2023 O3 Squad call recording

November 7, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_xjukqajm

November 2, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_2dr1vyf1

2023-10

October 31, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_blwc31rt

October 26, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_440kqgfz

October 24, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_8yuf4h0j

October 19, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_0dcfmrts

October 19, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_ydvb2mpp

October 16, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_s443c5kb

October 12, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_2b8r9rf1

October 9, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_b9xysfsq

October 6, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_4nz4bc3n

October 5, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_hxdv3m4c

2023-09

September 28, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_t1qomzls

September 21, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_31myiqw8

September 14, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_4x2ps1rr

September 7, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_xpdwab7n

2023-08

August 31, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_3tucg34v

August 28, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_0dk93sso

August 24, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_7x50kd13

August 17, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_mloqr8qg

August 10, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_7y1m6qrk

2023-07

July 27, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_ord1cn4i

July 20, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_k5g1z544

July 17, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_i5bblazf

July 13, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_uf8s4v34

July 6, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_dyrceeln

2023-06

June 29, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_gnlehmig

June 23, 2023 O3 App shell deep dive call recording: https://iu.mediaspace.kaltura.com/media/t/1_01i0mvtw

June 22, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_iz6dam2h

June 19, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_mjd4mwr6

June 15, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_tenrx2u4

June 12, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_t450nz1h

June 8, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_g0k6v4je

June 1, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_ulv1sery

2023-05

May 25, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_c6k1hqn7

May 22, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_c82u1m7d

May 18, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_lj7zwxyo

May 15, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_qqwyamdd

May 11, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_p52yo6dx

May 8, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_eseltcz3

May 4, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_wy7c5wwx

May 1, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_7s6sxgrz

2023-04

Engineering Work Gaps: 

• Tasks: https://zeroheight.com/23a080e38/p/6226bc-task-management 
• "Flag toggle" https://zeroheight.com/23a080e38/p/851fea-patient-flags/t/687271 (Ian reviewed for feasibility; PIH interested)
• In-Form Actions (e.g. Enrol in Program)

April 27, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_c9exch7w

April 25, 2023 O3 Performance review call recording: https://iu.mediaspace.kaltura.com/media/t/1_gg58dzrl

April 24, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_s6m0u6f9

April 20, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_0whacci3

April 17, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_h0dk0dh1

April 13, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_vwci2vnn

April 6, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_qpshflfp

April 3, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_cn4xq29d

2023-03

March 30, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_m55o2qe6

March 23, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_hjsr052s

March 20, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_fgilrkc4

March 20, 2023: Design call recording: https://iu.mediaspace.kaltura.com/media/t/1_seeokv43

March 13, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_nzrv9fzr

March 13 2023 Design call recording: https://iu.mediaspace.kaltura.com/media/t/1_efn8msf8

Attendees: Paul A, Fiona A (PIH), David (PIH), Mark (PIH), Wamz (UCSF), Grace (OMRS)

March 9 2023 Design call recording: https://iu.mediaspace.kaltura.com/media/t/1_j1fest1u

Mar 2, 2023 O3 Squad Call: Recording: https://iu.mediaspace.kaltura.com/media/t/1_89la472a

Grouping Concern with Dispensing

Fiona: Just returned from SL Wellbody site; found that pharm users are tending to dispense drugs one at a time rather than in grouped list because they may not have all of the medications available in inventory. They also want to then close the order for the drug they didn't have, or put it into a "hold" of some kind (e.g. pt to return in a week), to indicate the order has been dealt with for now. 

Wamz: In past, system w/ stock mgmt had way of flagging what you didn't have. 

Next steps: Mark to query existing PIH useage data to see how often orders are done in group vs incomplete.

Fiona: Ppl who saw the UI were excited and hopeful. Already pretty much paperless, using PIH system at POC

Visit Notes

HFE supports a view mode. O3 Design Docs do show opening in read-only mode: https://app.zeplin.io/project/60d59321e8100b0324762e05/screen/61f3bc47a8db51b352d1a034 

Is this rendered by the form engine?

OHRI Example: Where form had already been filled, (lab order) - 2-step form

Home Page title

Certain users would want to go directly to certain pages when they log in. 

Design Input: Home screen should include Queues, but intent is not that the Home Page defaults to the equivalent of Queues. 

Headline should just be "Home"; Home becomes its own configurable app; or, default to what user likely to want, e.g. direct to queues

2023-02

February 23, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_q9bi91cw

February 21, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_767b3u5l

February 20, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_pfm0577x

February 20, 2023 Design call recording: https://iu.mediaspace.kaltura.com/media/t/1_u8r1ctak

February 16, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_41ruqtls

February 14, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_h1h5dtr7

February 13, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_uh0tzvsb

February 6, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_1k7v1sq7

February 2, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_f7h44h90

February 2, 2023 O3 Squad call recording: https://iu.mediaspace.kaltura.com/media/t/1_9au8x4nv

Grace Potma, Paul Adams, Burke Mamlin, Tendayi Mutangadura, Antongy, Cynthia Kamau, Dennis Kigen, Donald Kibet, Geert Meekers, Ian Bacher, Jacinta, J Teich, Joshua N, Lousa Yogo, Pius Piru, Samuel Lubwama, Samuel Male, Vineet Sharma, Wamathaga Kamau, Kennedy Makombe

Lab Orders Review:

• Can I just search without having to click into one specific category? Do order templates contain “type” of order?The ordertemplates module looks like it will need some changes to handle the option being selected, but the search part should be… ok-is

Palladium Pilot Findings w/ Appointments & Queues:

• Bahmni Appointments - Missed Definition different in Field: To retreive data clinicians wanted. Only able to track statuses - scheduled, checked-in, or missed. Users define honored as “checked in” AND “visit started” AND seen clinician - e.g. users who check in, then never get seen. 
• Service Queues Challenges: First facility quite small, didn’t need queue. 2nd facility, very many patients; use cards to monitor movement & priority. Need to organize who to see first - entries are ordered by wait time (and w/ emergency at top). Also need Queue Number. → Need number that can be called out, even displayed, publicly rather than name (due to sensitivity - e.g. instead "Jon Smith next please" can be "#44 next please"
  
  • Sounds very similar to needs i.d.'d in Uganda
  • Next steps:
    • Need Queue Number (e.g. service token/placard; via visit attribute) and/or Patient Unique Program ID (pt-specific number)
    • To add physical rooms to the Queue Module, both FE and BE. E.g. location: MCH, which can have multiple rooms. Any clinician able to see you should be able to grab you into their room. 
      • Potentially automating sending pts to different rooms. 
    • Role-based or location-based landing pages for appointments and queues. (Login location may come in handy)
    • (Later) Auditing, & Visualizing: How long they took at a given service point. Show a patient journey using service queues module. Patient journey i.e. Registration -> Triage -> Clinical consultation -> Lab -> Clinician -> Pharmacy – b/c for audit purpose want to record how/when they went from one point to the next. 

These multiple clicks become very 

One-click Visit Start: Proposal: Could we have smart values - e.g. Date, Time, Location, 

Proposal to change language to Check-in: UgandaEMR's "Check-in" combines several actions in the background (starts visit, on that day in that particular minute, at the location you're logged into

Pre-select Visit Type (e.g. default to what Appointment was made for), Default Urgency to "Normal" (can change if needed) (or even checkbox for Emergency)

Only thing that needs to be picked manually: Queue ("where am I sending this patient")

Grace to do: Change O3 RefApp demo data for Visit Type - currently too locations-based (different than Encounter type)

Auto-fills fields for you: 

If NOT found,

What if information is different - e.g. they've moved, changed number - you would edit and update, then click "Post to registry" (however right now the registry in Kenya doesn't allow these edits right now - more about are you in the registry or not)

Why have post to registry button at all? Why not do automatically with Save Registration?

UGEmr already doing this in background automatically. Samuel L likes idea of validate - explicitly share/update

OHRI: Checking if they exist in Registry is being done in search workflow

Samuel M: HOw to make this generalizeable given so many places have different MPI APIs?

OHRI assumes FHIR-compliant registry, via middleware (OpenHIM) which translates the mediators to FHIR. 

Samuel M: Thinking of translator strategy similar to FHIR2 Mod. 

Sam M would like to contrib to queues 

2023-01

TBD: 

• Design System & Design Components & Code Components and how to bring into greater alignment (Ciaran, Aline, Dennis, Grace; ?Ian, ?Daniel, ?Eudson, ?Pius, ?Samuel M) → ? dev work to look at the code components and see which are easy to refactor, e.g. content switchers, tide headers - next week or week after

2023-01-30: Design Call: 

• Allergies: See @Ciarán Duffy latest ideation (follow-up from last week) - moved to next week

Frontend "Encounter Context" & Visit Context - "You are here"

• Encounters & Visits: How we show users which encounter or visit they're working within at any given time. Should be clear which encounter / visit they're working within. Right now it's possible for them to unknowingly enter info against a completely different encounter/visit.
• Clinical Meaning vs Technical/Backend Meaning can be used differently 
  • E.g. PIH - Vitals Encounter for info entered in Vitals Form (very form-based; looking for O3 to support better than current form-based approach does. Form based approach not something we want to continue doing.).
  • Problem/challenge: O3 has pulled apart the "everything in 1" form approach. Need ability for multiple components to contribute to 1/the same encounter. Want encounter in the system to represent the encounter in real life. 
• Use cases: Why do we make multi-active possible at all?
• Logic for Closing an Encounter - E.g. Bahmni's implicit encounters - setting a timer when an encounter is created, any new data coming in w/in certain frame of time, goes in that encounter. If you're in different context, border color changes etc.
• Why do we allow multiple encounters or visits at once?

• Editing: E.g. Pt comes in for return HIV visit: Write note, orders, form for right now. See past mistake or issue in last month's encounter - I want to edit that. Or, patient has left, and I want to keep working on some documentation for that past encounter. Need to know explicitly "you are adding something to this encounter."
• Movement: E.g. Pt goes over to lab, billing, etc
• Multiple Providers: E.g. Nurse, Clinician, Social Worker - may be in same department/visit but different encounter. Implementation might decide to have everything in the same encounter. 

• E.g. When you order a drug it creates a Drug Encounter. We would like things to be logged against a single encounter - not one for the drug order, one for a form, etc etc. (Feature Architecture)

• E.g. Multiple Active Visits at once: End Modal should be clear about which one you're ending; how can UI make clearer which Active Visit you are adding information to?

• Confirm Order History plan - for now we'll proceed w/ simple table

Where do we go from here? Next Steps:

• Introduce encounter context → Burke → Talk post ongoing here
• Design time - user mental model; way to give them the context of what they're in → ____ (Grace f/u on how to fund...but, this is really a technical thing; e.g. Amazon - I want to cancel something in my orders. Go into order and select something in there. A little design that shows us how we put the encounter context in. Design tweak not design project.)
• Then - once Design Model done - Fix encounter model of Order Basket - orders should be part of your desired clinical encounter
  • TAC Call 

Debrief w/ Ian: Main concern is reporting. We had ok'd the encounter for Drug Orders just to keep that work moving forward. 

2023-01-23: Design Call

Attendees: Grace, Ciaran, Burke, Jonathan T, David D, Dennis 

• Lab Recent Results Summary Widget redesign ideas - Clinical Presentation - Grace & Ciaran
  • Decision: Remove Recent Results Widget for now, reconsider when w/ Order Status
  • Also partly covered by Clinical Summary designs
• Allergy form redesign ideas - Grace
  • Decision: Yes, redesign for entering 1 allergy at a time
  • F/U w/ Ciaran re. how to get designs done for Allergy form
• Advice: Single-tab forms - Grace

  • Decision: Remove page nav if 1 section form and qnr body will take over that space. Don't show nav if only 1 page. 

  • Dennis: Could we load the buttons as not part of the form but part of the workspace?
• Update on Lab Orders plan - Wamz/Grace/Paul
  • Designs for initial feedback coming later this week
• Way to show Order History (e.g. for Meds, Labs, etc...) esp. now that Orders page renamed "Medications"
  • TBD - need to think about it
• PIH Update: 2023 moving ahead seriously w/ O3. One goal is for new MCH centre for excellence in S/L (tentative opening mid-2024) 

2023-01-16: Design Call

Grace Ciaran JonT SamuelL Vineet Joshua

Joshua - flags

Bug & Improvement Ideas review - Grace

• Notes here, to be filed in Jira

Samuel L: How do you document someone's careplan over time? 

• If patient changes hands, instead of looking at entire Hx, what is the careplan for this patient? What is the condition, and how are we treating them for that specific condition? What is the treatment plan?
• Currently, careplans tend to be buried within text notes deep in the EMR. (insight found from Ciaran's research w/ high-risk-pt HIV clinicians in Kenya)
• Want structured, unlike sticky note which is not structured
• https://hl7.org/fhir/careplan.html 
• Eg: HIV: Pt receiving DTG for HIV, and DPG for TB; need for long-refills; Cancer: Chemo, Condition
• How do you organize patient treatment? Do we continue using orders as they are?

2023-01-09: Design Call

Agenda:

• Pt Summary: how to optimize this page? Where does the offline actions summary belong? How can we clean up the Recent Results view on the Pt Summary page?
• Medication Tab on Left - rename the current "Orders" page to "Medications": https://issues.openmrs.org/browse/O3-1737 - and how will we later show Order History - UX Design plan: A place in order basket for you to go to to see Order History
• Ordering drugs - how do we make the drug name more clear? https://issues.openmrs.org/browse/O3-1730

Plan for CarePlans? e.g.: Documentation of long refills - document how you decided right medication.Hard to represent care plan in active medications list.  Let's discuss next week in depth

Ability for user to enter something like: Consult Note, Imaging, Lab Test

Need to reorganize this so fields are thematically on same line:

Look at "Simple Orders" w.r.t. combining dose # & dose unit (mg)

Cull Pt Summary to have the widgets in the order shown here: https://app.zeplin.io/project/60d59321e8100b0324762e05/screen/60d59c8c1ff239bbe989d7d5 

Cards need max width - value too far

2022-12

2022-12-12: Design Call

Attendees: Christof (SolDevelo), Grace (OMRS), David (PIH), Beata Komorowska & Beata Zwidryn (SolDevelo), Ciaran (Sonder), Dimitri (Mekom), Fiona (PIH), Geert Meekers (SolDevelo?), Mark (PIH), Paul (Sonder), Ian Bacher (Brown), John Mark Esplana (ICRC), JJ (Ampath)

Full recording at this link here 1.

• Reports Dashboard for O3 End-Users By @christoforos of @SolDevelo: https://iu.mediaspace.kaltura.com/media/t/1_e35zda2t?st=250
• Dispensing Medications in O3 By @ddesimone of @PIH (Note that the demo is using a PIH distro, not the O3 refapp, hence the different drug ordering UI) https://iu.mediaspace.kaltura.com/media/t/1_e35zda2t?st=1681&ed=3059
• ICRC’s O3 Use Cases & New Features By @jesplana of ICRC https://iu.mediaspace.kaltura.com/media/t/1_e35zda2t?st=3059

• • Bulk RDE/Fast Form Entry
  • Group Visits
  • Patient Grid creation and use
  • Real-Time Clinical Analytics in SuperSet
  • New workflow tool in patient chart

SolDevelo/J&J: Reporting ideas + Feedback designs - Christof

Navigate report, select output, run it

Need to show users like clinicians a simplified UX in O3 visuals - without going through the big Sys Admin page. This resonated for both Dimitri/Mekom and David/PIH, b/c they have users who aren't necessarily sys admins. Dream for Mekom would be a one-button for "run all data exports". 

link to the newer prototype version

Ciaran to review and provide detailed design feedback

Dispensing

Dispensing form: 

Rx's being grouped by encounter. Allergies is working (hooked up to PIH 2.x). 

ICRC Demo: How ICRC is using O3 in a bigger HIS system picture 

• Fast data entry
• Group data entry
• Patient Grid
• Superset
• Offline use:

• Work on encryption – updates and timeline
• Fast data entry / group data entry

Many locations, diff countries: .

Form tabs are configurable

Grids:

Integration: OMRS & Superset

Data is streamed q 2 mins

Workflow / user journey:

2022-11

2022-11-07: Design Call - Service Queues with KenyaEMR & UgandaEMR

Participants: Samuel L (METS), Jonathan T (Vol), Antony (Palladium), Ciaran (Sonder), Cynthia (Palladium), David (PIH), Dennis (OMRS), Grace (OMRS), Isaac Akileng (METS), JJ (Ampath), Musa (METS), Pius (METS/OHRI), Solomon (METS), Vineet (Mekom), Piotr W (SolDevelo), Michael (Madiro)

Antony: KenyaEMR going live at a site on Wednesday: Registration, Appointments, Queing, at small site with selected providers. Goal is user feedback and refinement. Giving users new features. Will come back to this group w/ feedback from users on Appointments, Queues. 

Proposal for v2 of Service Queues by Samuel L: (previous Talk post here: https://talk.openmrs.org/t/o3-queue-workflows-from-station-to-station/36869) Sam L = Queues Lead

Example case of woman with stomach pain: sees OPD: Registraion Triage (combo), Clinician, Blood tests for Pregnancy and HIV, HIV positive so sent to HIV Clinic for confirmatory test → HTS Counselor → HIV Clinician → ART Dispensary. 2 docs, 2 lab people, 1 triage. 2 departments which refer pts to each other when certain program rules are triggered (eg HIV + → send for confirm test). Depts or clinics that operate semi-autonomous but also have referral workflows. 

UI: 9, 6, 5, 7, 8, 11

2022-11-10

Attendees: Dennis Kigen, Samuel Lubwama (METS), Joshua Nsereko (OMRS fellow), Pius Rubangakene (OHRI), Sharleen Awinja (Volunteer), Tendayi Mutangadura (Fellow), Vineet Sharma (Mekom), Juma Mukoova (Volunteer)

Sharleen and Juma introduced themselves to the group.

Juliet: spoke about her work on fixing the identifiers UI on the patient banner. Mentioned that she would file a PR soon.

Vineet demoed on his work on adding keyboard navigation controls to the patient search. He also gave an update on his patient search experience v2 work - mentioning that displaying recent search results was the last piece of the work. He also demoed his work on fixing the drug ordering experience. He had a query about whether a user should be able to record past medications.

Pius gave an update on OHRI's PMTCT work in Namibia. He also mentioned that he was working on the new form builder (helping advance Kumuditha's good work during his GSOC program) as well as fixes to the dispensing app. He had a query about configuring services types in the Services Queues application

2022-10

2022-10-27

Attendees: Grace P, Hadijah, Solomon (UgEMR/METS), Burke (Reg), Deb (Vol), Isaac Akileng (UgEMR/METS), Jacob Wasswa, Jonathan T (Vol), Joshua N (OMRS fellow), Juliet (Vol), Musa (UgEMR/METS), Pius (UCSF/OHRI), Vineet (Mekom)

Vineet: O3-1565

Hadijah: New type of notification / new component: Actionable Notification: (showActionableNotification function - can add, attach an action) - documentation added to repo. Let's also include in devdocs. 

Juliet:

Musa: UgEMR team working w/ Pius to solve a few issues encountered in OHRI. Bootcamp next week, team will be working to complete pulls for family health module, and handling service queues, and prepping for go-live. We will also be in touch w/ Hadijah about leveraging the cmty appointments module. 

Solomon: Re. Service Queues: Resolved their metadata and have all that's required for the queue module. Backend working fine. Trying to see today how the 2 can be combined (FE and BE). Samuel L in Kenya, talking to Palladium about how this can be achieved. Still some issues b/c of how they want to package their product - raised on Talk: ______ Esp. about how to have 1 single file to put at facility without internet and run it. Packaging is the slow down. 

Adjourned early. 

2022-10-20