IEC 62366-1: Medical Devices – Application of Usability Engineering to Medical Devices

💡 Standard Snapshot: IEC 62366-1 (Edition 1.0, 2015, with Corrigendum 1:2016) specifies the usability engineering process for medical devices. It establishes a framework for analyzing, designing, testing, and validating the user interface of medical devices to minimize use errors and ensure safe and effective operation by healthcare professionals and patients.

1. Scope and Field of Application

IEC 62366-1 applies to all medical devices that have a user interface. The standard provides a structured usability engineering process that, when applied, helps manufacturers identify and mitigate use-related hazards before devices reach the market. The standard covers both professional medical devices used by healthcare practitioners and devices intended for use by lay persons (including home-use medical devices).

Key regulatory bodies including the FDA (US), EMA (Europe), and NMPA (China) recognize IEC 62366-1 as a key standard for demonstrating reasonable assurance of safety and effectiveness with respect to the user interface. The 2015 edition introduced a significant shift toward risk-based usability engineering, integrating closely with ISO 14971 (risk management for medical devices).

Usability Engineering Phase	Key Activities	Deliverables
User Interface Design Input	User research, task analysis, use scenarios	User needs specification
Formative Evaluation	Iterative prototyping and testing with representative users	Formative evaluation reports
Summative Evaluation	Validation testing with specified users, use environments, and tasks	Summative evaluation report
Risk Management Integration	Use error analysis, risk control for use-related hazards	Use-related risk analysis

2. The Usability Engineering Process

2.1 User Interface Design Input

The standard requires manufacturers to establish the user interface design inputs based on a thorough understanding of the intended users, use environments, and use scenarios. This includes:

Identifying the intended patient population and their characteristics
Analyzing the skills, training, and knowledge of intended users
Documenting the physical, perceptual, and cognitive capabilities of users
Defining use environments (hospital, home, emergency, transport)

⚠️ Engineering Insight: The most common use errors identified in medical device adverse event reports relate not to complex clinical decisions but to simple perceptual and cognitive tasks: misreading displayed values, confusing similar-looking controls, and failing to hear or understand alarms. IEC 62366-1 emphasizes addressing these fundamental human factors issues through systematic usability engineering.

2.2 Formative Evaluation

Formative evaluation is an iterative process conducted throughout the design phase. It involves testing preliminary user interface designs with representative users to identify usability issues before the design is finalized. The standard recommends multiple formative evaluation cycles, each followed by design refinement. Sample sizes of 5-8 users per evaluation cycle are typically sufficient to identify the majority of usability issues.

2.3 Summative Evaluation

Summative evaluation is the final validation of the medical device user interface. It must be conducted with:

Representative users who match the intended user population
In representative use environments (or simulated environments)
Performing critical tasks that could affect safety or effectiveness
The final or near-final version of the user interface

✅ Design Recommendation: The standard strongly recommends involving users from diverse backgrounds in usability testing. This includes users with different levels of experience (novice to expert), different cultural backgrounds, and users with common age-related impairments (reduced vision, hearing, or manual dexterity) that may affect their interaction with the device.

3. Risk Management Integration

3.1 Use Error Analysis

A critical requirement of IEC 62366-1 is the systematic analysis of potential use errors and their consequences. This analysis is integrated with the overall risk management process per ISO 14971. The standard distinguishes between:

Use errors: Actions or omissions that lead to a different result than intended by the manufacturer
Abnormal use: Deliberate actions that bypass or defeat safety features
Unintended use: Use of the device for purposes not intended by the manufacturer

3.2 Risk Control for Use-Related Hazards

When use-related hazards are identified, the standard requires risk control measures in the following order of priority:

Inherent safety by design: Eliminate the hazard through design modification (e.g., physical keying to prevent incorrect connection)
Protective measures in the device: Add alarms, warnings, or interlocks (e.g., confirmation prompts for critical actions)
Information for safety: Provide instructions, training, and labeling

🚨 Critical Regulatory Note: Under IEC 62366-1, reliance solely on instructions and labeling as risk control measures is the least preferred option. Manufacturers must demonstrate that they have first exhausted design-based and protective-measure-based risk controls before relying on user training or warning labels. This principle, known as “alphabet soup” (the tendency for users to ignore warnings), is supported by extensive human factors research.

4. Documentation and Regulatory Compliance

The standard requires a usability engineering file that documents the entire process. This file typically includes:

User interface specification
Use scenarios and task analyses
Formative and summative evaluation protocols and reports
Use-related risk analysis
Traceability between use errors, risk controls, and verification/validation activities

IEC 62366-1 also defines several annexes providing practical guidance, including a frequently used “Usability Engineering Process” flowchart (Annex A), guidance on applying the process to home-use devices (Annex B), and a table relating usability engineering activities to risk management activities (Annex C, which was updated by the 2016 corrigendum).

Frequently Asked Questions (FAQ)

Q1: What is the difference between IEC 62366-1 and IEC 62366 (the 2008 edition)?

The 2008 edition of IEC 62366 was a general usability engineering standard. The 2015 edition was restructured as IEC 62366-1 with a stronger emphasis on risk-based usability engineering and closer alignment with ISO 14971 risk management. A companion standard, IEC TR 62366-2, provides informative guidance on implementing the usability engineering process.

Q2: Does IEC 62366-1 apply to software-only medical devices (SaMD)?

Yes. IEC 62366-1 applies to all medical devices with a user interface, including software-only medical devices (mobile apps, clinical decision support software, etc.). For SaMD, the user interface includes graphical user interface (GUI) elements, navigation flows, and input/output mechanisms.

Q3: How many participants are needed for summative usability testing?

The standard recommends a minimum of 15 participants per distinct user group for summative evaluation testing. This number is based on statistical models showing that 15 participants can detect approximately 97 % of usability problems that occur with a probability of 10 % or greater.

Q4: How does IEC 62366-1 relate to FDA human factors guidance?

IEC 62366-1 is harmonized by the FDA and accepted as a consensus standard. The FDA’s “Applying Human Factors and Usability Engineering to Medical Devices” guidance (2016) is closely aligned with IEC 62366-1 requirements. Compliance with IEC 62366-1 typically satisfies FDA expectations for human factors engineering, though additional FDA-specific documentation may be required for US market submissions.