In most countries, manufacturers must establish, document and maintain a usability engineering process. The key standard is IEC 62366-1 (2015, with corrigendum 2016 and amendment 2020). The whitepaper explains how the process is structured, which evidence is expected at each step and how to meet the requirements. A dedicated section relates the process to FDA expectations.
What you get
- a management summary of the purpose and benefits of the process
- the ten steps according to IEC 62366-1, each with its goal and expected output
- the link to risk management according to ISO 14971
- how the process relates to FDA expectations: critical tasks, human factors validation, the guidance documents of 2016 (revised 2026) and May 2026, and the QMSR
- an overview of what belongs in the usability engineering file
- pointers for further reading in IEC/TR 62366-2
Who the whitepaper is for
For everyone who is responsible for or contributes to the process in a medical device project, whether setting it up from scratch or checking an existing process for gaps:
- Usability Engineer / Human Factors Specialist
- UX / HCD Professional
- Regulatory Affairs / Quality Manager
- R&D / Development Manager
- Project / Product Manager
- Head of Product Digital Health
- Founder / CTO Health Startup
The process in ten steps
For each step you will find a short description and the matching wiki term here. The whitepaper explains each step in detail, together with the expected evidence.
Analyse
Who uses the product for what, and where can use become hazardous?
- 1Prepare the use specification
Describe the intended use, intended users, use environment and operating principle.
In the wiki: Use Specification - 2Identify user interface characteristics related to safety and potential use errors
Which characteristics of the user interface affect safety, and which use errors are conceivable?
In the wiki: Safety-related Characteristics - 3Identify known or foreseeable hazards and hazardous situations
Known and foreseeable use-related hazards, linked to risk management.
In the wiki: Hazardous Situation - 4Identify and describe hazard-related use scenarios
Sequences in which a use error can lead to a hazardous situation.
In the wiki: Hazard-related Use Scenario - 5Select the hazard-related use scenarios for summative evaluation
Decide which scenarios will be demonstrated at the end, with a rationale.
In the wiki: Critical Task
Design and evaluate formatively
Develop the user interface and test it with users early.
- 6Establish the user interface specification
Testable requirements for the user interface, derived from the analysis.
In the wiki: User Interface - 7Establish the user interface evaluation plan
Plan objectives, methods and criteria for formative and summative evaluation.
In the wiki: Usability Engineering File - 8Design, implement and evaluate formatively
Develop iteratively and use expert reviews or user tests to find weaknesses early.
In the wiki: Formative Usability Evaluation
Iterative, not linear: Findings from formative evaluation feed back into analysis and specification. The steps repeat until the user interface is ready for summative evaluation.
Demonstrate
Provide evidence that the user interface can be used safely.
- 9Perform the summative evaluation
Test with representative users whether the selected scenarios are handled safely.
In the wiki: Summative Usability Evaluation - 10Evaluate the residual use-related risk
Transfer the results to risk management and assess the residual risk.
In the wiki: Use-related Risk
Simplified view: the grouping into three phases is for orientation only. IEC 62366-1 describes the ten steps without this grouping.
Further reading in our knowledge base: identification of hazard-related use scenarios, formative usability evaluation according to IEC 62366-1 and tailoring the process to your organisation.
The usability engineering file
All results of the process come together in the usability engineering file: from the use specification and the hazard-related use scenarios to the reports of formative and summative evaluation. The whitepaper lists which documents belong in it and how they are linked.
