Propose a Design Forum Topic

meetings
design-forum
Tags: #<Tag:0x00007f13b0e7cf00> #<Tag:0x00007f13b0e7cd48>

(Darius Jazayeri) #23

On Monday March 19 I would like to discuss this on an OpenMRS design call:

Specifically, this is work that a team is about to start doing for a Bahmni implementation project, and they’re asking for design feedback up front, when it’s easier to incorporate. And so that the output can be more generally useful for Bahmni (and presumably for OpenMRS too).

FYI @mseaton, @mksd, @jdick , @nkimaina, @pramidat

(Also FYI @paynejd since this will preemput our scheduled OCL discussion. But I promise to send some mockups soon.)


(Burke Mamlin) #24

We would like to discuss the work on the Condition Lists for Ref App work done in the OMRS17 hackathon for inclusion in RefApp 2.8 on the next (Wed, 11 April) design forum.

At least a quorum of @darius, @ssmusoke, and @burke should be in attendance. If @insiderish is able to join, that’d be swell. :slight_smile:


(Ellen Ball) #25

Super. PIH will join the discussion. We appreciate the emphasis on the work.


(Andrew Moko) #26

That’s great!


(Darius Jazayeri) #27

Based on yesterday’s quarterly Scrum of Scrums I would like to propose several design topics:

  1. Data Warehousing and Analytics

    • Description: The eSaude team wants to work on data warehousing and analytics in the upcoming quarter. They are interested to learn about existing work by Bahmni and PIH, to understand if they can leverage one of these approaches.
    • Required attendee(s): @ningosi, @valvijo, @pramidat, @mseaton
    • Desired Timing: eSaude should comment on this
  2. UI Dev Conventions

    • Description: A lot of JS development is happening these days, it feels very scattered, and many people don’t know what the current best practices are or what code/libraries they should be starting from. Let’s have a call to see if we can identify good practices and reusable components being used in recent development, and document them in an obvious place.
    • Required attendee(s): @dkayiwa, @darius, (@raff), @darius, @burke, @mogoodrich
    • Desired Timing: no preference
  3. OCL for OpenMRS


Design Time for UI Dev Conventions
Design Time for Data Warehousing and Analytics
Design Time for OCL for OpenMRS
Design Forum 2018-05-30: UI Dev Conventions
(Darius Jazayeri) #28

A post was merged into an existing topic: Design Time for UI Dev Conventions


Design Time for Appointment Scheduling
Design Time for UI Dev Conventions
(Stephen Senkomago Musoke) #29

A design call to discuss approaches for simpler appointments scheduling, whether this can be based on the current appointment scheduling or a new module based on Patient Appointment Scheduling - Integration with other forms

Required @mseaton @mogoodrich @ddesimone @darius @dkayiwa (hoping to leverage Andela team), @burke @mksd (Did you need something like this some time ago, it may have skipped my mind) @wyclif


(Dimitri R) #30

@ssmusoke see the second half of my message here about my opinion about having yet another appointment scheduling module.

So there are already two appointment scheduling OpenMRS modules out there, there should be a way to not create a third one…

Otherwise, on the principle, I support moving forward enhancements of the appointment scheduling feature and achieving a better integration with other tools/screens/APIs in OpenMRS and its distributions.


(Mark Goodrich) #31

Adding Order Status for Orders

Description: The PIH team is looking to build functionality for “Order Tracking”, and adding a “status” to Orders would help to facilitate this.

Required attendee(s): @burke @darius @mseaton @mogoodrich

Desired Timing: ASAP (just not the one starting in 15 minutes)


Design Time for Adding Order Status for Orders
(Tunmise Ogunniyi) #32

Following up with the discussion here(Order Entry UI Sprint 7 Progress), we would like to schedule a design forum.

Title: Discuss/finalize the Consolidated Order Entry UI design/flow.

Description: Consolidated Order Entry UI is a proposal from @ddesimone, more details about it can be found in this Talk post.
A team of developers from Andela(which I am a part of) has started working on the initial design provided in the Talk post and here is a link to the sprint announcement Order Entry UI Sprint 7 Announcement.
However, there have been a lot of feedback given on the initial design(here and here) which has to be integrated into what is already existing. This call is meant to help facilitate the discussion on how to integrate the feedback provided into what is already existing.

