Propose a Design Forum Topic

Next Monday works for me.

Thank you for suggesting this @darius Sync 2.0 architecture draft has been moved to Monday, July 17.

Need to have a call for Reporting Enhancements based on this thread Reference Application 2.7 - Simplifying Reporting Module - Documentation, Pre-built Reports, Higher Level Abstractions next Monday July 24, 2017

@mseaton @raff @mksrom @k.joseph @judeniroshan @dkayiwa @aolaniran @reddberckley, @fortune, @femi, @ethan, @enahomurphy - can you make it?

2 Likes

@ssmusoke, yes I should be able to attend.

@ssmusoke, Monday would do. Though I am in ICT time zone (South East Asia: UTC+7) so I am afraid I won’t be able to attend if it is after 4pm UTC.

We’d like to schedule a design discussion for incorporating the idgen module into the Platform.

  1. Title: “Incorporating the idgen module into the Platform”

  2. Description: We have set a goal of incorporating idgen within the Platform. We will be discussing IDGEN-33 and IDGEN-42 and come up with action steps & assignments to complete them.

  3. Required attendee(s): @mseaton, @darius, @burke

  4. Desired timing: Next open slot.

Additional detail

Following up on the discussion from Updating OpenMRS Radar for 2017, we’d like to schedule a design forum to update our Technology Radar.

  1. Title: “Updating OpenMRS Technology Radar for 2017”

  2. Description: Reviewing and updating the radar.openmrs.org data for 2017

  3. Required attendee(s): @darius, @mseaton, @pascal, @wyclif, @burke

  4. Desired timing: Next open slot when attendees are able to join

1 Like

From Error Editing voided property.

Title: Unvoiding/Unretiring via REST Description: Standardize on a REST API for undeleting (unvoiding data, or unretiring metadata) Timing: next available

1 Like

We’d like to schedule a call for

Title: “Module to collect data from user-related forms”

Description: The discussion will focus on developing a module, or enhancing an existing one in order to capture data that is not directly linked with patients, but part of the implementation. For example, recurring data related to facility performance or feedback from community health workers, etc.

Required attendee(s): @maimoonak, @ningosi, @rabbia.hassan, @darius, @shujaat

Desired timing: Next open slot on Wednesday when attendees are able to join.

1 Like

Title. Refactoring RefApp UI (login, landing page) to use Javascript+REST to promote greater collaboration

Description. During OMRS17, we had a session specifically discussing ways we could create greater collaboration beyond the platform (notes). One of the action items from that discuss was to refactor the main UI components of the Reference Application (specifically, login page & landing page, then maybe dashboard ±visit page) to use contemporary development techniques that we want to promote –i.e., React or Angular against REST, npm, maybe webpack or similar technologies. As Darius put it (paraphrasing): “I don’t want to devs to have to learn extra OpenMRS-specific steps in order to add an app to the RefApp.”

Goal: Determine strategy for refactoring login page and landing page, including technologies/approach to be used and draft action plan. Our intent to complete this refactoring before GSoC starts in May.

Required attendee(s). @darius, @dkayiwa, at least one of @wyclif & @raff if we can’t have both.

Others I know may be particularly interested: @mseaton, @mogoodrich, @ssmusoke, @jdick. Of course, we’d love to have anyone join who can help contribute toward our goal.

Desired timing. Next available slot (I’m covering inpatient service 9-26 Feb, so would like to fit in this call and, if we need it, a follow-up call before 9 Feb).

1 Like

for what it’s worth, I will be unavailable Jan 25th to Jan 30th, but feel free to have the call without me… I am interested in following this, though.

1 Like

Hi all,

I’d like to schedule a design session focused on improving concept dictionary management for OpenMRS using OCL. We had a preliminary discussion in January where we outlined 3 milestones that we hope to hit in 2018 so that OCL can be a more valuable tool for the OMRS community. This topic corresponds to milestone 2 in these notes: https://docs.google.com/document/d/1UjgF1GYuuI7tFsK3qGMT2efdmLeNaKpfbptajgw0Vxc/edit?usp=sharing

Thanks! Jon

Title. Implementing LDAP support in Atlas 3.1 project,

Description. During GSoC 2016, a new version of the Atlas server code was written in nodejs as the Atlas 3.0 Project, but this new, node-based server code was never fully deployed.Since in 2017 the authentication is switched to LDAP, it is needed to implement the same in atlas 3.1 project.

Goal: Determine strategy for designing the authentication module with LDAP and discussing other security related issues.

Required attendee(s). @burke @pascal @shekhar

Desired timing. 28 Feb (Since GSoc applications would start from 12th March).

1 Like

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.)

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:

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

That’s great!

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

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

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