Usability Engineering Process: User Research to Validation
The EN 62366-1 usability engineering process end to end, from use specification through summative evaluation to the usability engineering file.
54 in-depth guides in this cluster
The EN 62366-1 usability engineering process end to end, from use specification through summative evaluation to the usability engineering file.
What a usability engineering file must contain under MDR and EN 62366-1, from use specification to summative report. A living document, not static.
The MDR use specification under EN 62366 is the most-skipped document. Decompose every procedure to make use-related hazards visible.
How to recruit usability test participants for medical devices under EN 62366-1, and why engineers and friendly KOLs are not intended users.
How to write a usability test protocol that survives notified body review under EN 62366-1, covering objectives, tasks, success criteria, and data capture.
How to turn raw usability observations into root-caused use errors, design changes, and risk file updates under EN 62366-1 and EN ISO 14971.
MDR Annex I requires medical electrical equipment to be safe. EN 60601-1 is the harmonised standard that gives you presumption of conformity. Here is how it fits together.
EN 60601-1 has accumulated amendments through A1, A12, A2, A13, sometimes called Edition 3.2. Here are the changes that matter for startups.
MDR Article 8 lets harmonised standards demonstrate presumption of conformity. Here is how that mechanism works for electrical safety via EN 60601-1.
Basic safety and essential performance are the two core concepts of EN 60601-1. Here is what they mean and how they map to MDR Annex I.
Electrical safety testing under EN 60601-1 is done at a certified test lab. Here is what a startup should know before booking the lab.
The EN 60601-1 test lab process is structured but unfamiliar to most startup founders. Here is what to expect from booking to certificate.
EN 60601-1 defines Means of Protection (MOP) against electrical hazards. Here is what MOPP and MOOP mean and how to design for both.
EN 60601-1 includes mechanical safety requirements, stability, enclosures, moving parts. Here is how they map to MDR Annex I and what testing looks like.
MDR thermal safety using EN 60601-1 temperature limits: applied parts, hot surfaces, heat-balance, and what a test lab actually measures for burns protection.
PEMS sit at the intersection of EN 60601-1 and EN 62304. Here is how the two standards combine for programmable electrical medical systems under MDR.
MDR Annex I requires medical electrical devices to be electromagnetically compatible. EN 60601-1-2:2015+A1:2021 is the harmonised standard. Here is what it means in practice.
EN 60601-1-2 defines EMC testing for medical devices: emissions limits and immunity levels. Here is the practical scope of EMC testing for startups.
Design choices that prevent EMC failures in medical devices: PCB layout, shielding, grounding, cables, and pre-test prep aligned to MDR Annex I §14.5.
How EN 60601-1-6 cross-references EN 62366-1 for medical electrical equipment, and what a single usability file must contain under MDR.
How EN 60601-1-8 defines alarm priorities, audio and visual signals, and distributed alarms for MDR-compliant medical electrical equipment.
EN 60601-1-9 applies environmentally conscious design to medical devices. Lifecycle impact, design choices, and evidence for the MDR technical file.
EN 60601-1-10 governs closed-loop controllers in medical devices. Lifecycle activities, validation, failure-mode analysis for MDR compliance.
How EN 60601-1-11 extends EN 60601-1 for home use devices under MDR, lay users, mains variability, IFU obligations, PMS implications.
How EN 60601-1-12 extends EN 60601-1 for EMS, ambulance, field and air-ambulance devices under MDR, ruggedization, EMC, battery autonomy.
How the EN 60601-2-xx particular standards work under MDR, how to find the right one for your device, and how conflicts with EN 60601-1 are resolved.
When functional safety concepts from IEC 61508 and IEC 62443 add value to MDR medical device development, and what you cannot claim about them.
How EN 60601-1 shapes medical power supply design: isolation classes, leakage limits, and qualifying COTS medical-grade supplies for the technical file.
Battery selection, charging, thermal runaway, BMS design, and transport for portable medical devices under MDR and EN 60601-1.
Wireless medical devices must meet both MDR and Radio Equipment Directive 2014/53/EU. Here is how to plan the dual-compliance path without surprises.
Packaging is a regulated component of the medical device. Here is what MDR Annex I and the EN ISO 11607 series actually require, and how to pass audit.
MDR Annex I §17.1 requires devices to work under foreseeable environmental conditions. Here is how to plan climate, vibration, and drop testing early.
How startups can apply a lean systems engineering V-model to medical device development under MDR and EN ISO 13485 without drowning in paperwork.
How to write, manage and trace system requirements for medical devices under MDR and EN ISO 13485 clause 7.3.3, from GSPR to verifiable specifications.
What a system architecture document must contain for a medical device under MDR Annex II, including hardware/software boundaries and safety segregation.
System integration and verification testing for medical devices under MDR: plan, traceability, evidence, and handling failures the auditor will accept.
Hardware development and PCB design for medical devices under MDR: safety and EMC decisions, schematic and BOM control, and evidence auditors request.
Firmware for medical devices under EN 62304 and EN 60601-1: hardware abstraction, real-time constraints, and joint hardware and firmware verification.
Realistic cost ranges for EN 60601-1 and EN 60601-1-2 testing under MDR. Categories, drivers, and where startups can save without cutting corners.
The eight most common EN 60601-1 test failures in MedTech startup labs, each with the test that caught it and the design fix.
A startup-sized electrical safety checklist against EN 60601-1 and EN 60601-1-2, prioritized by risk of failure and mapped to MDR Annex I.
Why MDR cybersecurity is continuous, not one-time. EN IEC 81001-5-1 lifecycle activities, CVE handling, and the Subtract to Ship minimum viable setup.
Mapping EN IEC 81001-5-1:2022 activities onto MDR Annex I §17 obligations. The harmonised cybersecurity route for health software under MDR.
A cybersecurity risk assessment that lives inside the EN ISO 14971 risk file. Threat, asset, vulnerability flow and the minimum viable template for MDR.
How GDPR Article 25 privacy by design and by default maps onto MDR design controls, turning data minimisation into a concrete medical device constraint.
How to choose and qualify AWS, Azure, or GCP for a medical device under MDR, GDPR, and the shared responsibility model, with EU residency in mind.
Why IoT and IoMT medical devices need a dedicated cybersecurity lifecycle and why 'not connected' is rarely a complete defence under MDR Annex I.
IVDR performance evaluation replaces MDR clinical evaluation for IVDs. Scientific validity, analytical performance, clinical performance explained.
IVDR clinical performance studies: when they are required, study design, ethics approval, sample sizes, endpoints, applicable standards.
The three pillars of IVDR performance evaluation: scientific validity, analytical performance, clinical performance. Each builds on the previous.
DiGA approval is not CE marking. DiGA MDR CE marking BfArM explained: two regulatory paths, two evidence bars, one product.
DiGA startup qualify criteria, honestly explained. Four gates, one CE mark, and the evidence bar Tibor says founders underestimate.
DiGA evidence positive care effects, explained honestly. Beyond MDR Article 61: what BfArM expects, and why founders underestimate it.
When in-house testing is acceptable under MDR and when an ISO/IEC 17025 accredited lab is effectively mandatory for startup evidence.