ISO 14971 Versus IEC 62366: Key Differences

A comparison of ISO 14971 versus IEC 62366 should not begin with the question, “Which standard applies?” For most medical devices with user interaction, both apply. The more useful question is how risk management and usability engineering evidence must work together to show that use-related hazards have been identified, controlled, and validated under representative conditions.

ISO 14971 establishes the framework for medical device risk management across the product life cycle. IEC 62366-1 establishes the usability engineering process used to identify, analyze, mitigate, and evaluate risks associated with user interaction. One is broader in scope; the other provides focused process expectations for a significant source of device risk: use error.

For development, quality, and regulatory teams, the distinction affects design inputs, verification planning, human factors validation, risk documentation, and submission readiness.

ISO 14971:2019 specifies a process for manufacturers to identify hazards, estimate and evaluate associated risks, implement risk controls, and monitor the effectiveness of those controls throughout the medical device life cycle. It is not limited to a particular hazard category. The process can address electrical shock, excessive temperature, biological contamination, incorrect therapy delivery, software failure, mechanical injury, and use error.

The standard expects a manufacturer to establish a risk management plan, define criteria for risk acceptability, perform risk analysis and risk evaluation, implement risk controls, evaluate residual risk, and conduct production and post-production activities. The resulting risk management file must provide traceable objective evidence that these activities were completed and reviewed.

IEC 62366-1:2015+A1:2020 addresses the application of usability engineering to medical devices. Its purpose is to reduce use-related risk by requiring a structured examination of intended users, intended use environments, user interfaces, reasonably foreseeable misuse, and use scenarios. The user interface includes more than screens and controls. It can include labeling, instructions for use, training materials, packaging, alarms, accessories, connectors, displays, and the physical configuration of the device.

IEC 62366-1 does not replace ISO 14971. It provides a disciplined way to develop and validate user-interface-related risk controls that support the ISO 14971 risk management process.

The Core Difference: Broad Risk Management vs. Usability Engineering

ISO 14971 asks whether a hazard could lead to harm and whether the associated risk is acceptable after controls are applied. A manufacturer may identify a hazardous situation in which a clinician selects an incorrect treatment setting, causing delivery of excessive energy. The risk analysis considers the sequence of events, the potential harm, the initial risk, the controls, and residual risk.

IEC 62366-1 asks a more specific set of questions about the same issue. Which users may select the setting? Under what environmental conditions? Can the display be misread? Are units clearly identified? Can the control be confused with another control? Is the alarm meaningful? Does the workflow encourage confirmation before therapy begins? These questions turn a general use-related risk into design and validation activities.

In practical terms, ISO 14971 provides the risk management structure, while IEC 62366-1 provides the usability engineering discipline needed to demonstrate that user-interface design adequately addresses critical use scenarios.

This relationship is particularly important for devices used under time pressure, with multiple user groups, or in environments where lighting, noise, protective equipment, patient condition, or workflow interruptions can affect performance. Infusion systems, patient monitors, diagnostic ultrasound systems, physiotherapy equipment, endoscopes, and connected home-use devices often require close integration between the two standards.

How the Documentation Connects

A common compliance weakness is treating the usability engineering file and risk management file as separate document sets that only reference each other at a high level. Regulators and notified bodies generally expect more direct traceability.

The ISO 14971 risk analysis should identify use-related hazards and hazardous situations. Those items should flow into usability engineering activities where applicable. The usability engineering file should document the analysis of known or foreseeable use problems, the identification of hazardous use scenarios, formative evaluations, user-interface specifications, and summative usability validation results.

The connection should work in both directions. If formative testing uncovers a new use error, confusing task sequence, or recurring user difficulty, the manufacturer should assess whether it creates a new hazardous situation or changes an existing risk estimate. The risk management file may need to be updated, along with design controls, labeling, training, verification, and validation plans.

