Sreejith N Portfolio

Back

Live Product

2024–2025 · 2026 enhancement

Medora : Connecting people, projects and clinical workflows in one platform

Designing a clinical-trial operations platform that connects project teams, sites, clinicians and patients across the entire visit lifecycle.

Role

Product / UX Designer, UX Research, UI Designing, Prototyping & Testing

Platforms

Web Application · Responsive mobile for Clinicians

Timeline

4 Weeks of Explorations - 2024–2025 · 2026 enhancement

This project is under NDA.

Specific workflows, client details, and final screens are not disclosed. What's shown here covers the problem space, process, and high-level outcomes - enough to understand the design thinking. Happy to walk through the full project in conversation.

1.Overview

One platform. Multiple roles. One connected workflow.

Medora is a clinical-trial operations platform built to coordinate projects, sites, clinicians and patient visits across distributed teams. The platform brings together everything from project setup and team assignment to visit execution, source-document submission, review and completion.

Focus

Discovery → Delivery

Users

Admins · Project teams · Site teams · Clinicians · Monitors

System

Rules, payments, safety

Outcome

Three connected products

2.Context

Clinical trials are a chain of coordinated actions

A single patient visit can involve multiple people:

Site

Project Team

Clinicians

Patient

Investigator

Project Team

Every handoff needs the right person, permission, information and documentation.

Medora was designed to bring these moving parts into one controlled workflow, instead of relying on disconnected communication and manual coordination.

Every handoff needs the right person, permission, information and documentation.

Medora was designed to bring these moving parts into one controlled workflow, instead of relying on disconnected communication and manual coordination.

3.The Problem

The complexity wasn't in one workflow. It was in how everything connected.

Medora needed to support :

The challenge was to make this complexity manageable without making the product feel complex.

Multiple user roles

Multiple projects

Multiple sites

Audit history

Different clinician types

Different visit types

Role-based permissions

Source-document workflows

Review and approval

Design question?

How might we connect the entire clinical-trial workflow while giving every user only the information and actions relevant to their role?

4.My Role

I worked across the product, from discovery to delivery.

Understand

UX analysis · Research inputs · Clinical workflows · Competitive analysis

Define

User roles · IA · Journeys · Visit flows · Privilege matrix

Ideate & Solve

Project workflows · Visit types · Source documents · Forms · Vendor management

Design

Wireframes · UI · Design system · Responsive experiences · Prototypes

Deliver

Admin Web · Project Web · Site Web · Clinician Mobile · Monitor View

5.User personas

6.Understanding the Users

One ecosystem. Six user groups.

HomeNurse4U Admins

Create and manage the platform's master data, projects, users and permissions.

Need: Control and visibility.

Project Managers & Coordinators

Manage project execution, assign teams and coordinate visits.

Need: Coordination and operational oversight.

Site Users

Hospital-side users including Site Coordinators, Principal Investigators, Sub-Investigators and Site Personnel.

Need: Manage visits, patients and clinical activities.

Clinicians ( MRC & PPC )

Clinicians who perform home visits or support patient-pledge journeys.

Need: Simple, task-focused mobile workflows.

Monitors

View-only users who monitor project activity and progress.

Need: Visibility without modification access.

7.The Product Model

Master data first. Project assignment second.

One of the key structural decisions in Medora was separating what exists in the platform from what belongs to a specific project.

Master lists

Sites · Clinicians · Project users · Countries · Vendors

Trust needs to be visible.

These entities are created and maintained centrally.

Users shouldn't have to search for reasons to trust a therapist or the platform.

Project setup

When a new project is created, existing master entities are assigned to the project rather than recreated.

A mental-health product should reduce emotional and cognitive friction, not add to it.

Create Project

Add Project Details

Assign Team

Assign Clinicians

Assign Sites

Assign Clinicians

Configure Milestones & Tasks

This reduced duplication and created a more scalable foundation for managing multiple clinical trials.

8.The Core Workflow

A controlled workflow connecting sites, project teams, clinicians and investigators.

The visit lifecycle is where the different roles come together.

Visit flow :

Create visit

Assign clinician

Accept & confirm

Perform visit

Submit documents

PI review

Complete

Visit types :

Home Visit

Home Visit

Clinician visits the patient

performs tasks

submits source documents

PI reviews.

Visit types :

Patient Pledge

Patient Pledge

Clinician takes patient to hospital

PI performs tests

results uploaded

expenses reviewed

reimbursement.

Source documents :

Project tasks

Visit tasks

Clinician completes

Documents submitted

PI review

Privilege & audit trials

Role-based access

View / Create / Edit / Assign / Approve

Every action logged: Who · What · When

One workflow framework, different roles, controlled access, and complete traceability.

9.Userflows

Then I started asking: "what happens next?"

The flows helped me understand not only what screens were required, but also what needed to happen between those screens.

10.Wireframes

I solved the experience before solving the visuals.

What matters first, what can wait, where actions belong, how information should be grouped, how different states should behave. The goal was clarity, not polish.

11.Brand & design system

Consistency across a complex product

A reusable design system helped maintain consistency across the many modules and user roles.

12.Final UI

13.The Product Evolves (2026)

One year after launch, Medora came back with a new challenge.

The first version successfully established the operational foundation. In 2026, a new requirement emerged:

How can administrators manage forms and vendors without creating more manual work?

Create once → manage centrally → assign where needed.

14.Form Management

Moving from project-specific forms to reusable templates

Previously, project tasks were configured during project setup. The new requirement introduced a reusable Form Management layer.

Create Form Template

Save to Master List

Assign to Projects

View Project Tasks

Select required tasks

Use during visits

Separate form creation from project execution.

Administrators can build reusable templates once and apply them across projects.

15.Vendor Management

Bringing external partners into the same operational system

Vendor Management extends the master-data model to external organizations.

Create vendor

Assign users

Assign to Projects

This keeps vendor relationships structured while fitting naturally into the existing project-assignment model.

16.What Changed

From a workflow platform to a scalable operations system

AFTER

Master data

Reusable forms & vendors

Project assignment

Controlled execution

Review & approval

Audit trail

BEFORE

Projects

Manual task configuration

Repeated setup

Project-specific management

17.Impact

Making a complex operation easier to control

Medora created a connected workflow across the clinical-trial lifecycle.

For Admins

Centralized control over projects, users, clinicians and configuration.

For Project Teams

Clear ownership of assignments, visits and approvals.

For Sites

A structured way to initiate and manage patient visits.

For Clinicians

Focused web/mobile workflows for completing visits and documentation.

For Investigators

A clear review point for submitted clinical information.

For Monitors

Visibility without unnecessary editing access.

Live Product

2024–2025 · 2026 enhancement

Medora : Connecting people, projects and clinical workflows in one platform

Designing a clinical-trial operations platform that connects project teams, sites, clinicians and patients across the entire visit lifecycle.

Role

Product / UX Designer, UX Research, UI Designing, Prototyping & Testing

Platforms

Web Application · Responsive mobile for Clinicians

Timeline

4 Weeks of Explorations - 2024–2025 · 2026 enhancement

18.My Learnings & Reflection

The hardest part wasn't designing individual screens.

It was understanding how every role connects.

A Site User initiates a visit.

A Project Coordinator assigns it.

A Clinician performs it.

An Investigator reviews it.

A Project Team closes the loop.

Thank you for
exploring Medora.

Working on Medora was a valuable experience that strengthened my product thinking, problem-solving, and ability to simplify complex healthcare workflows into clear, intuitive, and user-focused experiences.