As the first step of the GSoC project – Merge Patient Enhancement, Since “community bonding period”, I had around five discussions how to implement this project with Simon Savai and Ada Yeung. At the begin of the bonding period, Simon and Ada were tried to give an understanding of the implementation. How it uses the current module, how it’s working, what’s the purpose of the project implementation.
After having three meeting with my mentors, I started designing my UI mockups as matching project requirements. As my understanding, I have developed UI mockups first phase. However, After getting valuable feedback from the mentors, We decided those UI should have a redesign for matching easier way.
In the GSoC project implementation, there are major three components,
- Merge Patient Registration Data
- Create New Patient Registration Data
- Enhance Error resolution UI to make it easy for resolving other types of errors encountered during processing of data coming from mobile devices.
Merge Patient Registration Data Mock-ups
In the merge, patient registration data UI give those functionalities for the user,
- Use The user can select “Short View” or “Extend View”, If the user selects “Short View”, the user can only see conflicted data attributes and new attributes with red and orange colors. “Extend View”, the user can see all attributes of the Patient Registration data from EMR DB and Patient Registration data from mUzima mobile side by side.
- The user can start edit by click on the locked padlock. If padlock unlock user can start change attributes of the registrations.
- The user has two ways to edit Patient Registrations. 1) The user can edit Patient Registration by type on the text area of each attribute, or 2) User can select attributes by click on the checkbox. As an additional feature, the user can merge all conflicting data into one registration from another registration by click on the relevant “Select All” checkbox.
- From the different colored UI, User can clear understand edited, conflicted, conflicted after edited, identically same after the edit.
- Merging Alerts avoid user mistakes clicks.
Create New Patient Registration Data Mock-ups
- The user can start edit by click on the locked padlock (If padlock unlocked user can start change attributes of the New Registration)
- From the different green color indicates edited attributes of the Patient Registration.
- The user can continue New Patient Registration with newly edited attributes or old patient registration data which came from the mobile application.
- Alerts avoid user mistakes clicks and give an understanding of the changes on registrations.
With the aim of provides more idea about UI, I have created a demo video for the UI mock-ups.
mUzima – Patient Merge Enhancment Mock-up Demo
TODO List:
- How to incorporate the new UI.
- Understand current uzima core module.
- Divide workload into subtask and create Tickets.
milankarunarathne 