Health UX Studios

Clinical & Provider-Facing Tool Design Studios (2026)

  • 3 studios
  • Dashboards · internal tools
  • Field, admin and provider software

This category covers the software healthcare workers use that patients never see — internal dashboards, field-technician portals, incident-reporting systems, administrative platforms. It’s an unglamorous design problem compared to a slick patient app, and that’s exactly why it’s underserved: most “healthcare UX” portfolios skip straight past it. We looked for studios with named internal tools and, where possible, actual measured outcomes, not just a claim of “streamlined workflows.”

Best for

Which clinical or provider-tool studio fits your project?

Field-technician tools

Single-task tools used under real-world conditions, often on a phone or tablet.

  • Create Ape logo

    Create Ape

    Southern California

    Redesigned Abbott’s ID NOW field-technician portal, moving a manual software-update process onto a remote platform for 100+ accounts.

Profiles
01Create Ape logo

Create Ape

The tools that never make a demo reel, measured anyway

Southern California

Websitecreateape.com

The track record
  • Redesigned Abbott’s ID NOW field-technician portal, moving a manual software-update process onto a remote digital platform for more than 100 accounts — the published, client-reported results: a 135% usability increase, 161% productivity increase, and 9,900% ROI on the engagement
  • Designed the UX for Performance Health Partners’ incident-reporting platform, which has ranked #1 in its Best in KLAS category for four consecutive years running — a rating earned through independently verified interviews with the providers who actually use the software, not a design-agency-issued claim
  • Founded and led by Al Fard, whose prior work spans Siemens Healthineers, Abbott, and the U.S. Department of Veterans Affairs, giving the studio genuine pattern recognition for internal, operations-heavy healthcare software
Signature strength

Measured impact on tools nobody screenshots. Most internal healthcare tool redesigns never get evaluated with real numbers — Create Ape’s Abbott and Performance Health Partners work both did, and the results are published, not just claimed.

Choose them if

you’re redesigning an internal tool — field operations, incident reporting, technician workflows — where you want a studio that measures and publishes actual outcomes.

Look elsewhere if

your project is a patient-facing consumer app — Create Ape’s strongest, most quantified work is specifically on the provider and operations side.

02Fuselab Creative logo

Fuselab Creative

Turning a county-by-county health crisis into a screen an administrator can act on

McLean, VA (Washington, DC area) · Est. 2017 · GSA contract holder

Websitefuselabcreative.com

The track record
  • Built a government public health dashboard using choropleth maps for geographic distribution and progressive-disclosure panels that let administrators drill from a state-level overview down to county-level detail without losing their place
  • The project is now in its second consecutive two-year government contract — a renewal that reflects the dashboard actually being used, not just delivered once and forgotten
  • Eight years of continuous work with NIH and DHCS gives the studio a specific, repeat understanding of how public health administrators actually make decisions under real operational pressure
Signature strength

Geographic and hierarchical data at administrator scale. Fuselab’s specific skill is letting one person go from “what’s happening across the whole state” to “what’s happening in this one county” without the interface losing them along the way.

Choose them if

you’re building an administrator-facing dashboard that has to surface geographic or hierarchical health data clearly under real decision-making pressure.

Look elsewhere if

your tool is a single-technician, single-task workflow rather than a multi-level administrative dashboard — Create Ape’s field-technician work runs closer to that problem.

03The Skins Factory logo

The Skins Factory

Provider-to-provider coordination, not just patient-to-provider

Fort Lauderdale, FL · Est. 2000

Websitetheskinsfactory.com

The track record
  • Redesigned a provider-facing platform for InnovaMD, an Anthem company, covering referrals, authorizations, eligibility checks, and care coordination — internal operations that never touch a patient’s screen directly
  • InnovaMD returned years after the first engagement for a separate, different portal project, a genuine repeat-client signal for provider-side operational work specifically
  • 25 years of practice spanning both patient- and provider-facing healthcare software, giving the studio a working sense of how the two sides of the same workflow need to connect
Signature strength

The provider-to-provider handoff. Referrals, authorizations, and care coordination are where healthcare operations quietly break down — Skins Factory’s work is specifically aimed at that connective layer.

Choose them if

your tool manages referrals, authorizations, or care coordination between providers rather than a single internal workflow.

Look elsewhere if

you need a studio with published, quantified outcome metrics specifically — Create Ape’s case studies carry harder numbers.

Compare

Quick compare

Studios compared by headquarters and where each is strongest. Facts only, no scores.
StudioHQWhere they’re strongest
Create ApeSouthern CaliforniaField-technician and internal operations tools, with quantified results
Fuselab CreativeMcLean, VAAdministrator-facing government health dashboards
The Skins FactoryFort Lauderdale, FLProvider platforms for referrals and care coordination