Required attendee(s): @ddesimone, @dkayiwa, @mogoodrich, @jteich, @darius, @mseaton, @burke, @efosa, @topseysuave

Desired timing: Next Available Slot(16th July 2018).

cc: @jthomas


Design forum to discuss/finalize the Consolidated Order Entry UI design/flow
Order Entry UI Sprint 7 Progress
(Burke Mamlin) #33

2 posts were merged into an existing topic: Design forum to discuss/finalize the Consolidated Order Entry UI design/flow


(Burke Mamlin) #34

A post was merged into an existing topic: Design forum to discuss/finalize the Consolidated Order Entry UI design/flow


(Ryan James) #35

Title: Adding end-to-end test automation to OpenMRS applications

Description: Several times a year we run a suite of front-end tests to validate core scenarios in the Esaude POC. We run these tests manually which requires a dedicated team and several months of work. During the spring of 2018 we developed an end-to-end automation tests framework–using CodeceptJS and puppeteer–to run tests automatically. Since then we’ve automated several tests in our suite to run in under 5 mins total, tests that previously took hours to run manually. We think this work is important because it will allow us to validate core scenarios much more frequently–on a daily basis before new code is checked in rather than on a quarterly basis–which should result in less regressions and more time for new features. We still have quite a bit of work to do, but would like to present what we have done so far in hopes it resonates with others in the community.

Goal: Present our end-to-end automation framework and discuss ways that it can be improved upon and used by others members of the OpenMRS commuity.

Required attendees: @valvijo @janflowers @ningosi @asacur

Desired time: Early Aug

cc: @jthomas @burke


Design Time for Adding end-to-end test automation to OpenMRS applications
(Stephen Senkomago Musoke) #36

I would like to suggest a design call to look at Ampath Form Builder technology and lessons learned implementing it as part of the process of working towards Point of Care + Retrospective Entry - Advice, Experiences and Best Practices

Needed @jdick Nicky Kimaina @darius @slubwama @slubwama1

@ddesimone @mogoodrich - would love to hear how this compares with your experience with Bhamni forms

@mksd @mksrom Ideas and comments given your current working with Bhamni Forms


Design Time for Ampath Form Builder technology and lesson learned
(David DeSimone) #37

Hi, can we have a Design Call tomorrow June 25 for data model or other design questions for the Oncology module we are building as part of the 3 week IBM Health Corps engagement?

We are midway through the engagement and it’s important to get through some of these questions as soon as possible. We will post something for review tomorrow morning. Sorry for the short notice.

I would be great to have: @ddesimone @mseaton @mogoodrich @burke @darius @jdick @jteich

Thanks! Dave


Design Time for Oncology Module
Design Forum 2018-07-25: Oncology Module
(Jamie Thomas) #38

Those watching this post would love to get your thoughts on Issues Arranging Design Forum Calls


(mona saleh) #39

title: clinical decision support using (Snake disease model) and linking it to the signs and symptoms and treatment and cure from the disease that the patient has. description: snake disease model has a template like the one in these episodes: https://www.youtube.com/watch?v=tsWLoJeCU48 desired attendees: clinical informaticists desired timing: whenever appropriate :slight_smile:


(Daniel Futerman) #40

Title: Google Summer of Code 2018 - After Action Review

Description: GSoC 2018 has come to an end, and it’s time to reflect on this year’s program and all the great contributions made by students and mentors alike, as well as looking forward to GSoC 2019 and how we can apply new learnings to making next year’s program a success.

Required attendee(s): @burke, @c.antwi, any #gsoc2018 mentors and students, and NB: anyone interested in administrating GSoC (or other OpenMRS internship programs) in future.

Desired Timing: Monday 27th August


GSoC 2018 - Final Evaluations
Design Time for Google Summer of Code 2018 - After Action Review
(Kaweesi Joseph) #41

Title: More patientSearch filters such as age and gender

Description:

Required Attendees: @darius, @dkayiwa, @wyclif

Desired dates: 5, 10, 12 september


Design time for More patientsearch filters such as age and gender
(Burke Mamlin) #42

2 posts were merged into an existing topic: Design time for More patientsearch filters such as age and gender