Niva
Niva is an innovative vision of Centralised Data-Driven integrated platform for Mobiles to manage all the health records with security layers. Easy to download, share and customise for quick sharing.
FIGmd is a leader in providing healthcare solutions & rapid deployment of secure, interoperability driven, clinical, claims, quality data acquisition platforms & EHR in the USA, because providers have different systems in place for storing Electronic Health Records (EHR) and there isn't a standard process to share patient information.
Our task was to design a mobile application for patients to share their medical history with another provider seamlessly with anyone.
To Build a multi device supported, integrated platform to capture & share health records with doctors. Create a Scalable, android & iOS native assistance application for healthcare market. Creating a common EHR platform which can be integrated with other FIGmd products. Which will eventually add more value to the data.
We initiated and conducted design sprint to add UI UX efforts in very beginning of the product development cycle for maximum control and excellent experience
We started research work with the stakeholders (Business Analyst, Marketing Head etc.) to get market insight and understand the users, early research showed that our primary user group would be patients with recurring medical issues and secondary doctors. After the research we created 2 primary personas of our target group.
We interviewed 15 patients and 5 providers with the help of our USA office team we interacted with the target group audience to understand WHAT WHY & HOW and asked them questions like:
Dr. John is a 32 years emergency doctor who lives in New York. He thinks time is very important factor in saving life, he prefers away to share medical reports with an casy access
In dealing with emergency cases too he has to contact another medical provider to have the access to the patient's history.
There should be an easy way to be updated and connected without annoying or over loading doctors all the time.
Dr John is very friendly with the mobile and tablet
Bella is a 28 year old housewife who lives in New York. She has been suffering from diabetes for about 15 years, she is worried about her medical status and she has to frequently visit doctors.
Bella's regular doctor has left the job from USL hospital, and now he is associated with LBS hospital, he doesn't want to change the doctor, but both the hospitals don't have any tie up to share EHR.
Easy access to medical data and files to share with the same doctor in new hospital.
Getting medical history from the hospital is a very difficult process. She needs to contact the hospital and needs to do many formalities.
Bella is not much tech-savvy but she used IPhone
Next, we made a user journey for my patient persona to determine and prioritize the most critical user flows, this process helped us to visualize the process of the patient which he goes through in order to accomplish a goal.
She visits to Dr. Robert at ABC hospital every month, but few days back she got to know Dr. Robert have left job from ABC hospital and now he is associated with XYZ hospital, as Bella is getting treatment from Dr. Robert for long time, so she don't want to change the doctor and decide to visit Dr. Robert at XYZ Hospital.
But ABC Hospital & XYZ hospital both don't have any tie-up to share EHR, so Bolla needs to access her medical history from ABC hospital
| Phase | Awareness | Search | Documentation | Collect | Share |
|---|---|---|---|---|---|
| Action | Bellas makes a call to Dr. robert to book his appointment, but Doctor informs her that he is not associated with ABC hospital, If she needs to visit him, she has to come to XYZ hospital with her medical history | Bella calls the ABC hospital to know how she can access her medical history and share it with xyz hospital. Ther hospital informs her she need to sing and submit few documents at the hospital to access her medical history | Bella visits the ABC hospital, fills up the form with details of required medical history, signs a medical authorization release form and pay the medical history fees | After few day bella again visits the ABC hospital to collect her medical history bunch of paper document | Bella visits Dr. robert at XYZ hospital and share her medical history paper documents |
| Feelings | Worried | Tense | Irritated and Frustrated | Feel Relaxed | Happy |
After this user journey, we determined which all user behaviors and actions are of prime significance to them. We considered the technical feasibility of this prioritization process. This was done in collaboration with the Product Managers Technical Leads, and the Strategist of Niva. Going deeper into these actions, we created a list of major requirements of the user and product features
| Priority | Feature | Details |
|---|---|---|
| Must Have | Vital | Users will be able to see their details as per monitored by medical professional and health care provider |
| Medications | Users can see which medicine currently he/she is taking which medicines he/she has stopped | |
| Allergies | Users will be able to see quick view of their allergy history | |
| Health records | Users will be able to see their entire EHR as per their hospital visits also they will be able to share the same with other providers | |
| Care team | Users will be able to manage their hospitals and providers like link and unlink the hospitals and providers | |
| Lab Reports | Users will be able to find their all lab and diagnostic reports history | |
| Surveys | Any survey or questionnaire rolled out by the hospital or provider will be in the survey | |
| Profile | Users will be able to manage details like mobile number, email address, passwords , medical id etc | |
| Settings | User will be Able to manage and set preferences notification security settings etc | |
| Nice to Have | Appointments | Users will be able to make appointments with doctors |
| Fitness | This feature will help users to keep healthy with regular health tips, adviceses, blogs etc ... |
Information Architecture (IA)
The information architecture (IA) is not part of the on-screen user interface (UI) — rather, IA informs UI.
After iterating multiple rounds of IA in UX workshop with the team we finalized detailed Information architecture, we came up with a model which worked the best for chronic patients. we categorized the items into sections of vital, medications, allergies, and health records and lab reports chronologically. A medical history organized in catagory by chronology does help a patient to find their history easily.
Looking at the waste data captured & analysed for Pegasus, we chose open card sorting to define Information Architecture which led us to strong navigational structure catering to the capabilities of each bucket
This Navigation helped users find information, related functionality and encourage them to take desirable actions. Also, separated components include global navigation, local navigation, utility navigation, breadcrumbs, filters, facets, related links, footers, fat footers, and so on.
Based on the key findings and generated information architecture, We came up with the following key app prototypes. It helped me arrange the interface elements easily and alongside we focused more on the functionality of the app. Moreover, the wireframes allow me to quickly test ideas without diving into the visual details.
Based on the key findings and generated information architecture, We came up with the following key app prototypes. It helped me arrange the interface elements easily and alongside we focused more on the functionality of the app. Moreover, the wireframes allow me to quickly test ideas without diving into the visual details.
Font : Roboto
Category : San serif
Classification : Neo-grotesque
almost before we knew it, we had left the ground.
ALMOST BEFORE WE KNEW IT, WE HAD LEFTTHE GROUND.
0123456789~!@#$%^&*()_+=-`[]\\\\\\\\\\\\\\\\;’,./{}:”?
We then used the paper sketches to create mock-ups of different screens in Adobe XD. Below you can see visual design of the key screens we designed in order to improve usability of the app according to the major pain points. We followed the existing branding and design of the NIVA Web app and tried using fresh and more approachable colour for Niva Mobile app, also tried to keep solutions as simple and effective as possible to align with the business goals.
After creating wireframes and choosing a style, we did internal usability testing between team, And stared for high fidelity design. We made a prototype of the project and asked respondents to do tasks in order to test it with them. We picked realistic scenarios to engage the respondents in reaching their goals with the app. Using all the information we had, we designed tasks for users to complete.
Documented and restructured the language for user’s understanding. And conducted tests with different users, internal and externals!
We used different tools to analyse the user experience and the problems users came across (with the help of tools such as morae). It helped extensively to capture heat maps and user’s behaviour and patters.
Feedback -
1. Securely sharing of sensitive data (SAMSHA) as per FHIR and HIPAA guidelines on Niva perform
2. Patient can send data to any doctor without hesitation at any point of time.
