> ## Documentation Index
> Fetch the complete documentation index at: https://docs.withdovetail.com/llms.txt
> Use this file to discover all available pages before exploring further.
# SOP Design Control
> Deploy systematic design control frameworks for safe and effective medical device development from concept to market.
## Summary
Your **Design Control** SOP establishes a systematic framework for medical device development from concept through post-market activities, ensuring that your device meets user needs, regulatory requirements, and safety standards through controlled design inputs, outputs, verification, validation, and transfer processes.
## Why is SOP Design Control important?
Design controls exist because regulators require **systematic evidence** that medical devices are designed safely and effectively before reaching patients. Without structured design controls, organizations risk developing devices that don't meet user needs, fail safety requirements, or cannot demonstrate regulatory compliance during submission reviews.
The SOP ensures **traceability and risk mitigation** by establishing clear phases, deliverables, and approval gates that connect user needs through design outputs to verification evidence. It transforms device development from an ad-hoc engineering exercise into a **regulated process** that builds confidence with regulators, customers, and internal stakeholders.
## Regulatory Context
Under **21 CFR Part 820** (Quality System Regulation):
* Design controls are **mandatory** under Section 820.30 for Class II and III devices
* Must establish procedures for **design inputs, outputs, review, verification, validation, transfer, and changes**
* Design History File (DHF) must be **maintained** with evidence of design control compliance
* Each design phase must have **appropriate approvals** before proceeding
**Special attention required for:**
* Software medical devices require special design control considerations
* Design verification vs. validation distinction (820.30(f) vs 820.30(g))
* Design transfer requirements (820.30(h)) before production
* Design change control (820.30(i)) for post-market modifications
Under **EU MDR 2017/745**:
* Design controls required as part of **quality management system** (Article 10(9))
* Must comply with **EN ISO 13485:2016** design and development requirements (Section 7.3)
* Risk management must be **integrated** throughout design process (Article 10(2))
* Technical documentation must demonstrate **design control compliance** (Annex II)
**Special attention required for:**
* Clinical evaluation integration throughout design process (Article 61)
* Post-market surveillance planning during design (Articles 83-86)
* Essential requirements compliance demonstration (Annex I)
* Notified body involvement for higher-risk devices
## Guide
Your Design Control SOP establishes the **systematic approach** to device development that regulators expect. Structure the process in clear phases with defined inputs, outputs, and decision points.
### Phase 1: Planning and Design Inputs
Begin with **comprehensive planning** that defines project scope, timeline, resources, and responsibilities. This phase is critical because poor planning leads to scope creep, timeline delays, and incomplete requirements capture.
Gather **complete design inputs** including user needs, intended use specifications, regulatory requirements, applicable standards, and performance requirements. Ensure inputs are complete, unambiguous, and verifiable. Incomplete or vague design inputs lead to design outputs that cannot be properly verified.
Conduct thorough **risk analysis planning** early to identify potential hazards and establish risk management strategy. Early risk identification enables proactive design decisions rather than reactive corrections later in development.
### Phase 2: Design Development and Outputs
Develop **detailed design outputs** that directly address each design input. Outputs should include specifications, drawings, software architecture, procedures, and any other documentation needed to manufacture and test the device.
Ensure **traceability** between design inputs and outputs through systematic documentation. Each design input should map to specific design outputs, and each output should trace back to inputs. This traceability is critical for regulatory submissions and audits.
Implement **design transfer planning** early to ensure manufacturing feasibility. Consider how design outputs will translate into manufacturing procedures, quality controls, and commercial production capabilities.
### Phase 3: Verification and Validation
Conduct **design verification** to confirm that design outputs meet design inputs. This typically involves testing against specifications, requirements verification, and objective measurement against predetermined criteria.
Perform **design validation** to confirm the device meets user needs and intended use in realistic conditions. Validation often involves clinical studies, usability testing, or real-world performance evaluation with actual users.
Execute **risk management verification** to confirm that risk controls are effective and residual risks are acceptable. This includes verification of risk control measures and validation of overall risk management effectiveness.
### Phase 4: Design Transfer and Release
Complete **design transfer** to manufacturing by ensuring production processes can consistently produce devices meeting design specifications. This includes process validation, manufacturing procedure development, and quality control establishment.
Conduct **market release activities** including regulatory submission preparation, post-market surveillance planning, and commercial readiness verification. Ensure all regulatory requirements are met before commercial distribution.
Establish **post-market monitoring** procedures to collect performance data and identify potential issues requiring design changes or safety updates.
### Integration with Other QMS Processes
Connect design control outputs to **risk management, verification and validation, change control, and post-market surveillance** processes. Design controls should not operate in isolation but integrate with your broader quality management system.
## Example
### Scenario
MedDevice Corp develops a wearable glucose monitoring system for diabetes management. They implement design controls to systematically progress from user needs identification through regulatory clearance and commercial launch while ensuring safety and effectiveness throughout the process.
### Example Design Control Implementation
**Phase 1: Planning and Inputs**
* **User Needs:** "Patients need continuous glucose monitoring without finger pricks"
* **Design Inputs:** Accuracy ±15%, 14-day wear time, waterproof to 1 meter, smartphone connectivity
* **Regulatory Strategy:** FDA 510(k) submission with predicate device comparison
* **Risk Management Plan:** Risk assessment covering sensor accuracy, skin irritation, data security
**Phase 2: Design and Development**
* **Design Outputs:** Sensor specifications, algorithm requirements, mobile app design, packaging design
* **Traceability Matrix:** Links each design input to specific outputs and verification methods
* **Supplier Management:** Qualify sensor component suppliers and adhesive manufacturers
* **Design Transfer Plan:** Manufacturing process definition and quality control procedures
**Phase 3: Verification and Validation**
* **Verification Testing:** Laboratory accuracy testing, environmental conditioning, electromagnetic compatibility
* **Validation Studies:** Clinical accuracy study with 100 diabetic patients over 14 days
* **Usability Validation:** Human factors testing with intended users in simulated home environment
* **Risk Control Verification:** Confirm sensor alarm functionality and data encryption effectiveness
**Phase 4: Transfer and Release**
* **Manufacturing Validation:** Process validation at contract manufacturer facility
* **510(k) Submission:** FDA submission with verification and validation evidence
* **Commercial Readiness:** Post-market surveillance procedures, customer support training
* **Market Launch:** Product registration in GUDID database with assigned UDI
**Phase 5: Post-Market Activities**
* **Performance Monitoring:** Customer complaint analysis and adverse event reporting
* **Design Change Control:** Systematic evaluation of proposed improvements or issue corrections
* **Continuous Improvement:** Annual design review incorporating post-market data
## Q\&A
Design changes after market release must follow systematic change control procedures that evaluate the impact on safety, effectiveness, and regulatory status. Major changes may require new regulatory submissions, while minor changes may only need internal documentation. All changes should be evaluated through your risk management process.
Design verification confirms that design outputs meet design inputs - essentially "did we build it right?" Validation confirms that the device meets user needs and intended use - "did we build the right thing?" Both are required but address different aspects of design assurance.
Software medical devices require special consideration in design controls, including software lifecycle processes, risk management for software, cybersecurity considerations, and appropriate verification and validation methods. Follow IEC 62304 for software lifecycle processes within your design control framework.
Design reviews should be conducted at key milestones throughout the design process, typically at the end of each phase before proceeding to the next. Reviews should include appropriate stakeholders and document decisions, action items, and approval to proceed.
Risk management should be integrated throughout all design control phases, starting with hazard identification in planning, continuing through risk control implementation in design development, and concluding with risk control verification and post-market risk monitoring.
The Design History File should contain all documentation demonstrating compliance with design control requirements, including design inputs, outputs, review records, verification and validation protocols and reports, design transfer documentation, and design change records.