GSoC 2020 : OpenMRS Android Client 2.9.x Project

Owned by Shivang Nagaria
Last updated: Aug 28, 2020 by Fawwaz YusranVersion comment
3 min read

 

Primary mentor

@Fawwaz Yusran

Backup mentors

@CLIFF GITA @Vibhor Chinda

Assigned to

@Rishabh Agarwal 


Abstract

The goal of the Android client is to provide an alternative to access a hospital's OpenMRS instance by just using the provider's Android devices. See the full Android client guide for more info.

Considering the services offered by a hospital, an Android application can help doctors, patients, and other staff a lot with its mobility and ease of use, without them having to start the OpenMRS web app on a desktop computer. This will improve the productivity and efficiency of the hospital workflow.

This year, we will focus on two aspects to improve the Android client - performance and UI/UX.

There are still frequent crashes when using the app, especially if a doctor is using it for a long time with no pause. On crashes, the app will just return the user to the dashboard page, and any unsaved transactions will be lost. Also, the offline-first solution needs to be developed, where a provider cannot connect to the internet and needs to work offline temporarily. Data should be synced again when back online.

Next, the current user interface is slow to respond to user inputs and does not look pleasing to the eye, compared to the newer and modern Android apps in the google play store. E.g. 'Undo' buttons (that takes the user back to the previous state if he/she errors) should be available for any operation. So we should enhance the feel of the app so that the user knows that he/she is in control every time.

Finally, seeing the number of components in the web app, the Android app should integrate more of them so that doctors and staff can expect to see the same functionalities in the web app implemented in the client.

An additional request is to migrate the Java source code to Android's now recommended Kotlin, to increase readability and reduce a thousand lines of code present in the GitHub repository.

Objectives

  1. Material UI design (Figma Link)

  2. Integrate more components of the web app to the client (to be discussed further)

  3. Password reset via email

  4. Replace Java code with Kotlin

  5. Replace native SQL to Room

Future Works that need to be done

  1. Migrate the remaining 80% codebase to kotlin.

  2. Start converting MVP pattern to MVVM as it follows the new standard guideline brought by Google.

  3. Re-design Home screen with a better UI.

  4. Add the password-reset feature.

  5. Create a diagnosis using REST.

  6. Implement the Appointment Scheduling Module.

  7. Mark Patient deceased using a non-coded response.

Sample Use Cases

  1. A doctor does not have access to a PC, but his Android phone is available to use during office hours.

  2. No internet connectivity and a doctor needs to work offline temporarily.

Project Champions

Same people who use the web app: Providers (e.g. doctors, nurses, clinicians)

Skills Needed

Android, Java, Room, Kotlin

Progress

Issues that are completed and their status:

Timeline

Week 1

Blog post

Tasks completed:

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Week 2

Blog post

Tasks completed:

Week 3

Blog post

Tasks completed:

Week 4

Blog post

Tasks completed:

Week 5

Blog post

Tasks completed:

Week 6

Blog post

Tasks completed:

Week 7

Blog post

Tasks completed:

Week 8

Blog post

Completed database migration (from ActiveAndroid to Room) at

Week 9

Blog post

Tasks completed:

Week 10

Blog post

Tasks completed:

Week 11

Blog post

Tasks completed:

Week 12

Blog post

Tasks completed:

Dev Tracks

Resources