Usability Evidence for Digital Health Products

Usability is a safety property in digital health

IEC 62366 and FDA human factors guidance treat use errors as design failures that can harm patients. For digital health products — clinician dashboards, patient apps, alarm interfaces, infusion programming screens — usability evidence is not optional polish.

Teams that plan usability alongside functional requirements avoid costly redesign after validation failures.

Formative usability during design

Formative studies identify problems while they are still cheap to fix.

• Use scenarios derived from intended use and task analysis.
• Early prototypes tested with representative users (not only internal staff).
• Critical tasks identified — those where error could cause harm.
• Findings fed back into requirements and UI design iterations.
• Known use-related risks updated in risk management file.

Summative validation before release

Summative testing demonstrates that residual use-related risk is acceptable under realistic conditions.

• Test protocol defines tasks, success criteria, and data collection method.
• Participants match intended user profiles (experience, environment, stress).
• Simulated clinical context where possible (lighting, interruptions, gloves).
• Close calls and use errors classified and traced to design root cause.
• Validation report documents methods, results, and conclusions.

Connected product considerations

Connectivity introduces usability risks that standalone apps do not have.

• Connection status visible and understandable to users.
• Error messages distinguish user error, device fault, and network failure.
• Alarm presentation supports correct clinical response within required time.
• Setup and pairing workflows tested with naïve users.
• Labelling and IFU tested for comprehension.

Integrating usability with software V&V

Usability findings should generate requirements and tests like any other design input.

Link usability test scripts to hazard analysis. A use error that closes a risk control should have regression coverage in future releases.