Question Clearly sourced

Expert knowledge for digital decisions

What requirements does IEC 62366 place on usability?

Short answer

IEC 62366-1:2015 with Amendment 1:2020 requires a safety-related usability engineering process. Manufacturers must determine the context of use, user groups, critical user actions, and hazard-related usage scenarios, iteratively test the user interface, and demonstrate through a summative evaluation that remaining use-related risks are acceptable.

Usability is part of product safety

IEC 62366-1:2015+A1:2020 primarily considers safe operation of a medical device rather than comfort or aesthetic design. The standard describes a usability engineering process that identifies and reduces risks from correct use and from use errors. Deliberate actions that fall outside any reasonable use are excluded from this consideration.

The regulatory reference is found in the MDR: Annex I Number 5 requires risks to be minimized as far as possible through ergonomic features and the use environment, taking into account the knowledge, experience, training, and physical capabilities of the intended users. For products intended for use by laypersons, Annex I Number 22 contains additional requirements.

What must be documented

A robust process includes at least:

  • a Use Specification with medical purpose, user profiles, patient groups, use environment, and functional principle,
  • the description of safety-related characteristics of the user interface,
  • known or foreseeable use errors and hazard-related usage scenarios,
  • a user interface specification with verifiable requirements,
  • an evaluation plan as well as results of formative and summative testing,
  • the linkage of results with the risk file according to ISO 14971,
  • a traceable usability engineering file.

Formative evaluations accompany the development. Prototypes, comprehension tests, or observations with representative users are used to identify weaknesses early and improve the design. Summative evaluations assess the safety-critical usage scenarios on a sufficiently representative, final, or production-like interface. This is not about a general satisfaction rating, but about objective data on successful, erroneous, and near-error actions and their causes.

Software requires a realistic context

In medical software, not only individual screen masks are part of the interface. Alarms, error messages, data imports, units, default values, timing behavior, and transitions between devices or roles can also be safety-relevant. A clinical professional at the workplace, a patient at home, and an administrator have different knowledge and risks. Therefore, tests should realistically depict the intended roles, tasks, devices, lighting and noise conditions, and time pressure.

The number of test subjects is not replaced by a single universal number from the standard. It must be justified based on user groups, risk, scenarios, and evaluation goals. IEC 62366-1 provides the process; whether a specific design is safe enough remains a product-specific, documented decision.

Example from practice

In an alarm app, it is not only checked whether the alarm is visible. A realistic scenario examines whether the intended user group correctly understands priority, patient assignment, and required actions even under time pressure.

Key facts

Standard
IEC 62366-1:2015+A1:2020
MDR Reference
Annex I Number 5 and Number 22
Two types of evaluation
formative and summative
Risk linkage
ISO 14971

Sources

All external claims are backed by traceable sources.
  1. 01
  2. 02
    IEC 62366-1:2015/AMD1:2020 International Electrotechnical Commission (IEC)
  3. 03
    Verordnung (EU) 2017/745, Anhang I EUR-Lex / Europäische Union

Ready for your next project?

Free initial consultation - no sales pressure, just clear answers.

Request consultation