Product leaders, operations heads and design teams at healthcare software companies - patient portals, clinical tools, credentialing and practice-management platforms - deciding whether and how to audit their product's UX.
- Most friction in healthcare workflows is accumulated UX debt, not regulatory necessity. An audit separates what can be safely removed from what is a genuine constraint.
- A useful healthcare audit combines four lenses: heuristic evaluation, journey and drop-off analysis, accessibility review and competitor benchmarking.
- Drop-off is usually cumulative - several small frictions across a multi-step process - rather than one broken screen.
- Rank findings by user impact, effort and compliance risk. A 60-page undifferentiated report rarely gets acted on.
- The stakes are high: physicians rated EHR usability at 45.9 out of 100 in a large national study, an "F" grade.
Healthcare teams are often more hesitant than most to run a UX audit. There is a reasonable worry that friction in a regulated workflow is simply the cost of doing things correctly - that the extra confirmation screen, the long form or the repeated identity check exists for a reason nobody should touch. Sometimes that is true. More often, the friction that makes clinicians, patients and administrators abandon a task is accumulated UX debt that nobody has had time to untangle.
A structured audit exists to tell the difference. This article explains what a good healthcare UX audit covers, how to run it, and how to turn findings into a plan a product team can act on.
Why healthcare software needs regular audits
Healthcare software carries a heavy usability deficit. In a national study of US physicians published in Mayo Clinic Proceedings, electronic health records scored a mean of 45.9 on the System Usability Scale - an "F", in the bottom 9% of technologies studied - and lower usability was strongly linked to burnout. Clinicians also spend a large part of their day in software; a time-and-motion study found nearly two hours of EHR and desk work for every hour of direct patient time.
Source: Sinsky et al., Annals of Internal Medicine, 2016
View as table
| Activity | Share of office time |
|---|---|
| EHR and desk work | 49.2% |
| Direct clinical face time with patients | 27% |
| Administrative and other tasks | 23.8% |
The "administrative and other" figure is the remainder of the day after the two measured categories reported in the paper.
For patient-facing products, the risk is different but just as real: people who give up on an online form call the practice instead, miss appointments or do not complete important steps. Every abandoned task has a cost somewhere else.
The four lenses of a healthcare UX audit
Healthcare products fail users in more than one way at once, so a useful audit runs several lenses together rather than as separate reviews:
| Lens | What it examines | What it finds |
|---|---|---|
| Heuristic evaluation | Core flows against established usability principles such as Nielsen's 10 heuristics | Confusing labels, missing feedback, inconsistent patterns, error-prone forms |
| Journey and drop-off analysis | Where users abandon tasks, using analytics where available and structured walkthroughs where not | The steps and moments where effort outweighs perceived value |
| Accessibility review | WCAG-informed checks of key templates and journeys | Contrast, keyboard, labelling and error-handling barriers |
| Competitor benchmarking | How comparable products handle the same flows | Expectations users bring from other tools, and proven patterns |
Nielsen Norman Group recommends three to five evaluators for heuristic reviews, because any single reviewer misses issues. In practice, pairing an experienced UX reviewer with someone who knows the clinical or operational context catches far more than either alone.
Drop-off is usually cumulative
When a workflow underperforms, the instinct is to look for the one broken screen. In healthcare credentialing and clinical-operations tools, the more common pattern is cumulative friction:
- A status label that is slightly ambiguous.
- Information that has to be entered again because an earlier step did not carry it forward.
- A form that asks for something without explaining why.
- A confirmation that appears for trivial actions, so people learn to click through it.
- An error message that says something is wrong without saying what.
Each is tolerable on its own. Together, they are enough to make someone give up or call support instead of finishing. That is why a good audit maps whole journeys, not just the screen with the highest exit rate.
How to run the audit
- Agree scope and goals. Choose three to six critical journeys (for example: provider onboarding, renewal, a clinician's daily worklist, patient booking) and define what success looks like for each.
- Gather evidence. Analytics funnels, support tickets, session recordings where permitted, and short interviews with a handful of users and support staff.
- Walk the journeys. Heuristic and accessibility review of every step, with screenshots, noting issues against named principles.
- Benchmark. Review two or three comparable products for the same journeys.
- Validate the biggest issues with users. Even a few moderated sessions confirm whether suspected problems are real. Five participants per round uncover roughly 85% of usability problems, according to Jakob Nielsen's analysis.
- Prioritise and present. A ranked list of findings with evidence and recommended fixes.
Prioritise by impact, effort and compliance risk
The output is only useful if a team can act on it. Every finding should be scored, not delivered as an undifferentiated list. In healthcare, add a third dimension: compliance risk.
| Score | User impact | Effort to fix | Compliance risk |
|---|---|---|---|
| 3 | Blocks or regularly derails a critical task | Weeks of work across teams | Touches a regulated step, clinical safety or consent |
| 2 | Slows users or causes errors they notice and recover from | Days of work for one team | Touches data that needs audit trails or review |
| 1 | Minor annoyance or inconsistency | Hours; copy or style change | No regulatory implications |
High impact with low effort goes first. Anything with high compliance risk needs review with your compliance or clinical-safety owner before changing - a "quick fix" in a regulated workflow may need more care than its effort score suggests.
What good audit output looks like
- A one-page summary of the most important findings and the recommended first moves.
- Each finding with a screenshot, the journey step, the principle it breaks, the evidence, the scores and a recommended fix.
- Quick wins separated from structural changes that need design and engineering time.
- Accessibility issues integrated with the rest, not in a separate appendix nobody reads.
- A suggested sequence for the next three months.
For a detailed example of what an audit uncovers in credentialing, see UX design for credentialing workflows.
The most common mistake I see healthcare teams make with UX audits is treating them as a one-time compliance exercise rather than a diagnostic. A good audit is not there to prove the product is fine. It is there to find the handful of places where real users are quietly giving up, and to be honest about which are worth fixing first.
On the healthcare credentialing platform I worked on, the findings that mattered most were not dramatic. They were the small, cumulative frictions across the credentialing journey that, fixed together, changed how trustworthy the whole product felt. That is usually where the return is: several small fixes that compound.
Frequently asked questions
How long does a healthcare UX audit take?
A focused audit of three to six critical journeys typically takes a few weeks, including evidence gathering, review, a few validation sessions and a prioritised report. Larger platforms or multiple user types take longer.
Do auditors need access to patient data?
No. Audits can use test accounts, anonymised or synthetic data and screenshots. Any access to live systems should follow your privacy and security policies.
Can we audit if we have no analytics?
Yes. Heuristic review, accessibility checks, benchmarking and a few user sessions still reveal most issues. Analytics sharpens prioritisation when it exists.
Should accessibility be a separate audit?
Integrate at least a WCAG-informed review of key journeys into the UX audit so fixes are prioritised together. A full conformance audit can follow for procurement or regulatory needs.
What happens after the audit?
Usually a sequence of quick fixes, followed by design work on the structural issues. Re-measure the same journeys afterwards to confirm the improvement.
Want to know where your platform is losing people?
A fixed-scope audit finds the answer before you commit to a redesign.
Sources
Every statistic in this article links to its original publisher. Figures were checked against these sources on September 29, 2026.
- Doctors give electronic health records an 'F' - ScienceDaily, reporting Melnick et al., Mayo Clinic Proceedings
- Allocation of Physician Time in Ambulatory Practice - Sinsky et al., Annals of Internal Medicine, 2016
- 10 Usability Heuristics for User Interface Design - Jakob Nielsen, Nielsen Norman Group
- How to Conduct a Heuristic Evaluation - Nielsen Norman Group
- Why You Only Need to Test with 5 Users - Jakob Nielsen, Nielsen Norman Group, 2000
