IEC 62366-1:2015+AMD1:2020
Medical devices — Application of usability engineering to medical devices
Standard Introduction
IEC 62366-1:2015+AMD1:2020 is an active standard published by International Electrotechnical Commission (IEC). It is commonly used across Medical Devices, Healthcare, Electronics and applies in Global.
Use this page to review the official documentation, current status, and the certification or assessment bodies most commonly associated with IEC 62366-1:2015+AMD1:2020.
Use Error Prevention
Focuses on identifying and mitigating use errors that could lead to harm — not user convenience, but safety-critical interactions between users and the medical device user interface.
User-Centered Process
Requires manufacturers to understand users, use environments, and user interface characteristics through structured analysis, including contextual inquiry and user profiles.
Summative Evaluation
Mandates summative (validation) usability testing with representative users performing critical tasks to provide objective evidence that the device can be used safely.
list_alt Usability Engineering Process
- Use specification and user profile definition
- Identification of user interface characteristics related to safety
- Identification of known or foreseeable hazards and hazardous situations
- Identification of hazard-related use scenarios
- Formative evaluation (iterative design testing)
- Summative evaluation (validation testing)
- Documentation in usability engineering file
- Integration with ISO 14971 risk management process
Who Needs to Comply?
All medical device manufacturers, including software-as-a-medical-device (SaMD) developers. Required by the EU MDR, recognized by the FDA as a consensus standard, and referenced globally for regulatory submissions.
Key Requirements
Use Specification
Define the intended users, intended use environments, and user interface characteristics of the medical device. Establish a use specification document that drives all subsequent usability activities.
Hazard-Related Use Scenarios
Identify use scenarios where foreseeable use errors or correct use could lead to hazardous situations. Analyze the user interface to determine which tasks are safety-critical and require focused usability engineering.
Formative Evaluation
Conduct iterative formative evaluations during design and development to identify usability issues early. Methods include cognitive walkthroughs, heuristic evaluations, expert reviews, and user testing with prototypes.
Summative Evaluation
Perform summative (validation) usability testing with representative users in simulated or actual use environments. Demonstrate that users can perform critical tasks safely and that residual use-related risks are acceptable.
Usability Engineering File
Maintain a usability engineering file documenting the entire process — use specification, hazard analysis, formative and summative evaluations, and evidence that use-related risks have been adequately addressed.
Implementation Roadmap
Prepare scope, ownership and obligations
Define the medical device usability engineering program scope across medical device user interfaces, intended users, use environments, use scenarios, use-related hazards, formative evaluations, summative evaluations, and usability engineering files. Assign accountable owners, identify applicable legal, customer, certification, or regulatory drivers, and agree how evidence will be governed.
Gap analysis and risk prioritisation
Assess current practices against IEC 62366-1 expectations and risk context. Review use specification, user interface characteristics, known use problems, hazard-related use scenarios, risk controls, formative evaluation, summative evaluation, residual use-related risk, and usability engineering file maintenance, then prioritize gaps by legal exposure, safety or consumer impact, customer impact, operational dependency, and review readiness.
Implement controls, records and reporting
Deploy required controls, operating processes, documentation, supplier or partner workflows, testing, reporting, and escalation paths. Build traceable evidence around use specifications, user profiles, task analyses, known-use-problem reviews, hazard-related use scenario records, formative study reports, summative validation reports, risk-control traceability, and usability engineering files.
Review, audit and keep current
Complete readiness reviews, internal checks, and corrective actions before the regulatory submission review or usability engineering audit. Refresh the program after product, service, supplier, technology, legal, market, incident, or regulator changes.
Compliance Checklist
checklist Scope and accountability
checklist Controls and evidence
checklist Monitoring and improvement
Penalties & Enforcement
No direct fines for non-compliance. However, inadequate usability engineering can lead to rejection of regulatory submissions (FDA 510(k)/PMA, EU MDR Technical Documentation), product recalls due to use errors, and liability exposure from patient harm caused by design-related use errors.
Frequently Asked Questions
Who needs IEC 62366-1?
expand_more
IEC 62366-1 is relevant for organizations whose products, services, systems, or regulated activities fall within medical device user interfaces, intended users, use environments, use scenarios, use-related hazards, formative evaluations, summative evaluations, and usability engineering files. It is commonly driven by regulation, customers, certification, market access, or assurance needs.
What is the main purpose of IEC 62366-1?
expand_more
The practical purpose is to create a repeatable program for use specification, user interface characteristics, known use problems, hazard-related use scenarios, risk controls, formative evaluation, summative evaluation, residual use-related risk, and usability engineering file maintenance. The program should make obligations visible, define accountable owners, operate controls, and keep evidence current.
What should be done first?
expand_more
Start by confirming scope, ownership, and applicable obligations. This prevents teams from building documents or controls that do not match the actual product, service, system, or regulated activity.
How long does implementation take?
expand_more
A focused implementation can take several weeks or months. Timing depends on maturity, number of sites or systems, supplier involvement, technical complexity, testing needs, and external review depth.
What evidence is most useful?
expand_more
Useful evidence includes use specifications, user profiles, task analyses, known-use-problem reviews, hazard-related use scenario records, formative study reports, summative validation reports, risk-control traceability, and usability engineering files. Reviewers usually expect traceable evidence that connects obligations to decisions, controls, tests, reports, and corrective actions.
How should suppliers or partners be managed?
expand_more
Supplier and partner duties should be documented through contracts, onboarding requirements, data or evidence requests, performance monitoring, and escalation routes for findings, incidents, or changes.
When should the program be updated?
expand_more
Update the program after legal changes, product or service changes, supplier changes, new markets, incidents, complaints, regulator feedback, or audit findings. Stale evidence is a common compliance failure.
Can this be integrated with other programs?
expand_more
Yes. IEC 62366-1 can usually share governance, document control, training, supplier management, issue tracking, risk management, internal review, and corrective-action workflows with adjacent compliance programs.
Official Documentation
Official PDF for IEC 62366-1:2015+AMD1:2020
Official publication or summary for IEC 62366-1:2015+AMD1:2020
Official online resource
International Electrotechnical Commission (IEC) guidance and reference material
Implementation toolkit
Templates, guidance, or companion resources for IEC 62366-1:2015+AMD1:2020