The Patient Portal

INTRODUCTION

Whilst creating PACO: The Patient and Care Optimiser, I had created 4 main modules. These were:

  1. Analytics – The module to give practices data to make meaningful change, see capacity and demand, and analyse patients and medication use in their practices.
  2. Comms Hub – The key to connecting patients and their practices. This module allows practices to send preselected lists from the analytics module to Comms Hub, and communicate with these patient cohorts via sms and/or email with only a single click.
  3. Patient Facing Scheduler – The first patient facing module in the PACO family, this application allows the user to book appointments sent to them by clinicians (via Comms Hub) to free up practice phone lines, reduce DNAs and reduce the average time for booking a patient into appointments.
  4. Virtual Consult – this module is the final goal along the user journey with PACO. The Virtual consult module uses web chat and video consultations to increase access to patients and allow those hard to reach cohorts the chance to keep up with clinical appointments without leaving their home.

With all of this, I couldn’t help but think we needed some form of platform where all this information and data can be handled from the patient side rather than relying on data and information fed through from clinical systems, such as EMIS.

ROLE

Lead UX/UI Designer

Solo designer on this project, taking the design from initial screen sketches after stakeholder meetings and requirement gathering, to the final prototype.

Connectivity and integration

As mentioned earlier, I’d already worked on 4 modules on a clinician facing web application (PACO). Part of the analytics module, includes the Patient and Medications Analyser. Within this, I designed a patient timeline, which allows Practice staff to see all observations for a patient throughout their life. But what we need is the ability for the patient to upload and input into this timeline to better help the clinician gain an understanding of their patients.

Initial wireframes

After working with the CEO and product lead on this, we were able to define some key criteria for the application. Patient input being the forefront of the acceptance criteria meant this would heavily influence my design. My initial thoughts led me to create a home dashboard with some very easy to use tiles allowing a patient to ‘add a new post’, or add a quick post such as checking into a dentist appointment or other clinical appointment that they wished to add to their timeline.

Low Fidelity Wireframes

Working from my initial sketches I created a lo-fi run through of the application. However, looking at the Home Screen once in a digital wireframe, I found that the ui wasn’t very clean. It didn’t have that cutting edge design I would have liked to have created in an application.

The symptom tracker looked too busy for a Home Screen, the top buttons didn’t look as refined as I’d have hoped and the recent evens taken straight from the Patient Timeline didn’t suit the mobile application.