Developing the "OCL for OpenMRS" Application

(Muhozi Emery) #339


The sprint planning will start in 10 minutes. You can join it from here:

CC: @dkayiwa @darius @alexmochu @nesh @emmabaye @michy @ian

(Muhozi Emery) #340

Thanks everyone who attended the sprint planning. Those who missed it can find the recorded video here.

(Darius Jazayeri) #341

Actually, stepping back, a better UX for this would be to indicate which fields are required/optional up front, e.g. by have a red * by all the required field labels. (Alternately since this form has ~6 required fields and 2-3 optional fields it would be okay to just mark the optional fields with an “(optional)”, but the first approach is probably more standard.)

It would be more helpful to include a quick snapshot of the output of sprint planning. The typical question someone would have is “what work was prioritized” and I’d rather not watch a video to find this out. Approaches that would be nice:

  1. include a list of the ticket summaries
  2. screenshot of the JIRA board
  3. link to the JIRA board

(Darius Jazayeri) #342

PS- when I look at the JIRA board I see a lot of tickets there, definitely not just one sprint’s worth. How are we using this? Since you’re doing 2-week sprints I would expect to see a board that contains multiple sprints in it (one active and all the rest closed).

Also, once work is completed, tested, and showcased, it should be marked as closed. I see a lot of tickets that are still open even though all their subtasks are closed, like this one:

We should do a round of user acceptance testing by me +/- others (@ball, @akanter). Can the team start by doing a pass through and closing off anything that’s clear and requires no feedback, and give me/us a list of tickets that are ready for UAT?

(Muhozi Emery) #343

@darius Thanks for the feedback. Sorry for not sharing the links here. There is a prepared wiki page stating the goals of this sprint and it includes the summary of the tickets with other useful links for the sprint planning. That wiki page can be found here. You can also find the JIRA board here

In addition to that, there is an announcement made here

(Muhozi Emery) #344

@darius Thanks for pointing this out. Before it was thought that we should have one sprint board with all issues. But after your feedback, It was changed, we have one active sprint board, the other one was closed. Now, you can check the board with the issues that will be worked on during this sprint here.

Regarding UAT, Yes, We’ll take time and pass through and closing anything that’s clear without any feedback and give you the list of the tickets ready for UAT. From now on, once the work is completed and showcased we’ll close its ticket.

CC: @dkayiwa @alexmochu @nesh @emmabaye @michy @sheriff @abulojoshua1

(Muhozi Emery) #345

Hello Everyone,

We are about to finish 10th sprint of OCL for OpenMRS, and we are looking to demonstrate what has been during this sprint.

We’ll appreciate your availability and hear from you about what has been done. So, we’re requesting you to vote for the demo day. Please vote the demo here

For what we have been working during this sprint, check the following resources:

10th Sprint of OCL for OpenMRS Announcement

10th Sprint of OCL for OpenMRS Wiki Page

CC: @darius @akanter @dkayiwa @michy @ianduncan @sheriff @abulojoshua1

(Daniel Kayiwa) #346

Will you also give a text summary, with screenshots, for what has been accomplished, for those who may not attend the demo or have time listening to the recording?

(Muhozi Emery) #347

@dkayiwa Yes, I’ll do.

(Muhozi Emery) #348


Thanks to everyone who voted for the demo day. The time voted for the Demo of tenth Sprint is Monday, 5th November from 5:00 PM to 6:00 PM EAT. The calendar event will be created soon and you can join the demo using the following link:

CC: @darius @akanter @dkayiwa @michy @ianduncan @sheriff @abulojoshua1

(Muhozi Emery) #349


Due to the service we’re using, the new sprint demo call link will be shared before 30 min of the Demo time. Sorry for the for the inconvenience.

CC: @darius @akanter @dkayiwa @michy @ianduncan @sheriff @abulojoshua1

(John Joshua Abulo) #350


I would like to know which API endpoint I can use to implement a search through sources in the OpenMRS Open Concept Lab, I would like to get done with a task in this JIRA ticket but even after going through the OpenMRS OCL API documentation, I still cannot seem to find the API endpoint I can use to successfully finish complete the JIRA ticket.

(Muhozi Emery) #351

Hello everyone,

I would like to let you know that we’re preparing for the release of OCL for OpenMRS MVP :rocket:. In this previous sprint, we were implementing the feedback we have received in the last demo. and I want to raise a blocker that hindered us from releasing the MVP on time and we would like to share it with you because we want to release MVP in this next sprint. The blocker is related to the UI/UX. In fact, we have the wireframes without mockups and this led to bad app UI/UX inconsistency. We can use tools like Figma for making the mockups, where a team can collaborate and agree on the UI including almost every detail like fonts and colors. One of the advantages using such a tool is that any stakeholder can use the tool to make suggestions, this can reduce the time we spend to rework on the UI.

Regarding this blocker, there are some tickets that waited to be discussed on because there are changes that have made which are different from the wireframes.

We’ll appreciate you to share what you think about this, here or during the demo call.

@darius @akanter @dkayiwa @michy @ianduncan @sheriff @abulojoshua1

(Muhozi Emery) #352


I would like to remind you that the tenth sprint demo will start in next 15min, you can join the demo using the following Google hangout link:

CC: @darius @akanter @dkayiwa @michy @ianduncan @sheriff @abulojoshua1

(Ellen Ball) #353

@muhozi Any chance this is recorded?

(Ian Duncan Abidha) #354

Hello Community,

We are excited to announce the eleventh sprint for Open Concept Lab for OpenMRS(OCLOMRS). The sprint planning session is scheduled for tomorrow on Tuesday from 5:00 PM to 6:00 PM EAT(East African Time). I will update you with the link to the session call 30 minutes before.


CC: @darius @dkayiwa @akanter @michy @muhozi @abulojoshua1 @sheriff

(Muhozi Emery) #355

Thanks for everyone who attended the tenth sprint demo. For those who were not able to attend the demo call here is the video record:

@ball yes it was recorded.

CC: @darius @akanter @dkayiwa @michy @ianduncan @sheriff @abulojoshua1 @ball

(Muhozi Emery) #356

Here is the summary of the tickets that were worked on in the previous sprint:

CC: @darius @akanter @dkayiwa @michy @ianduncan @sheriff @abulojoshua1

(Ellen Ball) #357

Some basic testing of OCL for OpenMRS. These are some very nice features and many things that work, but there are some issues:

Create a new concept

  1. Message says to set organizations in OCL. I have plenty of organizations in OCL, but they don’t appear in OCL for OpenMRS. (figure 1 and 1a)
  2. Won’t save a new synonym, and the error message isn’t helpful. It should be possible. (Figure 2)
  3. Language doesn’t save. When you return to edit the concept, the language is always English. (Figure 3)
  4. It does not save an incorrect uuid (ie. 777), but it does show an error.
  5. It’s good that you are using “Language” instead of “Locale” but then it’s inconsistent with using “Preferred in locale”. Pick one: locale or language.

Add a concept

  1. There should be better paging thru long list of concepts. It only allows >> and << but should allow first, last, and associated number of 20 concept groups (Figure 5). Maybe even allow the user to change the number for default (20) to 50 or 100 concepts (next phase).
  2. Allow view of all concepts from this page. If the concept is not editable (ie. because it’s from CIEL?), it should still allow a view. There should be a way to expand to see all the names and uuid. (Figure 6).

Figure 1

ocl-err1a Figure 1a

Figure 2

Figure 3

Figure 5

Figure 6

FYI @darius

(Muhozi Emery) #358

@ball Thanks for the feedback. We’ll work on those issues.