Design Verification vs Validation — PatSnap Eureka
Design Verification vs. Design Validation in Medical Device Development
Two mandatory activities under ISO 13485 Section 7.3 — but they answer fundamentally different questions. Understanding the distinction is critical for quality management compliance and successful regulatory submissions.
Two Questions. Two Activities. One Compliant Device.
Under ISO 13485 Section 7.3, both design verification and design validation are mandatory components of the design and development lifecycle — but they serve entirely different purposes and occur at different stages.
Design verification asks: "Did we build the product right?" It confirms that design outputs meet the specified design inputs. This is an internal, specification-focused activity performed throughout development.
Design validation asks: "Did we build the right product?" It confirms that the finished device meets the intended use and the needs of the user. This is an externally-facing, user-focused activity performed on the final device — or a representative sample — under actual or simulated conditions of use.
A device can pass all verification activities and still fail validation if the original design inputs did not accurately capture what users actually need. This is why medical device quality management frameworks treat them as complementary — not interchangeable — assurances. Regulatory bodies including the US FDA and EU MDR authorities require documented evidence of both in every submission.
Design Verification vs. Design Validation: Key Differences Under ISO 13485
Six regulatory dimensions that distinguish these two mandatory design control activities.
| Dimension | Design Verification | Design Validation |
|---|---|---|
| Core question answered | Did we build the product right? | Did we build the right product? |
| Reference document | Design Inputs (specifications) | User Requirements / Intended Use |
| Timing in lifecycle | During development, at each design stage | On the final device or representative sample |
| Typical methods | Inspection, testing, analysis, review | Clinical evaluation, usability testing, real-world performance studies |
| Who is the reference? | The specification / design input document | The intended user and intended use |
| ISO 13485 record requirement | Verification plan, protocol, test reports, results, conclusions | Validation plan, protocol, results, conclusions — all in DHF |
Map your V&V activities to ISO 13485 requirements
PatSnap Eureka surfaces relevant patent filings and regulatory literature to support your design control documentation.
Where Verification and Validation Sit in the ISO 13485 Design Lifecycle
Visualising how V&V activities are distributed across the five phases of ISO 13485-compliant medical device development.
Design Control Activity Intensity by Development Phase
Verification activity peaks during output and prototype phases; validation is concentrated at the final device stage.
ISO 13485 Design History File: Required Record Types
The DHF must contain records from both verification and validation activities, alongside other design control documentation.
What Verification and Validation Actually Involve
Practical methods and documentation requirements for each activity under ISO 13485 Section 7.3.
Confirming Outputs Meet Inputs
Verification is performed by comparing design outputs against the design inputs that generated them. Typical methods include inspection, testing, analysis, and formal design review. Verification activities occur at each design stage — not just at the end — and must be planned in advance. Results are documented as objective evidence in the Design History File.
Objective evidence requiredConfirming the Device Meets User Needs
Validation is performed on the final device — or a representative sample — under actual or simulated conditions of use. It must demonstrate that the device meets the needs of the intended user and the intended use. Methods typically include clinical evaluation, usability testing, and real-world performance studies. Validation is the last gate before regulatory submission.
Final device requiredPlanning, Protocols, and Records
ISO 13485 Section 7.3 requires that both verification and validation activities be planned, documented, and retained as quality records. Required documentation includes plans, protocols, test reports, results, and a summary of conclusions. All records must be maintained as part of the Design History File (DHF) and made available for regulatory inspection by bodies such as the FDA.
DHF retention mandatoryPassing Verification, Failing Validation
A device can satisfy all specified design inputs (pass verification) yet still fail to meet actual user needs or intended use (fail validation). This typically occurs when design inputs were poorly defined, incomplete, or did not accurately capture user requirements. This is why both activities are mandatory under ISO 13485 — they provide complementary assurance that cannot substitute for each other.
Complementary — not interchangeableISO 13485, FDA QMSR, and the Global V&V Landscape
How design verification and validation requirements align across major regulatory frameworks.
ISO 13485 Section 7.3
The primary international standard for medical device quality management systems. Section 7.3 governs all design and development activities, requiring planned and documented verification and validation with retained objective evidence. Certification is recognised by regulators in over 100 countries.
FDA 21 CFR Part 820 & QMSR
The US FDA's Quality System Regulation aligns closely with ISO 13485 on design verification and validation requirements. The FDA's updated Quality Management System Regulation (QMSR), effective 2026, further harmonises with ISO 13485, making alignment between the two frameworks increasingly important for US market access.
The ISO 13485 Design Control Lifecycle
How design inputs, verification, and validation connect across the three phases of ISO 13485-compliant device development.
Design Verification vs. Validation — key questions answered
Design verification confirms that design outputs meet design inputs — it answers 'Did we build the product right?' Design validation confirms that the finished device meets the intended use and user needs — it answers 'Did we build the right product?' Both are required under ISO 13485 Section 7.3 but serve distinct purposes at different stages of the design lifecycle.
Design verification occurs after design outputs have been generated but before final validation. It is performed at each design stage to confirm that outputs meet the specified design inputs, typically using objective evidence such as inspection, testing, and analysis.
Design validation is performed on the final device — or a representative sample — under actual or simulated conditions of use. It must demonstrate that the device meets the needs of the intended user and the intended use, as defined in the user requirements. Validation typically involves clinical evaluation, usability testing, and real-world performance studies.
Yes. A device can satisfy all specified design inputs (pass verification) yet still fail to meet actual user needs or intended use (fail validation). This typically occurs when design inputs were poorly defined, incomplete, or did not accurately capture user requirements. This is why both activities are mandatory under ISO 13485 — they provide complementary assurance.
ISO 13485 Section 7.3 requires that both verification and validation activities be planned, documented, and retained as quality records. Required documentation includes verification and validation plans, protocols, test reports, results, and a summary of conclusions. All records must be maintained as part of the Design History File (DHF).
ISO 13485 and FDA 21 CFR Part 820 (the Quality System Regulation) share closely aligned requirements for design verification and validation. Both require planned and documented V&V activities, objective evidence of results, and retention of records. The FDA's updated Quality Management System Regulation (QMSR), effective 2026, further harmonises with ISO 13485, making alignment between the two frameworks increasingly important.
Still have questions about design controls? Let PatSnap Eureka answer them for you.
Ask Eureka About ISO 13485Accelerate Your ISO 13485 Design Control Compliance
Join 18,000+ innovators already using PatSnap Eureka to accelerate their R&D and navigate regulatory requirements with confidence.
References
- ISO 13485:2016 — Medical devices: Quality management systems — Requirements for regulatory purposes
- US FDA — Design Controls Guidance for Medical Device Manufacturers (21 CFR Part 820)
- US FDA — Quality Management System Regulation (QMSR) 2026 Harmonisation with ISO 13485
- International Medical Device Regulators Forum (IMDRF) — Global Harmonisation of Medical Device Regulatory Requirements
- European Union — Medical Device Regulation (EU MDR 2017/745) — Technical Documentation and Clinical Evaluation Requirements
- PatSnap — Life Sciences Innovation Intelligence Platform
All regulatory framework descriptions on this page are based on publicly available standards and guidance documents referenced above. Innovation intelligence powered by PatSnap's proprietary platform.
PatSnap Eureka searches patents and regulatory literature to answer instantly.