Overview

Designing a Scalable Clinical Interaction Model for
Point-of-Care Diagnostics

At Siemens Healthineers, the Atellica DCA redesign was part of a broader
initiative to modernize point-of-care (POC) devices and align them with
a Common Interface Platform (CIP).

Historically, devices like the DCA Vantage operated with isolated interaction
models, resulting in:

• Inconsistent user experiences across devices
• Increased training complexity
• Limited scalability of design and engineering efforts

The Atellica DCA became an opportunity to apply and validate a standardized interaction framework within a real clinical workflow.

My Role

I led the workflow and interaction redesign for Atellica DCA, while aligning
the solution with the Common Interface Platform (CIP) principles.
This required:

• Translating real-world usability issues into reusable interaction patterns
• Collaborating with cross-functional teams to ensure consistency across
  hardware and software
• Balancing product-specific needs with platform standardization

Through usability testing and workflow analysis, it became clear:
The core issue was not just poor UI; it was the absence of a coherent interaction system connecting physical actions, digital guidance, and system feedback.

Design Strategy: From Workflow Fixes to Interaction System

Instead of solving isolated usability issues, I focused on defining scalable interaction patterns.

DCA Vantage before CIP

• 12+ fragmented steps
• Manual transitions
• Heavy cognitive load
• UI disconnected from physical actions

Persona 1: The Structured Operator

Workflow Entry:
Select Engine → Login → Insert Cartridge

Context
Experienced clinician or lab technician working in a controlled environment where protocols are strictly followed.

Goals

• Follow standardized workflow with minimal deviation
• Ensure traceability and compliance
• Reduce risk of procedural errors

Behaviors

• Prefers logging in before performing any action
• Navigates intentionally through system-defined steps
• Relies on system feedback for confirmation

Pain Points

• Friction when workflows are not clearly guided
• Risk of missing steps if UI lacks structured sequencing

Design Implication
Design must reinforce linear, guided workflows with clear checkpoints, confirmations, and compliance cues.

Persona 2: The Efficient Operator

Workflow Entry:
Login → Select Engine → Insert Cartridge

Context
Frequent user operating in high-throughput environments (e.g., ER, urgent care) where speed is critical.

Goals

• Minimize time to initiate test
• Reduce cognitive load during repetitive tasks
• Quickly move from login to action

Behaviors

• Logs in immediately to unlock system capabilities
• Skips unnecessary steps when possible
• Optimizes for speed over strict sequence

Pain Points

• Redundant steps that slow down workflow
• Excessive confirmations or system friction

Design Implication
Design should support fast-path interactions, shortcuts, and reduced step counts while maintaining safety.

Persona 3: The Reactive Operator

Workflow Entry:
Insert Cartridge → Login → Continue Workflow

Context
User operating in time-sensitive or interrupt-driven environments where immediate physical action precedes system interaction.

Goals

• FStart test as quickly as possible
• Avoid delays caused by system gating (e.g., login screens)
• Maintain momentum during urgent scenarios

Behaviors

• Inserts cartridge first as a natural physical trigger
• Logs in only when required by the system
• Works in a reactive, non-linear manner

Pain Points

• System blocks progress due to forced sequencing
• Disruption when UI does not adapt to real-world behavior

Design Implication
Design must support flexible entry points, allowing the system to adapt to user behavior rather than forcing rigid order.