Electrical Safety, EMC, Usability and Connectors
IEC 62366-1: Usability Engineering for Medical Devices
IEC 62366-1 sets out a usability engineering process for medical devices. It applies to the user interface of any device, electrical or not, and focuses on use errors that could lead to harm. The output is a usability engineering file showing how use-related risks were found, addressed and evaluated with representative users.
At a Glance
- Standard
- IEC 62366-1
- Subject
- Usability Engineering for Medical Devices
- Group
- Electrical Safety, EMC, Usability and Connectors
- Industries
- 8 industry guides reference it
A plain-language summary of scope, not the standard itself. Buy the current edition from the publisher and check which edition your auditor or market expects.
What It Covers
The process starts with a use specification: the intended medical indication, patient population, user profiles, use environment and operating principle. From there the team identifies user interface characteristics related to safety, known and foreseeable hazards, and hazard-related use scenarios, which feed directly into the ISO 14971 risk analysis.
Design proceeds with a user interface specification and an evaluation plan. Formative evaluations during development explore the design and find problems while they're still cheap to fix. Summative evaluation at the end gathers objective evidence that the final user interface can be used safely, concentrating on the hazard-related use scenarios selected for it.
The standard also provides a route for user interfaces of unknown provenance, meaning existing designs that weren't developed under this process. For US submissions, FDA's own human factors guidance sets out its expectations, which overlap with the standard but aren't identical, so plan the work with both in view when the device is sold in the US.
Who It Applies To
- Any medical device with a user interface, including software, instruments, disposables and their labeling
- Devices used by patients, caregivers and other lay users as well as clinicians
- Software as a Medical Device and app-based devices where screens and workflows are the whole interface
- Design changes to the user interface, instructions for use or packaging
What Auditors Check
Use Specification
A use specification consistent with labeling, marketing claims and the risk management file.
Hazard-Related Use Scenarios
Identified scenarios linked to hazards in the risk file, with the rationale for which ones the summative evaluation covers.
Formative Evaluation Records
Evidence of formative work during design and what changed in the design because of it.
Summative Evaluation
A protocol and report with representative users and realistic conditions, analyzing use errors, close calls and difficulties down to root cause.
Labeling and Training as Risk Controls
Where instructions or training are relied on as a risk control, evidence they were evaluated and work for the intended users.
Usability File Upkeep
Updates to the usability engineering file after design changes and after post-market feedback about use errors.
Related Services
Submission Readiness (510(k), De Novo, PMA, Pre-Sub, 513(g))
The design, risk and V&V evidence behind a 510(k), De Novo or PMA, organized and gap-checked.
AI-Assisted QMS Gap Assessment
An AI-assisted first pass over the QMS documents you already have, with every result reviewed by an advisor.
QMS Build for Startups (Phased)
A QMS built in phases for a device startup: design controls and risk first, the rest before you need it.
Questions
Does IEC 62366-1 apply to devices that aren't electrical?
Yes. It applies to the user interface of medical devices generally, including disposables, instruments and software. IEC 60601-1-6 is the route for medical electrical equipment, but the process it points to is the same one in IEC 62366-1.
What's the difference between formative and summative evaluation?
Formative evaluation happens during design to explore ideas and find problems, and it can be iterative and informal. Summative evaluation is done on the final user interface to provide objective evidence that it can be used safely. Reviewers expect summative work to focus on the hazard-related use scenarios.
Can we rely on the instructions for use to control a use error?
Information for safety is a recognized risk control, but ISO 14971 ranks it after inherently safe design and protective measures. If you rely on it, the usability file should show the instructions were evaluated and actually work for your users.
How does this relate to FDA's human factors expectations?
They overlap heavily, and a well-run IEC 62366-1 process produces much of what FDA asks for. FDA's guidance has its own emphasis, including critical tasks and how validation results are reported, so check your plan against it before running summative testing for a US submission.
IEC 62366-1
Check Your Quality System Against IEC 62366-1
An AI-assisted first pass maps your existing documents against the requirements in scope, and an advisor reviews every result. Please don't send confidential documents yet: secure upload is set up after onboarding.
