DHF containing or referencing all design control records from plan through transfer — 820.30(j) index-and-reference structure preserved as QMSR 820.10(c).
ISO 13485 7.3.10 design and development file requires risk management file integration and completeness review at design transfer — not explicit in Part 820.30(j).
DHF completeness verification at design transfer and risk management file integration — fragmented design records without a formal completeness gate are a recurring gap.
Maps to
QMSR / ISO 13485: §820.30(j) Design history file.
ISO 13485: §7.3 Design and development
Requirement text
A Design History File (DHF) must be established and maintained for each type of device. The DHF must contain or reference the records necessary to demonstrate that the design was developed in accordance with the approved design plan and applicable regulatory requirements.
Why this clause exists
The Design History File is the documentary record of the design process — not a description of the design, but the evidence that the design was developed following a defined plan through the required stages of inputs, outputs, review, verification, validation, and transfer. FDA introduced the DHF requirement in the original Part 820 specifically to create an auditable trail of design decision-making: inspectors needed a single, navigable compilation of design evidence rather than scattered records across multiple departments and systems. The DHF is inspectable because regulators understand that the design process is where patient safety is most directly determined — a device's safety and effectiveness properties are set during design, and the records that demonstrate those properties were established deliberately, reviewed by qualified personnel, and verified against requirements are the evidentiary foundation of every subsequent regulatory submission that relies on design data. The requirement that the DHF be maintained as a living document throughout development — not assembled retrospectively — reflects the regulatory finding that retrospectively assembled files tend to be selective: documents that document failures, design iterations, and resolved problems during development provide a more complete and honest record than those compiled after transfer when only successful outcomes remain. Risk management file integration as a DHF component reflects the QMSR's alignment with ISO 14971:2019: the design process is the primary mechanism for implementing risk controls, and the DHF must demonstrate that those controls were identified, implemented, and verified — not just that the product specifications were met.
What changed
§820.30(j) — Part 820 (legacy)
"Each manufacturer shall establish and maintain a DHF for each type of device. The DHF shall contain or reference the records necessary to demonstrate that the design was developed in accordance with the approved design plan and the requirements of this part."
§7.3.10 — ISO 13485:2016 (current)
"The organization shall maintain a design and development file for each medical device type or medical device family. This file shall include or reference records generated to demonstrate conformity to the requirements for design and development and records for design and development changes."
Δ File scope expands from device type to also cover medical device families; records must now cover design change history explicitly, not only conformity to the original design plan.
Common gaps (what we see in audits)
- DHF missing risk management file integration — Under QMSR, the design history must include or reference risk management records because ISO 13485 7.3.3 makes risk management outputs a design input. Many Part 820-era DHFs do not reference the risk management file, hazard analyses, or risk control traceability as part of the design history.
- No DHF completeness review at design transfer — ISO 13485 7.3.10 and good practice under the QMSR require that the DHF/DDF be verified for completeness — confirming all required records are present, approved, and retrievable — before or at the time of design transfer. Many companies compile the DHF retrospectively rather than verifying its completeness as a design transfer gate.
- DHF does not include records for expanded QMSR requirements — The QMSR's incorporation of ISO 13485 expands the scope of design control records beyond what Part 820 required. DHFs that met Part 820 may lack records for interface management, prior design references, usability evaluation, clinical evaluation, and manufacturing suitability verification — all now expected as part of the design history.
- Fragmented design records — Records of design changes or verification results are stored in personal drives or physical binders not referenced in a central 'DHF index.' ISO 13485 §7.3.10 requires the file to be maintained for each design.
- Missing legacy DHF for ISO-only systems — ISO-certified firms moving to the U.S. market often lack the 'DHF' structure, having only a 'DDF' that may miss earlier design iterations.