Most healthcare CX apps look like consumer or B2B SaaS products because the people building them came from consumer or B2B SaaS. The frameworks transfer in obvious ways — design systems, component libraries, accessibility tokens, journey maps, analytics. They do not transfer in the ways that matter most.
The user is not a user. They are a patient. And patients use software differently than the people the design playbooks were written for.
This is not an abstract critique. We have spent years working inside healthcare design systems, watching patterns that win on every other surface produce measurable patient experience failures in healthcare. Here are the eight differences that actually matter.
1. Engagement is not the goal
In consumer and B2B SaaS, engagement is the north star. Daily active users, time on site, feature adoption, retention curves. The product is better when people use more of it for longer.
In healthcare, engagement is a failure mode. A patient who is spending a long time in the billing portal is a patient who cannot figure out what to pay. A patient who comes back to the patient portal three times to look at the same lab result is a patient whose lab result was not clearly explained the first time. A patient who clicks five FAQ entries is a patient whose primary task did not have a clear answer.
The healthcare CX metric is the inverse: task completion at minimum cost. Did the patient finish what they came for, in as few steps and as little time as possible, without calling support? That is the score.
2. The user is anxious
The single biggest difference between healthcare users and other users is that healthcare users are using the product on a bad day. They got a bill they did not expect. They got a result they cannot interpret. They are looking up symptoms at midnight. They are scheduling an appointment for a parent who is declining.
Patterns that work for the calm engaged user — onboarding modals, feature tooltips, gamification, progress bars, animated transitions, anything that requires patience to navigate — fail under anxiety. The patient skips the tooltip. They miss the modal. They tap the wrong thing because the animation is still finishing. Healthcare CX design has to assume the user is not at their best.
3. The audience skews older and more accessibility-dependent
The B2B SaaS user is, on average, in their 30s, on a recent laptop, with good vision and fine motor control. The healthcare patient is, on average, ten to twenty years older, frequently on a phone, frequently with some level of visual or motor impairment, and frequently using assistive technology.
Default font sizes that look fine in a SaaS dashboard are unreadable for a 70-year-old. Tap targets that are 32px work for a designer in their office and fail for a patient with tremor. Color contrast ratios that pass WCAG AA can still be illegible in bright daylight on an older screen. Healthcare CX apps need to design at the floor of the user population, not the ceiling.
4. Trust is a design property, not a marketing one
In B2B SaaS, trust is built through marketing — case studies, testimonials, security pages, certifications. The product surface mostly assumes trust.
In healthcare, every screen has to earn trust on its own. A bill that does not look like the bill the patient is used to looks like a scam. A portal that looks too sleek looks unaffiliated. An app that asks for too much information up front looks like a phishing attempt. The visual language of healthcare CX has to feel institutional in a particular way — recognizable, conservative, clearly affiliated with the provider — because patients have been conditioned to distrust unfamiliar healthcare communications.
This is not an argument for boring design. It is an argument for design that is recognizably part of a health system, not a startup.
5. Comprehension beats elegance
A beautifully typeset clinical summary that the patient cannot understand is worse than an ugly one they can. Healthcare CX has to optimize for comprehension first — plain language, defined terms, prominent next steps — and aesthetic considerations second.
This is where a lot of design talent gets in its own way. The instinct of a strong designer is to remove redundancy, condense language, and use visual hierarchy to imply structure. In healthcare, that instinct produces patient documents that are technically minimal and functionally useless. Redundant labels, full sentences, explicit explanations, and over-clarified next steps are not weaknesses in healthcare CX — they are features.
6. The portal is not the experience
In B2B SaaS, the product is the experience. The customer’s relationship with the company is mostly mediated by the application.
In healthcare, the patient-facing app is one surface among many — the bill, the message, the appointment confirmation, the front desk, the lab, the pharmacy, the post-visit summary. A great patient portal that ships next to a terrible billing statement produces a bad patient experience overall. The app team that designs only for the app, without designing for the seams between the app and the other surfaces, builds a product that is locally good and globally invisible.
This is why healthcare CX apps need to ship with a journey map — not as a deliverable, but as a north star. The map is what tells the app team what comes before the app, what comes after, and where their surface fits in the cumulative experience.
7. Compliance is upstream of design, not downstream
In most software, compliance review happens at the end. Legal looks at the privacy policy, security audits the data handling, accessibility gets a final pass. Design has already happened.
In healthcare, this sequence produces designs that get redone. HIPAA constraints on what information can appear together, plain-language statutes on what billing has to say, transparency rules on what pricing has to be shown, accessibility minimums on contrast and tap targets — all of these are design constraints, and they are most efficiently absorbed at the start.
The design partners that work well in healthcare bring compliance into the brief. The ones that do not produce work that has to be retrofitted, usually losing most of the design quality in the process.
8. The lifetime of the product is longer
B2B SaaS products live in a fast-moving design landscape. They get redesigned every two to four years to feel current. Patterns are aggressive, fashions matter, and products that look dated lose customers.
Healthcare CX apps live longer. The patient population is more conservative, the brand of the health system is meant to feel stable, and the cost of changing the visual language is high — every change creates a wave of patient questions and a new round of staff training. Healthcare design has to age well. Decisions made today need to still feel right in five or seven years. That implies a quieter visual language, more durable type choices, and color palettes that read as institutional rather than current.
What this means in practice
If you are building a healthcare CX app, the practical implication of all of this is that you should resist most of the defaults of consumer and B2B SaaS design. Specifically:
- Optimize for task completion, not engagement. Measure success by how fast the patient finishes the primary task.
- Design at the floor of the user population. Older patients on older phones in bright daylight.
- Use plain language even when it feels redundant. Define every term that a patient might not know.
- Build the visual language to feel institutional. Recognizably part of the health system. Conservative on purpose.
- Treat compliance as an input. Get legal in the room early. Build the constraints into the design system.
- Design for the seams. The app does not live alone. It lives next to the bill, the message, the front desk, and the lab.
None of this is a critique of B2B SaaS or consumer design. The patterns are right for those contexts. They are simply being applied — often unconsciously — in a context where the user, the stakes, and the lifetime of the work are different. Healthcare CX is its own discipline. The teams that recognize that produce better outcomes for patients, and quieter, more durable products for the organizations that ship them.