GCI-2018 : New Ideas from GCI Students to improve OpenMRS

gci2018
Tags: #<Tag:0x00007f88c52c1140>

(Suthagar Kailayapathy) #1

Hi Students,

I have created this talk thread to have your ideas and thoughts in one place which can help OpenMRS for the future developments.

First, you need to claim one of these tasks from GCI dashboard :

  1. Research the UI issues in OpenMRS Ref Application 2.8.0

Then submit your work only to the GCI dashboard. Once your mentor reviewed and approved, then only add your ideas here. You should mention the approved Mentor name in the post here.

I would like to keep only the final version of ideas here (Having conversations or discussion for an idea in this thread may reduce the impact on other ideas here) So posts without approved mentor name will be deleted to reduce the number of posts.

Thanks.


Project Ideas for the Upcoming GSOC 2019
(Herbert Yiga) #2

@suthagar23 thanks for this


(Adrian Serapio) #3

Hi everybody! I have included a link here wherein I explored some UI issues in Database Changes , of which was already approved by @suthagar23.

I think in general the UI is fine, but the UX could be further improved through a declunking and addition of a search feature, as I have explained in the PDF. I would love to have a conversation in the proposed edits, and would be more than willing to actually try to make the component hahha :smiley:


(Aleksander W) #4

Hi! I’ve described some ideas for improvement of Global Properties manager in this document :smiley: My task was approved by @suthagar23

I’m aware that this component isn’t used very often/by a large group of people but I’d like to implement my ideas someday. This page really needs some upgrades, which might not matter at the moment but in the future could be really helpful. I’m not questioning the looks but rather the functionality.

Unfortunately I have no knowledge about any of the front-end JS frameworks used today (afaik OpenMRS RefApp mainly uses Angular), but it won’t stop me from learning it or simply trying to use vanilla JS, maybe with the help of jQuery. :slight_smile: BTW, trying to replicate my ideas using simple graphics software was probably the funniest part of doing this task :grin:


(Hrishikesh Patil) #5

Got my task approved by @f4ww4z

My idea is to update the links in a few pages under the System Administration module, which I’ve also documented in my report. This is the related JIRA issue

Will work on another task meanwhile, and come back to work on this as a GCI task


(Satvik Shrivastava) #6

Hello Everyone! I have prepared a report on UI issues of OpenMRS Ref Application and have also suggested measure to improve it. My submission was approved by @f4ww4z

You can check it here: UI issues Report

The 3 components I focused on are:

1) Registration of patient: I proposed a ‘next button’ to proceed further in form filling.

2) Appointment Request: I proposed a simple Time Zone conversion tool.

3) Finding Patient Record: I proposed a listing of complete patient data along with it’s systematic arrangement.

I have explained all these proposals in the PDF.

Thank you! :slight_smile:


(Svitlana Honcharuk) #7

Hi everyone! My task was approved by @pkatopenmrs

I’ve focused on fixing UI issues on Vitals page. I didn’t want to redesign it completely, because I understand my ideas should be realistic and implementable. There are a lot of small things which are not so hard to fix, but at the same time I believe working on them will lead to a better user experience.

Take a look at my submission on this PDF.

Some fixes there are relevant not only for Vitals page, but for some other ones.

UPD: just saw that Satvik and I have familiar ideas about “Next” button but on different pages. Feels like it’s really needed :slight_smile:


(Satvik Shrivastava) #8

Yes, I liked the idea of the ‘back button’ too. To be honest, I thought of this implementation along with my ‘next button’ implementation :smiley: These are the small things which go unnoticed but do have great significane in the user experience :slight_smile:


(Aditya Bisht) #9

Hey there everyone! I’d suggested improvements in UI design in the Data Management page. I have added things which I believe will improve user experience.

My task had been approved by @pkatopenmrs and here is my PDF file.

Things I changed :-

  • Using same text field for ID & name.
  • Reduced the information displayed while merging.
  • Removed shifting of buttons.

For details information, kindly refer to the PDF linked above. Thank You! :smiley:


(Aleksander W) #10

Hi everyone. Speaking of tabs @lana @satvikshri which are a part of Register Patient and Vitals wizards, I find them being overly-complicated for this design. While tabs do make sense when every page includes a lot of fields, buttons and so on (which fall under one category), in most cases these pages contain just one field and a simple explanation. Wouldn’t it be easier to just put them on a single page, separated with horizontal lines? It’s definitely easier to use mousewheel rather than switch between the tabs (this also makes it not possibile to see all of the data we’ve entered at one time and it forces the user to switch between the pages in a specific order (Patient Registration does that)). I’ve mentioned this problem when doing other task here.

I mean, OpenMRS web client is specifically designed for Personal Computers (for mobile use there’s Android and iOS client) so it’s better to use available free space on the display.


(Svitlana Honcharuk) #11

Yeah, it definitely makes even more sense than just having next/back buttons. Nice idea!


(Satvik Shrivastava) #12

Hey @anuar2k , I really liked the idea of merging the whole form in a single page separated by horizontal lines or just spaces. I think you should create a new talk topic for the same to take opinions of other community members too. I will prepare a basic preview of the proposal UI for demonstration purpose. :slight_smile:


(Qasim Khan) #13

Hello, my task was approved by @ykarim250. I suggested improvements for a couple of components, mainly System Administration, Reports, and Metadata. For SysAdmin, I proposed a new way for the “update module” loading process. The reports page was empty so I added a message for the user. One of the tables in the metadata component was poorly formatted, so I recommended a fix for that table. My proposal can be found here


(Aryan Malhotra) #14

Hello everyone my task was approved by @suthagar23 and @f4ww4z

I suggested the following improvements:-
  • Be friendly and helpful: Make webpage more users’ friendly by adding OpenMRS bot at the bottom right corner .OpenMRS bot is a useful contribution to the community. Why don’t we use it wherever possible?

  • Eye-catching Font: Use eye catching font for main headings. Before reading only font attracts the user interest. 

  • Make it memorable: Make it look attractive by using different themes. 

  • FAQ: A FAQ is good to help users clear their doubts/query.

  • User Guide: A simple user guide at the starting must be helpful for the new users and I guess it is the most important feature to develop more users.

  • Feedback: One of the most basic guidelines for improving usability is to provide an optional feedback. Feedbacks are great even regular users can post any bug/ issue they find in the Reference Application. 

  • Use Negative Space: Use negative space because there so much of white space left below. Using so much whitespace doesn’t show an attractive look. Using negative space hides the much of the whitespace which is indeed beneficial for the Reference Application.

  • Use Grid for layout: Since the website is mostly white using a grid for layout must be the best solution. Use green or black color so it can matches with colors already used in the website.

  • Hold up a sign: OpenMRS bot must be useful holding an optional link to the feedback form. 

  • Outbound links: Hyperlinked photos to be used. 

  • Be responsive & mobile-friendly: Mobile might not be in use this much but it has more scope in the future. Generally, mobile.website.com is used to create mobile friendly websites.