A useful traceability chain often includes the identified hazard, sequence of events, hazardous situation, harm, risk control measure, user-interface requirement, formative evaluation evidence, validation task, acceptance criterion, and residual-risk assessment. The precise format can vary, but the evidence must allow a reviewer to follow the logic without relying on undocumented assumptions.

Formative Evaluation and Summative Validation Serve Different Purposes

IEC 62366-1 recognizes both formative and summative evaluation, but they should not be confused.

Formative evaluations occur during development. They may include expert reviews, heuristic assessments, simulated-use sessions, workflow analysis, prototype testing, and feedback from representative users. Their purpose is to find and correct user-interface problems before design finalization. Formative work does not need to replicate final validation conditions every time, but it must be sufficiently rigorous to inform design decisions and document remediation.

Summative evaluation, commonly called human factors validation, occurs on the final or production-equivalent user interface. It evaluates whether representative users can complete critical tasks safely and effectively in conditions that reasonably represent intended use. The study design should address the highest-priority tasks and use scenarios identified through risk analysis and usability engineering.

A successful summative study does not prove that no user will ever make an error. It provides evidence that the final design supports safe and effective use for the intended users, uses, and environments. Observed difficulties, close calls, task failures, and unexpected behaviors require careful analysis. Some findings may be acceptable with justification; others may require design changes and additional validation.

Risk Controls Must Be Evaluated Beyond Labeling

ISO 14971 follows a priority order for risk control: inherent safety by design, protective measures in the device or manufacturing process, and information for safety. IEC 62366-1 reinforces the practical importance of that hierarchy for user-interface decisions.

If a device setting can cause serious harm when selected incorrectly, a warning in the instructions for use may be necessary, but it is rarely sufficient as the primary control. The design may need constrained parameter ranges, confirmation steps, distinct connector geometry, differentiated visual presentation, alarm logic, interlocks, or workflow controls. The appropriate measure depends on the severity of harm, likelihood of the use sequence, user population, and clinical context.

This does not mean every control must be automated or that warnings have no value. Some devices rely on trained professionals operating in controlled environments; others are intended for lay users at home. A control that is appropriate for an anesthesia workstation may not be appropriate for a home-use therapeutic device. The manufacturer must justify the selected controls with risk-based evidence.

Where Testing Fits Into the Compliance Strategy

Usability evidence is one component of a broader safety and performance case. For many devices, the risk management file must also incorporate verification evidence from electrical safety, electromagnetic compatibility, acoustic output, ultrasound image quality, material characterization, mechanical performance, software verification, or other applicable testing disciplines.

The same design feature may affect multiple risk controls. For example, an alarm condition can involve electrical and software performance requirements, while its audibility, prioritization, display behavior, and user response require usability consideration. A treatment system may need performance testing to confirm output accuracy and human factors validation to show that users can select, initiate, monitor, and stop treatment appropriately.

Testing plans should therefore be developed with the risk management process in view. Each test should have a clear purpose: demonstrate conformity to a recognized standard, verify a design requirement, confirm a risk control, support performance claims, or provide evidence for a regulatory submission. Accredited laboratory data can strengthen this evidence when test methods, configurations, acceptance criteria, and reporting are aligned with the device’s intended use and applicable standards.

Building a Defensible Integrated Process

The most efficient approach is to integrate usability engineering early rather than waiting until the final design is ready for validation. Begin with clear intended users, uses, environments, and user-interface characteristics. Use those inputs to identify use-related hazards alongside technical and clinical hazards in the ISO 14971 process.

Then maintain traceability as the design matures. Risk controls should become measurable design requirements. Formative findings should feed back into the risk analysis. Summative validation should focus on critical tasks and realistic use conditions. Finally, the risk management review should consider whether all usability findings, verification results, validation outcomes, and residual risks have been appropriately addressed.

For teams preparing for submission, the practical value is not simply having an ISO 14971 file and an IEC 62366-1 file. It is being able to demonstrate that the device’s safety controls perform as intended and that the people expected to use the device can do so without introducing unacceptable risk. That connection is where a compliance strategy becomes credible product evidence.