Guide: How to Choose a Healthcare UX Studio

Before you look at any studio, get specific about which of these you’re solving:

• Patient portal or EHR/EMR. Registration, records, messaging, and the clinical record system itself — work that has to survive decades of regulatory accretion and real clinical workflow.
• Telehealth and virtual care. The harder problems live before and after the video call — scheduling, intake, documentation, and keeping patients on a treatment plan between visits.
• Health and fitness apps. Consumer retention and habit formation, closer to a behavior-change problem than a clinical one.
• Medical device UX. Interfaces subject to FDA human factors review under IEC 62366-1, whether the device is physical hardware or Software as a Medical Device (SaMD).
• Clinical and provider-facing tools. Internal dashboards, field-technician portals, and administrative software used dozens of times a day by the same person — a different design problem than anything patient-facing.

Not every healthcare product carries the same regulatory weight, and over-hiring for compliance you don’t need wastes budget just as much as under-hiring for compliance you do.

• HIPAA and PHI handling applies to nearly everything that touches patient data, from a fitness app with health logging to a full EHR.
• FDA human factors and IEC 62366-1 apply specifically to medical devices and SaMD — ask early whether your product could be classified this way, since it changes the entire design process.
• WCAG 2.1 AA accessibility is the practical baseline for anything patient-facing, and Section 508 applies on top of that for government health programs.
• State-level telehealth regulation — licensing, prescribing rules, consent — shapes provider-facing workflow specifically in virtual care products.

Risk shows up differently by category:

• EHR and clinical tools fail when they ignore how clinicians actually work today, reproducing old problems in a new visual skin.
• Medical devices fail expensively and dangerously when a misread data point or confusing control leads to a wrong clinical decision.
• Telehealth fails quietly, at the edges — a confusing intake form or a scheduling flow that doesn’t match how an anxious patient behaves, long before the video call even starts.
• Fitness and wellness apps fail on day 30, not day one — motivation and retention design matter more than onboarding polish.
• Internal provider tools fail from accumulated daily friction — small annoyances that compound across dozens of uses a day, every day.

Costs vary enormously by category and studio tier:

• Boutique or subscription-model studios can offer ongoing design capacity starting in the low tens of thousands.
• Project-based healthcare engagements commonly scope from the low tens of thousands up, depending on regulatory and integration complexity.
• Government-scale or enterprise health-system work carries higher minimums that reflect procurement, compliance, and stakeholder complexity.
• Physical medical device development spanning industrial design, engineering, and FDA submission support runs substantially higher than software-only work.

• Ask for a named, verifiable product in your specific category — not general “healthcare experience” spread thin across every category on this list.
• Push past compliance taglines. Ask for one specific example of a compliance-driven design decision, not just a HIPAA-aware checkbox.
• Confirm the engagement model — embedded team, fixed-scope project, or ongoing retainer — since each carries a different cost and risk profile.
• Get a reference from a stakeholder at your scale, not just the studio’s flagship case study.

• Hiring a patient-app studio for a clinical tool problem, or vice versa. These are genuinely different disciplines even within “healthcare UX” — don’t assume strength in one transfers to the other.
• Skipping FDA human factors thinking until late in the process. Retrofitting usability engineering after a design is finished is far more expensive than building it in from day one.
• Treating “HIPAA-compliant” as a design credential rather than a data-handling baseline. Compliance is necessary but says nothing about whether the interface actually works for real users.
• Choosing based on portfolio polish alone. A beautiful concept screen that was never shipped, tested, or measured is not the same as real healthcare product experience.