Patient Drug Safety
Monitoring App

Biogen · 2015–2017

Replacing a paper and fax-based compliance process with a purpose-built digital portal — setting a new standard for online REMS enrollment and patient management in a highly regulated healthcare environment.

ZINBRYTA REMS Program Portal — HCP Dashboard · Biogen

Project Snapshot

The Problem
Healthcare providers enrolling patients in the Zinbryta REMS program were drowning in paper — faxed forms, manual lab tracking, and handwritten signatures. The process was error-prone, time-consuming, and pulled doctors and nurses away from patient care.
My Goal
Design a digital REMS portal from scratch to replace the fax-and-paper process — leading cross-functional discussions with legal, compliance, regulatory, brand, and engineering using rapid prototyping and a user-centered approach.
The Team & Mandate
A cross-functional stakeholder group across Legal, Compliance, Regulatory, Brand, Marketing, and Engineering — nine stakeholders in total. I led all UX and facilitated alignment across disciplines with no prior shared process.
  • Replace fax/paper enrollment with an immediate online certification and patient enrollment flow
  • Enable doctors to delegate administrative tasks to nurses including patient management and form completion
  • Support DocuSign batch signing without disrupting doctors' preferred workflow
  • Build admin tools for patient status management and lab result tracking
  • Navigate and align nine stakeholders across technical and non-technical disciplines
Outcomes

Delivered a fully functional REMS portal with DocuSign integration, doctor-to-nurse delegation, and immediate HCP certification. Positive testing results shifted the organisation toward prioritising user needs in future healthcare digital products.

Nurses immediately comfortable navigating the prototype
Task-based dashboard and enrollment flow validated
DocuSign batch signing preserved doctors' preferred workflow
Eliminated the main source of doctor resistance
Testing results shifted org toward user-centred design for future products
Set a new internal standard for REMS portal design
Killer Feature

DocuSign Batch Signing — Doctors needed to sign multiple patient forms without losing their existing batch workflow. We designed a DocuSign integration that preserved that pattern — removing the biggest source of anticipated resistance.

Design Process
Stakeholder Sessions
Personas
Sketches
Lo-fi Prototype
User Testing
Med-fi Wireframes
Visual Design
My Role
Lead UX Designer
Company
Biogen
Timeline
2016–2017
Platform
Enterprise Web App / DocuSign
Team
Solo UX + Cross-functional Stakeholders

Research & Insights

The stakeholder environment was the most complex I had worked in. On the non-technical side: a Product Manager, Therapy Owner, Compliance, Regulatory, Legal, Brand, and Marketing. On the technical side: Enterprise Architecture, a Development team, a Design Agency, and a Business Analyst. My role as UX Strategist was to lead cross-functional discussions using a user-centered design process — with all stakeholders present simultaneously.

We designed for three audiences: prescribers who needed to certify and sign, nurses who managed the day-to-day compliance and enrollment work on their behalf, and patients whose safety monitoring was the whole point of the program.

"At the end of the day the nurse brings a pile of paper forms I must sign all at once. I like this process, it is easy, I don't want to lose that."

— Doctor, during user testing

This quote defined the design challenge perfectly — we weren't just digitising a process. We were redesigning it in a way that preserved the doctor's familiar batch-signing workflow while giving nurses the tools to manage everything else independently.

Sketches & Screen Flows

Sketches

I started with rough sketches — filling 5 to 6 notebooks throughout the project with notes, questions, design decisions, and UI concepts. Sketching quickly in every stakeholder session meant ideas were captured in real time rather than reconstructed later.

Screen Flows

Wireflows mapped the key use cases — new patient enrollment, new prescriber certification, and the migration path for prescribers who previously enrolled by fax or phone. These were essential for stakeholders to understand the full scope of the system.

Wireframes & Prototype

Wireframes

Once the team aligned on basic requirements and information architecture through the lo-fi prototype sessions, I moved to medium-fidelity. These wireframes served double duty: as a higher-fidelity prototype for nurse user testing, and as a handoff specification for the visual design agency.

Prototype

The prototype approach was central to the process. Rather than traditional wireframes reviewed in isolation, I brought a working lo-fi prototype to every sprint. Stakeholders reacted to real interactions, not static screens — and Legal and Compliance could flag issues before they became coded features.