DHF Self-Check
Score your Design History File against 21 CFR 820.30 and ISO 13485 design controls. "Not sure" scores as auditor exposure.
Design Controls Under FDA QMSR: What Has Changed
With FDA's final Quality Management System Regulation (QMSR), 21 CFR Part 820 incorporates by reference ISO 13485:2016. While the core philosophy of design controls remains consistent, audit focus has intensified around three specific interfaces:
1. Risk-Driven Design Verification Sample Sizes
Auditors increasingly demand quantitative justification for bench test sample sizes (ISO 13485 §7.3.6). Relying on arbitrary sample counts (such as "n=5" or "n=10") without documented statistical confidence and reliability levels tied to risk severity (ISO 14971) results in immediate verification non-conformances.
2. Independent Reviewer Independence
Under both 21 CFR 820.30(e) and ISO 13485 §7.3.5, design review meetings must include an individual who does not have direct responsibility for the design stage being reviewed. Design reviews signed exclusively by the core project team fail formal inspection scrutiny.
3. Design Transfer & DMR Interface
Design outputs are only complete when they form the verified baseline for the Device Master Record (DMR). Drawings, packaging specifications, and inspection procedures must be validated under production-scale conditions prior to commercial distribution.
Questions we get
Why does "Not sure" score as auditor exposure?
Under 21 CFR 820.30 and ISO 13485 §7.3, regulatory compliance requires demonstrable "objective evidence". If project engineers or quality personnel are unsure whether a formal protocol was pre-approved or whether an independent reviewer signed the review minutes, an auditor will find that the requirement was not established. In regulated audits, uncertainty equals exposure.
How does FDA's transition to QMSR affect Design History Files?
The FDA Quality Management System Regulation (QMSR) harmonizes 21 CFR 820 with ISO 13485:2016. While terminology aligns more closely with ISO (e.g., design and development files), the substantive expectations for design inputs, statistical verification sample sizes, and risk-management traceability remain rigorous and enforceable during inspections.
What is the most frequent 483 inspection observation regarding design controls?
Historically, the most cited design control deficiencies involve: (1) inadequate or unvalidated design inputs (ambiguous, non-testable requirements), (2) lack of design verification data tracing directly to inputs, and (3) missing independent reviewers on design review meeting minutes.
Does this self-check replace a formal regulatory gap analysis?
No. This is an internal heuristic triage tool designed to identify immediate procedural vulnerabilities. A formal gap analysis requires a qualified regulatory engineer to inspect every document, protocol, and trace matrix line-by-line.
Limited intake
Need an Independent DHF Gap Scan in 72 Hours?
Our regulatory engineering alliance provides scored, named-reviewer gap reports for Class II and III design history files.