General Overview
REDCap Cloud offers data capture solutions for clients such as: Clinical Research Orgs (CROs), big pharma companies, and biotech firms. Over the past two years, I have been collaborating with my team and clients in the development and launch of our V2 release. This initiative has been an exciting challenge, resulting in the creation of a robust platform. Our V2 release has the potential to streamline operations for certain CROs by consolidating their vendor count, potentially reducing their need from twelve or more suppliers to just one.
Below are a few examples of designs I have shipped at RCC:
Mobile App - Custom Domain Solution
Patient Portal Improvements
Permissions Module Redesign
Mobile App - Custom Domain Solution
Background
The basic schema of RCC is a database that has separate environments that house multiple instances. Some customers are bound by their local regulations to have private servers which necessitate custom domains.
Challenge
On web, a user with a custom domain simply opens their organizations unique URL. On a mobile application this needs to be configured manually.
Solution
I start with flowcharts so I clearly see all flows at a glance. These flow charts also give dev teams much quicker understanding of objectives compared to long winded Jira tickets.
Then I build out rough mockups (most often in PowerPoint) which then are turned into Figma prototypes. Once I get the green light, I write up everything in detail for my dev team.
Patient Portal Improvements
Background
Conducting clinical research is often supported my electronic patient reported outcomes (ePROs). This can be a daily mental health assessment or in the moment symptom trackers.
Challenge
Patients using the patient portal cannot see what surveys they have completed, missed, or are needing attention.
Solution
Add Status & Completion Columns: to give patients better understanding of where they are in the trial.
Add Due Date Column: to give patients a quick glance at when their pending surveys should be completed.
Statuses are Color Coded: and clear for patients to know which survey should be taken next.
Add Filter Buttons: to quickly clear up table for patient if they are in a multi-year trial with hundreds of surveys.
Permissions Module Redesign
Background
When many new features are developed rapidly for a database, there often may be a need for many permission settings to enable said new features. This presented as a UX challenge that was noted by our end users.
Challenge
The current permissions module is overwhelming, time consuming, and leads to confusion unless user documentation is pulled up side-by-side.
Pros:
Single click simplicity to enable/disable permission(s)
Easy to change Role name and/or Scope
First column/row remain frozen during scrolling
Cons:
Large amounts of horizontal scrolling
User only sees broad description of permission via hover text
To enable multiple permissions within UI requires many clicks
Letters are frequently re-used for separate functionalities.
Solution:
I use a six pronged approach that allows administrators to understand permissions at a glance and configure them more efficiently.
Transforming Axes: allows for the ability to collapse permission sets and give permission sets a header for broad info.
2. Sectioning: of permission sets are split into sections which allows for headers.
3. Written Description: of each permission set in the section header that comes from our user documentation.
4. Fill All: button which allows for administrators to quickly add whole sets of permissions more rapidly.
5. Name of Each Permission: is written out with corresponding letter in parentheses (Read (R), Update (U), etc).
6. Collapsibility: of each permission set via a familiar collapse button.