Which internal tools each studio has shipped

Internal healthcare software splits into field and operations tools, administrator dashboards and provider-to-provider coordination. This shows which of those each studio’s named work covers, and the outcome evidence behind it.

Which internal tools each studio has shipped. A filled cell means a named project in that area; a dash means none named.
Studio Field & operations toolsTechnician portals, incident reportingAdministrator dashboardsGeographic, hierarchical dataProvider coordinationReferrals, authorizations, eligibilityOutcome evidenceMetrics or renewals on record
Create ApeAbbott ID NOW portal; Performance Health Partners incident reporting——135% usability, 161% productivity (Abbott); Best in KLAS #1 four years (PHP)
Fuselab Creative—Public health dashboard, state to county—Second consecutive two-year contract
The Skins Factory——InnovaMD provider platform (Anthem)InnovaMD returned for a second project

Filled cells name the project behind them. A dash means no named work in that area, not a weakness score.

Red flags

Red flags when evaluating a clinical or provider-tool studio

Red flag

A portfolio entirely of patient-facing work, with internal tools mentioned only in passing.

Designing for clinicians and administrators under operational pressure is a different discipline than consumer-facing design — ask for a specific internal-tool case study.

Red flag

No measured outcomes, only visual before/afters.

A studio with real experience in this category should be able to point to a usability, productivity, or adoption metric, not just a cleaner-looking screenshot.

Red flag

No understanding of how the tool fits into a broader operational workflow.

An internal tool rarely exists alone — ask how the studio approached what happens immediately before and after someone uses the screen they’re redesigning.

Red flag

No experience designing for time-pressured, high-volume daily use.

Internal clinical tools get used dozens of times a day by the same person — a studio should design for that repetition, not a one-time delightful first impression.

Before you sign

Before you sign

  1. 1

    Ask for a specific, named internal tool with a measured outcome

    Usability score, productivity change, adoption rate — not just a description of the redesign.

  2. 2

    Clarify who the primary daily user is

    Field technician, administrator, care coordinator — since each has different workflow pressures.

  3. 3

    Ask how the studio validated the design with real users performing real tasks,

    not just internal stakeholder reviews.

  4. 4

    Get a reference from an operations or IT stakeholder,

    not just the product owner who commissioned the redesign — they’ll have a more honest read on daily usability.

FAQ

FAQ

Why is provider-facing and internal tool design so often overlooked compared to patient apps?

Internal tools don’t get demoed to investors or reviewed in app stores, so they attract less design investment even though the people using them — technicians, administrators, care coordinators — often depend on the same software dozens of times a day, all day, every day.

What’s different about designing for daily, repetitive professional use versus occasional consumer use?

A tool used dozens of times a day needs to minimize repetitive strain and cognitive load over the course of a shift, not just make a good first impression. Small friction points that seem trivial in a demo compound into real fatigue and error risk across a full workday.

How do we measure whether an internal healthcare tool redesign actually worked?

Look for concrete, before-and-after metrics — task completion time, usability scores, error rates, adoption or renewal signals — rather than only visual polish. A studio with real experience in this category should be able to describe how it measured success on a past project.

Should provider-facing tools go through the same accessibility review as patient-facing ones?

Yes — WCAG standards apply regardless of audience, and provider-facing tools often get overlooked for accessibility review simply because they’re not public-facing, which is a real gap worth asking about directly.

What’s the difference between designing a field-technician tool and an administrator dashboard?

A field-technician tool typically supports a single, focused task performed under real-world conditions — often on a phone or tablet in an imperfect environment. An administrator dashboard usually needs to support exploration across large, hierarchical, or geographic datasets. They call for different information architecture instincts.

Does a provider-facing tool need the same HIPAA rigor as a patient portal?

Generally yes, if it touches protected health information at any point, which most clinical and care-coordination tools do. Ask specifically how the studio handles role-based access and audit logging, since internal tools often have more complex permission structures than patient-facing software.

What does clinical and provider-facing tool design typically cost?

It varies by scope and studio tier. A single-workflow internal tool redesign can be scoped in the tens of thousands; a multi-level administrative dashboard or a platform spanning multiple provider roles, closer to Fuselab’s or Skins Factory’s work, runs higher given the added complexity.

How long should we expect a provider-facing tool redesign to take?

It depends heavily on how many user roles and workflows the tool serves. A focused, single-role tool can move in a few months; a platform serving multiple provider types with different permission levels and workflows, like a referral and coordination system, typically takes longer to research and validate properly.