The Healthcare Usability Crisis
We’ve shipped HIPAA-compliant software for enough healthcare organisations to understand something that rarely gets discussed in technical circles: the compliance conversation is often a distraction from the usability crisis. Electronic health record systems that take 14 clicks to document a routine visit. Billing platforms that require specialist training to operate. Telemedicine tools that work beautifully on a developer’s MacBook and break on the Android tablet mounted in a clinic room.
The Clinical Input Imperative
The organisations winning in digital health right now are doing something deceptively simple: they’re putting clinicians in the room during product design, not just the scoping call. Not as a checkbox for user research, but as genuine collaborators who can push back when a workflow doesn’t match how care is actually delivered.
Software built without clinical input creates friction at the point of care. Friction slows documentation. Slow documentation creates errors. Errors harm patients.
Designing for Real Workflows
Clinical workflows have constraints that don’t exist in other enterprise software contexts: one-handed operation while examining a patient, gloved hands that can’t use touchscreens reliably, interruption-heavy environments where multi-step flows lose their state, and time pressure that makes any friction intolerable.
Compliance and Usability Together
The most common false dichotomy in healthcare tech is the idea that compliance and usability are in tension. They’re not. HIPAA requires access controls; good UX makes those controls invisible through smart defaults and role-based interfaces. Audit logging is required; good engineering makes it automatic and transparent. The teams that treat compliance as a design constraint rather than a checklist build products that are both safe and usable.
- Put clinicians in the room during design, not just the scoping call
- Compliance and usability are not in tension design for both
- One-handed, gloved, interrupted use are real constraints design for them
- Test on the actual devices and environments where clinicians work
- Measure documentation time as a product metric, not just error rates