Human Factors and Usability Engineering (IEC 62366-1)
IEC 62366-1 defines the usability-engineering process manufacturers apply to identify, understand, and mitigate use-related risks in medical devices — the risks that arise not from a device malfunctioning, but from a device functioning exactly as designed while a user operates it incorrectly. It is a distinct discipline from general risk management, focused specifically on the interface between device and user.
What an explainer is not
A topic explainer is SPEQ’s synthesis of what a practice involves, cited to the standards that govern it. It does not reproduce their text, and it does not determine which of them apply to your product or process.
[ POSITION IN THE FRAMEWORK ]
7 DIMENSIONS · 18 LINKSUse-related risk is the one hazard class the device cannot be tested into safety on: it arises from the interaction, so it has to be designed out, and a summative study at the end can only tell you whether you already did.
06 · QUALITY MATURITY — HUMAN FACTORS AND USABILITY ENGINEERING (IEC 62366-1), REACTIVE TO ADAPTIVE
Usability means the instructions were reviewed. Use error is treated as user error and answered with training and labelling.
A usability file exists and a summative evaluation was run, but it was run late, on the design that was already frozen, with participants who were not the intended users.
Use-related hazards are identified from task analysis of the real use environment, critical tasks are named, and formative work changes the design before summative testing confirms it.
Use error found after launch feeds back into design rather than into the instructions, and the hazard analysis is updated as real-world use diverges from the assumed use.
The interaction is designed so the critical tasks are hard to perform wrongly, and labelling carries information rather than carrying the mitigation.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 3
Derived from the 3 standards SPEQ maps to this subject, across 3 regulatory bodies: FDA, EC, IEC.
RECORDS & OBJECTIVE EVIDENCE
- The use specification: intended users, uses, and use environments
- Task analysis identifying critical tasks and the use errors associated with them
- Formative evaluation records, and the design changes they produced
- Summative evaluation with participants representative of each user profile
- The usability engineering file, linked to the ISO 14971 risk-management file
COMMON INSPECTION FINDINGS
- Use error mitigated by instructions and training where the design could have prevented it
- Summative evaluation run after the design was frozen, so it could confirm but not correct
- Participants not representative of the stated user profiles
- A use specification that describes an idealised environment rather than the real one
- Post-market use error not fed back into the hazard analysis
Why Use-Related Risk Is Its Own Discipline
A device can pass every functional and performance test and still cause patient harm if its controls are ambiguous, its display is misread under realistic conditions, or its intended user cannot reliably complete a critical task. IEC 62366-1 exists because these failure modes are not caught by conventional verification testing — they require observing real or representative users interacting with the device, or a faithful representation of it, under conditions that resemble actual use.
The standard sits alongside general device risk management (ISO 14971) rather than replacing it: usability engineering identifies and mitigates use-related hazards, and those hazards feed into — and are evaluated within — the device’s overall risk management file.
Core Process Elements
The IEC 62366-1 process centres on defining the intended use, users, use environment, and user interface; identifying use scenarios, particularly those involving use errors with potential for harm; and distinguishing “critical tasks” — those where a use error could cause serious harm — for focused mitigation and evaluation.
Formative evaluation (iterative, exploratory testing during design to refine the interface) and summative evaluation (a final, structured usability validation study demonstrating the finished design is safe and effective for its intended users) are the two evaluation modes the standard distinguishes, and summative evaluation of critical tasks is typically the piece regulators scrutinise most closely in a submission.
Regulatory Expectation
Both the EU Medical Device Regulation and FDA’s device quality-system framework expect usability engineering as part of design controls and risk management for devices where use error carries meaningful harm potential — it is not an optional add-on for “complex” devices only, though the depth of the usability file scales with the device’s risk profile and interface complexity.
A usability engineering file summarising the process, identified use-related risks, mitigations, and evaluation results is typically expected as part of the technical documentation or premarket submission supporting a device.
Common Pitfalls
Two recurring gaps: treating usability testing as a late-stage validation activity bolted on just before submission, rather than an iterative input to design from early in development; and testing with internal staff or engineers rather than individuals genuinely representative of the intended user population, use environment, and training level — a labelling change or an unfamiliar-to-clinicians icon can look perfectly clear to the people who designed it.
FREQUENTLY ASKED
Is usability engineering required for every medical device?
The depth of usability engineering scales with risk and interface complexity, but the underlying expectation to consider use-related risk applies broadly under both EU MDR and FDA’s device quality-system requirements — a device with no user interface at all (fully implanted, no user-facing controls) has a much thinner usability file than one with a complex on-screen interface.
What is the difference between formative and summative usability evaluation?
Formative evaluation is iterative and exploratory, used during design to identify problems and refine the interface; summative evaluation is a final, structured study, typically conducted on the near-final design, intended to demonstrate that critical tasks can be performed safely by representative users.
How does usability engineering relate to ISO 14971 risk management?
Use-related hazards identified through the IEC 62366-1 process are entered into and evaluated within the device’s overall ISO 14971 risk management file; the two standards are designed to interoperate rather than operate as separate, disconnected risk assessments.