Vivy is an 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 prioritise 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

Vivy allows customers to digitally request their documents (lab. results, findings, x-rays etc.) from doctors, medical labs 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 management

Initially, the probability of a doctor fulfilling a request was minimal, given that Vivy was a novel and unfamiliar service, resulting in dissatisfied customers. To alleviate frustration, it became essential to enhance communication and transparency in the request service. This involved updating customers on the status of their requests, educating them about the process, and presenting potential solutions.

File sharing

After importing files to the user's smartphone, there was a seamless ability to share these files with other medical practitioners. Access could be regulated within the application, giving patients enhanced control over their data.

Practitioners interface

The practitioners Interface facilitated a secure, convenient, and direct connection between healthcare practitioners and their patients, the digital sharing of medical files is achieved in a safe and transparent format, thereby reducing transportation time and costs.

Findings

Creating a robust medical file sharing network posed more challenges than initially expected. Several factors contributed to this difficulty. As a private company, Vivy encountered trust issues, especially among healthcare professionals who were hesitant to adopt the services, rendering the document exchange process costly and time-consuming. To address this, we relied on end-to-end encryption security, emphasising that only the designated recipient could access the data. While this approach proved beneficial, in retrospect, for a project of similar scope, I would contend that it might be more effectively developed at a state or national level.

Invoice management

A key feature of the application was the ability to send invoices to your healthcare provider. Patients with private insurance in Germany must frequently go through this procedure, which can be challenging at times. We wanted as much direct input from key stakeholders as possible when developing this feature, so I travelled to Munich and worked with Allianz, our parent company, running a four-day design sprint to outline necessary functionality and requirements.