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).
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.
Based on yesterday’s quarterly Scrum of Scrums I would like to propose several design topics:
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.
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.
@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.
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.
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.
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.
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
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.
