< All work
prelude
Electronic data capture software for clinical trials · Work under NDA

Rebuilding an enterprise clinical research platform
from the foundation up.

My role
Sole designer, end to end
The team
1 VP of Product
2 Product Managers
4 Engineers
75%
Reduction in study setup time
50%
Less time spent collecting data
Overview

Prelude is an enterprise platform for animal clinical research that folds electronic data capture (EDC) and self-reported outcomes (ePRO) into a single connected system, carrying a study from first setup all the way through data, monitoring, inventory, and compliance.

Problem

Prelude needed to evolve. New features had to be added and existing ones redesigned, but every change became harder than it should have been because the platform had stopped being able to scale. Over time almost everything had been pushed into forms, so every new change meant slow setup, custom code, and nowhere clean to put anything new.

Objectives
Scalable foundation
Break the platform out of forms so settings, permissions, reporting, and configuration each have a dedicated place, and anything new has somewhere to live. A structure built to scale.
Effortless configuration
Make building a study effortless. Features that once needed custom code become configurable in a few clicks, so the platform is faster, easier, and more intuitive to use.
Role-based experience
Govern access and interface through a single matrix of roles and permissions, so each person sees exactly what their role allows, with a tailored experience of the platform.

Moving from a redesign to a foundation rebuild…

01
Everything lived in forms
Settings, permissions, reporting, and configuration had all been pushed into forms, making the platform outdated, unable to scale, and limited in what it could do.
Give each feature its own home
Configuration moved out of forms, so each function has a dedicated place and forms go back to collecting subject data.
02
Features needed custom code
Calculations and fields specific to animal studies needed custom code, because the platform had originally been built for human trials. That slowed study setup.
Make configuration effortless
Now every feature is a few clicks away, study setup is faster and easier, and it no longer relies on code.
03
Scalability needs control
With new features and a new foundation, roles, permissions, and access needed to evolve accordingly.
Govern it with one matrix
A single set of roles and permissions drives both access and experience, so each person sees exactly what their role allows.

…with solid core principles.

Role-based access control
Permissions by role
AdminPICRCCRADMSponsor
Protocol Builder✓RRRR
Data Entry✓✓✓
Form ReviewRR✓✓
Form FinalizationR✓R
Reports & Exports✓R✓✓R
✓Full
RRead
None
Example of matrix based on roles and permissions

The platform could finally evolve.

What started as a contained project became a broader product shift. It took longer and reached beyond the original scope, but it ultimately reset the roadmap and became the foundation for what followed. The same foundation went on to carry more than 12 features, including ePRO, eConsent, integrated IDEXX and VeDDRA / ATCvet coding, and RTSM.

1
Scalable foundation
12+
Added features
75%
Reduction in study setup time
EDC
ePRO
RTSMIDEXX
eConsent
VeDDRA
< All work
let's talk