Defining the experience architecture for bedside pharmacy fulfillment

Patients were sometimes leaving the hospital without medications essential to their recovery. Patient Engagement Advisors wanted to increase prescription fulfillment before discharge and reduce avoidable readmissions by bringing pharmacy fulfillment directly to the patient's room. At the start of the engagement, that was a goal, not yet a product: the roles a bedside transaction would touch, the workflow it would follow, the handoffs between digital and paper compliance processes, and the boundary between what the interface owned and what pharmacy operations owned were all still undefined. Interface design couldn't begin from stable requirements because those requirements didn't exist yet.

I led the UX architecture for this engagement, directing the research and coordinating a small group of part-time research, design, product, and implementation contributors as the one continuous full-time UX lead across a nine-week engagement. I owned the coherence of the product experience throughout, partnering with the leaders responsible for business strategy, pharmacy operations, clinical policy, and implementation. This case traces how I moved from an undefined bedside concept to a shared workflow model, an interaction architecture built on that model, and a design direction the team could carry into implementation.

The product existed as a goal, not yet an operating model

Before I could design an interface, I needed to understand what a bedside transaction actually required — and the existing system couldn't answer that. Patient context, transaction state, and payment each lived in their own modal. Closing a modal repeatedly obscured the patient's status and forced technicians to re-establish context. The workflow was also fragmented across digital and analog systems: some signatures were captured within specific transactions, like credit-card payment, while many pharmaceutical and compliance acknowledgements remained on separate paper forms stored behind the pharmacy counter. Technicians had to remember which requirement applied, retrieve the correct form, and reconnect that documentation to the active patient and transaction. The current product architecture could not reliably support the service model the hospital wanted to deliver: bedside fulfillment meant bringing that paper-based compliance process into the same digital transaction technicians were already juggling across modals, and no one had yet defined how those two systems should relate.

Before: one transaction split across two systems

On screen: context obscured by modal workflows

Patient context hidden

Product and transaction state obscured

Origin, progress, and next action unclear

Off screen: acknowledgements managed on paper

Privacy acknowledgement

Pharmacist consultation

Safety-cap preference

Generic illustrative reconstruction, not an original hospital document

Privacy, consultation, and pharmaceutical acknowledgements were managed on separate paper forms stored behind the pharmacy counter. Technicians had to determine which forms applied, retrieve them, capture signatures, and reconnect the documentation to the active patient and transaction.

Synthesizing fragmented operational input into one workflow

I directed ethnographic research across two hospital pharmacies, observing how technicians actually worked the floor — the paperwork, compliance and signature requirements, payment variability, and how pharmaceutical category changed what a transaction required. Going in, the working assumption was that a transaction was a fairly uniform sequence with a few variants; what the research showed was that variability by pharmaceutical category, payment path, and compliance requirement wasn't an edge case, it was the baseline of every shift, and a design built around the uniform case would have broken on contact with real transactions. I synthesized those observations into a single patient-transition workflow — a shared model of the operational sequence technicians needed to complete as one continuous bedside transaction, which gave the rest of the team a common reference for what the product actually had to do:

Six stages of one patient-transition workflow — not six separate tools.

Translating the workflow model into product-design requirements

The hospital's objective wasn't simply to deploy a mobile POS — it was to increase the number of patients who left with the medications they needed. Working from the patient-transition workflow, I translated that outcome into the specific UX, interaction, and workflow conditions the interface had to support, giving the team a defined design target instead of an open-ended goal:

Those requirements became the interaction architecture.

Interaction Architecture

Rather than handing the workflow model to product management as a set of requirements and letting screens get designed against it piecemeal, I translated it directly into a spatial interaction architecture — a single structure the rest of the team could design and build against consistently, instead of one-off flows per transaction type. The spatial model replaced modals with fixed, predictable regions. Patient, prescription, basket, and transaction state stayed visible in a persistent center workspace, designed to reduce the need to reconstruct status mid-transaction. Contextual controls surfaced from the left based on the active task.

Signature and confirmation entered from the right, consolidating requirements previously split between specific digital transactions and paper forms behind the counter into one interaction layer, so compliance became part of the active transaction rather than a separate paper process. Critical alerts entered from the bottom, so blocking issues were visually distinct from requirements that could wait.

One architecture, reused across every transaction type, rather than a custom flow for each.

Final Design

From interaction model to final design

Working with our part-time designer, I carried the spatial architecture through to a final design direction that gave the team a clearer foundation for implementation planning — a stable workspace that preserved patient and transaction context while temporary actions appeared only when needed.

Final design direction

1 2 3 4

1. 1

   Patient and input workspace

   Patient and prescription context remained visible in the design throughout the transaction.

2. 2

   Persistent basket and payment

   Transaction contents and payment state were designed to stay available while related tasks were addressed.

3. 3

   Medication status and requirements

   Medication-level status, requirements, and blockers were surfaced within the active transaction.

4. 4

   Completion state

   The completion action reflected whether required transaction conditions had been addressed.

Reported Outcomes

Following the initial implementation, the client reported that orthopedic-surgery readmissions decreased from approximately 7% to 4.4%, alongside increased prescription capture.

This was a client-reported outcome; the project team did not independently measure it or attribute it solely to the UX work.

Beyond that reported number, the more durable output of this engagement was a reusable spatial architecture and a single patient-transition workflow model, in place of six one-off transaction flows — giving product, design, and implementation partners a shared reference for what the product needed to do and how it needed to behave. Coordinating part-time research, design, and implementation contributors against that model kept the work coherent across a nine-week engagement, rather than fragmenting into disconnected pieces as each contributor rotated on and off.

Reflection

This case is less about a finished pharmacy interface and more about what it takes to move an ambiguous product toward implementation: directing research that corrects the team's working assumptions, synthesizing fragmented operational input into one workflow model, and translating that model into an architecture that enabled a small, part-time team to design and build toward the same coherent product model. My remit was the UX architecture, the research direction, and the design continuity that held those contributions together, in partnership with the leaders responsible for business strategy, pharmacy operations, clinical policy, and implementation.