Tissue Trace — Designing Proof Into Every Handoff

Healthcare · USA · Responsive Web · AI-Assisted

Tissue Trace is a compliance-first operating system for birth tissue donation. It follows a case from eligibility and digital consent through bedside collection, split-path logistics, lab intake, and final QA disposition.

The Challenge

Birth tissue donation combines an unpredictable clock, a fragmented set of organisations, strict regulatory requirements, and a donor who may be completing consent near childbirth. The experience had to be calm and low-burden for donors while remaining precise, permissioned, and fully attributable for staff.

Experience Architecture

The platform has three coordinated surfaces:

• Donor portal — eligibility, three signing moments, documents, due-date management, and neutral progress updates.
• Bedside staff app — a scan-first mobile and tablet stepper with hard blocks, credential gates, and minimal typing.
• Operations and admin — desktop workboards for users, hospitals, labs, routing, custody, deviations, and audit.

Tissue and maternal blood travel through independent custody paths. “In transit” is not a manually selected status: the system emits it only after a dual-authenticated courier handoff.

Donor Experience

The donor dashboard answers what happens next, keeps signed documents in one place, makes the expected due date easy to manage, and communicates donation progress in neutral, PHI-safe language.

AI-Assisted Prototype

This project was one of our first deep integrations of AI into the design-engineering workflow. A working Super Admin prototype made navigation, state changes, permission logic, filtering, user and QA-scope management, lab configuration, versioned routing, and audit inspection tangible before implementation.

Design System

Figma variables and semantic design tokens create a shared foundation across donor, bedside, and administrative contexts. The system encodes action, success, warning, critical, and surface meaning while supporting role-aware patterns, accessible interaction targets, visible focus, inline validation, and audit metadata.

Outcome

Compliance became the interaction model rather than a reporting layer added after design:

• Custody changes are validated system events.
• Overrides create traceable deviations instead of bypassing the record.
• Separation of duties is enforced in the interface.
• Enrollment, collection, logistics, lab intake, and governance share one scalable product foundation.