Integrating Design Controls with IEC 62366-1 Usability Engineering

Why Integration Matters

Both processes:

Start from intended use definition
Drive risk assessment
Require formal validation
Produce regulatory submission evidence
Need ongoing traceability

Treating them separately creates parallel documentation chains with significant duplication.

Integration Architecture

Shared Foundation: Intended Use Definition

Both processes start from a clear intended use statement:

Intended user
Use environment
Patient population
Indications and contraindications
Use scenarios

A single intended use document feeds both design controls and usability engineering.

Shared Inputs: User Needs and Use Requirements

Design Controls Input	Usability Engineering Input
User needs	Use specification
Performance requirements	Use scenarios
Safety requirements	Hazard-related use scenarios
Regulatory requirements	Applicable usability standards

Map user needs to use specification in a single requirements document.

Shared Risk Management

Both feed into ISO 14971 risk management:

Design controls identify design risks
Usability engineering identifies use-related risks
Combined risk assessment in single risk file

Integrated Workflow

Stage 1: Foundation (Project Initiation)

Define intended use, intended users, use environment
Identify regulatory pathway and applicable standards
Plan integrated design and usability process
Risk management plan covering both design and use risks

Stage 2: Design Inputs and Use Specification (Concept Phase)

Capture user needs in design input document
Develop use specification (IEC 62366-1)
Identify hazardous use scenarios
Cross-reference design inputs with use scenarios

Stage 3: Design Outputs and Use Interface Specification (Design Phase)

Design outputs documented per ISO 13485
User interface specification per IEC 62366-1
Risk control measures applied to design
Risk control measures applied to user interface

Stage 4: Formative Evaluations (Iterative Design Phase)

Formative usability studies (IEC 62366-1)
Design verification activities (ISO 13485)
Iterative refinement
Risk control verification

Stage 5: Summative Evaluation (Pre-Submission Phase)

Summative usability validation per IEC 62366-1
Design validation per ISO 13485
Validation includes use scenarios
Final risk-benefit analysis

Stage 6: Transfer and Documentation

Design transfer to manufacturing
Use-related training materials
Labeling and IFU reflecting usability findings
Integrated DHF (Design History File) includes usability files

Where Integration Saves Effort

Saving 1: Single User Needs Document

Without integration: User needs in design input doc + separate use specification.

With integration: Single document with cross-referenced sections.

Effort saved: 30–40 hours per project.

Saving 2: Combined Risk Assessment

Without integration: Design risk file + separate use-error risk file.

With integration: Single ISO 14971 risk file with design and use sections.

Effort saved: 40–80 hours per project.

Saving 3: Validation Activities

Without integration: Design validation + separate summative usability validation.

With integration: Design validation incorporates summative usability validation activities.

Effort saved: 50–150 hours per project.

Saving 4: Documentation Maintenance

Without integration: Changes require updates in design control records AND usability files.

With integration: Single update to integrated documentation.

Effort saved: 20–40% of post-launch design change effort.

Regulatory Submission Benefits

MFDS Submission

Korean STED Section 4 (Design and Manufacturing) and Section 6 (Clinical Evaluation, including usability) benefit from integration:

Cross-referenced design controls and usability files
Single use scenario list applied to safety analysis
Clearer benefit-risk justification

FDA 510(k)

FDA Section 14 (Performance Testing) includes usability validation. Integrated documentation:

Substantial equivalence comparison includes use scenarios
Performance testing maps to use specification
Risk management file unified

EU MDR

EU MDR Annex II requires both design and usability documentation. Integration:

Annex II Section 2 (Design and Manufacturing) and Section 6 (Risk Management) connected
Clinical Evaluation Report includes usability evidence
Post-market surveillance covers use-related issues

Common Integration Pitfalls

Pitfall 1: Usability Started Late

Design team treats usability as final-phase checkbox. Summative usability fails because design didn't account for use risks.

Fix: Usability engineering from concept phase, not pre-submission.

Pitfall 2: Separate Risk Files

Two risk files: one for design, one for use. Inconsistencies and missed hazards.

Fix: Single integrated ISO 14971 risk file.

Pitfall 3: Different Teams, No Communication

Design and usability teams work independently. Integration only at final review.

Fix: Cross-functional design team with usability practitioner embedded.

Pitfall 4: Documentation Duplication

User needs documented twice (design input + use specification). Updates inconsistent.

Fix: Single source of truth with cross-references.

Pitfall 5: Summative Usability Study Underpowered

Study with too few users to detect use errors. FDA, EU MDR, MFDS all flag inadequate sample size.

Fix: 15–25 users for summative studies, demographic representation.

When to Engage Usability Expertise

Project Phase	Usability Engagement Level
Concept	High (intended use, use scenarios)
Design inputs	High (use specification)
Detailed design	Medium (formative studies)
Verification	Medium (formative usability)
Validation	High (summative usability)
Transfer	Low (training materials)
Post-market	Medium (use-related complaints)

Frequently Asked Questions

Q: Is IEC 62366-1 mandatory for all medical devices?

A: For Class II+ devices in most jurisdictions, yes. EU MDR, FDA, and MFDS all expect IEC 62366-1 alignment. Class I devices have lighter usability requirements.

Q: Can our existing usability evaluation be reused for MFDS?

A: Largely yes. Summative usability validation conducted per IEC 62366-1 is recognized by MFDS. Add Korean clinical context discussion.

Q: How many users for summative usability study?

A: Minimum 15 users from each distinct user group. For Class III/IV devices, 25+ users recommended. Cover demographic and skill-level variation.

Q: Does usability evaluation require Korean users?

A: MFDS prefers Korean user evaluation but accepts foreign user studies with Korean context bridging analysis. For AI/ML devices with Korean-specific use considerations, Korean users may be required.

Q: Does Leanabl provide usability engineering services?

A: Yes. Leanabl's Usability Engineering service covers IEC 62366-1 implementation integrated with design controls.

How Leanabl Helps

Usability Engineering — IEC 62366-1 implementation
Discovery & Design — design controls integration
Korea Medical Device Registration — submission with integrated design/usability documentation

Contact Leanabl for design controls + usability integration.

Last updated: 2026-05-15.