IEC 60601-1-6 is the collateral usability standard in the IEC 60601 family for medical electrical equipment. It requires manufacturers to apply a usability engineering process that identifies and reduces risks from use errors, and it points to IEC 62366-1 for the detailed method and the usability engineering file.
What is IEC 60601-1-6?
IEC 60601-1-6 is a collateral standard to IEC 60601-1, the base standard for basic safety and essential performance of medical electrical (ME) equipment. The “-1-6” naming marks it as a collateral standard that adds cross-cutting requirements to the general standard. Its subject is usability: how a device’s user interface design affects safe use.
The current edition, IEC 60601-1-6:2010, with later amendments, does not specify the full process. It normatively references IEC 62366-1, the usability engineering standard for medical devices, and directs manufacturers to apply that process to ME equipment, ensuring that usability is treated as part of basic safety and essential performance.
Why IEC 60601-1-6 matters in medical device development
Use error causes a large share of harm involving medical electrical equipment. A confusing alarm, an ambiguous control, or a misread display can lead to the wrong dose, a missed event, or a delayed response. IEC 60601-1-6 requires design teams to treat the user interface as a safety system rather than a cosmetic layer.
Regulators expect it. IEC 60601-1-6 is a recognized consensus standard under FDA’s program and is harmonized under the EU MDR (Regulation 2017/745) for many ME devices. Notified bodies and FDA reviewers look for evidence that the usability engineering process was followed and documented. Gaps here can stall a 510(k), a CE technical file, or an MDR conformity assessment.
The usability engineering file is also reviewable audit evidence. If it is thin or disconnected from your risk management file, an auditor will notice.
How IEC 60601-1-6 works
IEC 60601-1-6 sets the requirement; IEC 62366-1 supplies the method. Together, they define a usability engineering process that runs alongside risk management under ISO 14971. The main activities are:
Prepare a use specification.
Define intended users, use environments, and the intended medical purpose of the equipment.
Identify user interface characteristics related to safety, as well as the hazards and hazardous situations they can create.
Describe hazard-related use scenarios that could lead to harm, and select which ones to evaluate.
Establish the user interface specification and a usability evaluation plan.
Run formative evaluations during development to find and fix design problems early.
Run a summative evaluation to confirm representative users can operate the finished interface safely in realistic conditions.
Compile the usability engineering file, the record that ties all of this together.
The output feeds back into the risk management file required by ISO 14971 and connects to the general requirements of IEC 60601-1. For software-driven interfaces, the process also intersects with IEC 62304 (medical device software lifecycle) and IEC 81001-5-1 for security.
IEC 60601-1-6 applies to ME equipment and ME systems; IEC 62366-1 applies more broadly to medical devices, which is why the two are read together.
Common challenges and best practices
Teams most often go wrong by treating usability as a late-stage checkbox. Summative testing the week before submission rarely ends well; if the test surfaces a serious use error, you are redesigning under deadline.
A few patterns separate strong files from weak ones:
Start the use specification early and keep it aligned with the risk analysis.
The two documents should reference each other.
Recruit representative users for evaluations, not internal engineers who already know how the device works.
Define what counts as a successful task and an acceptable use error before testing, not after.
Document formative findings even when messy.
Reviewers want to see problems found and resolved, not testing that looks suspiciously clean.
Treat the summative study as a validation, not a demo: realistic environment, realistic tasks, defined acceptance criteria.
Editions matter too. The 2010 edition with amendments, paired with the current IEC 62366-1, is the set most programs work to. Confirm which editions your target market and notified body expect before building the plan.
How SJML helps with IEC 60601-1-6
SJML builds usability engineering into electromechanical device design rather than bolting it on at the end. Risk management to ISO 14971 and usability engineering to IEC 62366 are part of the standard design flow, along with user needs analysis, phase-gate reviews, and change control. In-house labs support IEC 60601 electrical safety and EMC testing, so interface work and safety testing stay connected. The QARA team handles technical files, design history files, and regulatory strategy for FDA, EU MDR, and other markets, keeping the usability engineering file aligned with submission requirements.
Talk to SJML’s engineering team →
Frequently asked questions
IEC 60601-1-6 is the collateral standard that requires a usability engineering process for medical electrical equipment. IEC 62366-1 is the standard that defines the process in detail. IEC 60601-1-6 references IEC 62366-1 rather than repeating it, so manufacturers of ME equipment generally apply both together.
It is not a law on its own, but regulators widely recognize it. FDA lists it as a consensus standard, and it is harmonized under the EU MDR for many medical electrical devices. In practice, following IEC 60601-1-6 is the expected way to show that usability risks were managed.
A usability engineering file is the documented record of the usability engineering process. It holds the use specification, identified hazards and use scenarios, the user interface specification, evaluation plans, and formative and summative test results. It serves as reviewable evidence for auditors and regulators, and it links to the ISO 14971 risk management file.
Yes, when software forms part of the user interface of medical electrical equipment. The process covers screens, alarms, and controls regardless of how they are built. For software devices, IEC 60601-1-6 is applied alongside IEC 62304 for the software lifecycle and, where relevant, IEC 81001-5-1 for security.
Related terms
IEC 62366-1 | ISO 14971 | IEC 60601-1 | Use Error | Human Factors Engineering
