About
Vivy is a electronic health record, using end-to-end encryption which allows customers to securely store and share medical documents
Summary
As one of the initial designers, I supported by helping to establish the foundation of Vivy, shaping the product vision and pushing to prioritize research and the customer experience.
Position
Product Designer
Responsibilities
User interviews, diary studies, card sorting, storyboarding, wireframing, Interface design, Usability studies
Case Study:
Document request & sharing
November 2018
Vivy allows customers to digitally request their documents (lab. results, finding, x-rays etc.) from doctors, medical lab or hospitals and manage them on using a smartphone, regardless of opening hours or consultation times. Once files are on the smartphone they can be shared with safety and ease, for a more beneficial treatment.
Expectation managment
In the beginning the likelihood of doctor fulfilling request was low as Vivy was a new unknown service which in turn lead to frustrated customers. To prevent frustration we need to manage expectations by improving the communication and transparency of the request service. This was done by communicating the status of the request and educating customer about the request process as well offering possible fixes.
File sharing
In principle once files had been imported to the users smartphone these files could be easily re-shared with other medical pratications. Access could be managed within the application giving patients greater control.
Practitioners interface
Enabling a safe, easy and close bridge between healthcare practitioners and their patients. Medical files can be digitally shared in a secure and transparent format saving on tansport time and costs.
View prototype
Findings
Developing a comprehensive medical file sharing network proved harder than originally anticipated. this was due to a number of factors. Firstly Vivy as a private company struggled to build trust, particularly for healthcare professionals few chose to embrace the services making the document exchange service costly and time consuming. To help combat this we fell back on the end-to-end encryption security, explaining how only the intended recipient can view the data. This helped but in hindsight for a project similar this too really developed I would argue that it would need to be developed at a state or national level.
Case Study:
Invoice management
July 2018
Coming soon...
