DHFDesign History File
The Design History File is familiar industry terminology for medical-device design evidence. Distinguish current QMSR design-and-development requirements from the historical DHF definition in former §820.30(j).
On this page · 13 sections
- 1What a Design History File actually is
- 2What former QSR 21 CFR §820.30 actually requires
- 3Design inputs, design outputs, and the traceability matrix
- 4Verification, validation — and why they are not the same thing
- 5Risk management — the ISO 14971 layer the DHF must integrate
- 6Design reviews — the formal milestones inspectors look for
- 7Design transfer — where the DHF produces the DMR
- 8Design changes — the rule that keeps the DHF live
- 9Eight ways DHFs fail audit
- 10Frequently Asked Questions
- 11IEC 62304 and the software-in-DHF overlay
- 12Post-market surveillance feeding the DHF
- 13The QMSR transition — what changes for the DHF in 2026
How does DHF apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What a Design History File actually is
A Design History File (DHF) is the compilation of records that describes the design history of a finished medical device. It includes every record produced during design and development — the design inputs, the design outputs, the design reviews, the verification and validation records, the design changes, and the design transfer evidence. The DHF answers the question 'how was this device designed, and how do we know the design satisfies the user's needs and the intended use?'.
DHF is familiar industry terminology, not a named file requirement in current Part 820. Current 21 CFR 820.10(c) establishes the applicable design-and-development scope through ISO 13485 clause 7.3 and its subclauses. Preserve historical DHF records and map their contents to current requirements rather than treating a folder rename as compliance.
02What former QSR 21 CFR §820.30 actually requires
former QSR §820.30 has eleven sub-paragraphs covering the entire design-control framework. The DHF (subparagraph j) is the file in which the evidence accumulates; the other sub-paragraphs define the activities whose evidence ends up in the DHF.
- former QSR §820.30(a) — General. Scope of design controls.
- former QSR §820.30(b) — Design and development planning. The plan that governs the activity.
- former QSR §820.30(c) — Design input. The user needs and intended uses translated into requirements.
- former QSR §820.30(d) — Design output. The specifications that emerge from design.
- former QSR §820.30(e) — Design review. Formal documented reviews of the design results.
- former QSR §820.30(f) — Design verification. Confirmation that design output meets design input.
- former QSR §820.30(g) — Design validation. Confirmation that the device meets user needs and intended uses.
- former QSR §820.30(h) — Design transfer. Translation of the design into production specifications (the DMR).
- former QSR §820.30(i) — Design changes. Identification, documentation, validation and approval of changes.
- former QSR §820.30(j) — Design history file. The compilation of all the above.
The DHF is not itself a procedure; it is a file whose contents are produced by the procedures defined under former QSR §820.30(b) through (i). A manufacturer with a DHF that is just a folder of unsigned drafts has, in effect, no design controls — the procedures the DHF should evidence have not been performed.
03Design inputs, design outputs, and the traceability matrix
Design inputs (former QSR §820.30(c)) are the physical and performance requirements of the device. They include the user needs, the intended use, the regulatory requirements, and the standards the device must meet. Inputs must be documented, reviewed, approved by a designated individual, and traceable through the rest of the design process. Ambiguous or incomplete inputs are the most cited former QSR §820.30 finding.
Design outputs (former QSR §820.30(d)) are the specifications produced from the inputs. They include drawings, source code, formulations, work instructions, acceptance criteria, packaging specifications, and labelling. Outputs must be expressed in terms that allow adequate evaluation of conformance to design input requirements. Each output must trace back to one or more inputs; this is the traceability matrix.
The traceability matrix is the spine of the DHF. It shows, for every input, which outputs satisfy it; for every output, which verification activity confirmed it; and for every input, which validation activity confirmed the design as a whole satisfies the user need. An inspector asks for the traceability matrix early; a missing or partial matrix is the strongest signal that the design controls are weak.
04Verification, validation — and why they are not the same thing
Verification (former QSR §820.30(f)) confirms that the design output meets the design input. Did we build the device right? Verification answers this with bench testing, software unit and integration testing, dimensional inspection, biocompatibility testing, sterilisation validation, and so on. Each verification activity must reference the design output under test, the acceptance criteria from the design input, the method, the results, and the signature of the responsible person.
Validation (former QSR §820.30(g)) confirms that the device meets the user need and intended use under actual or simulated use conditions. Did we build the right device? Validation typically includes summative usability testing, human factors validation per IEC 62366-1, simulated-use testing, and (where appropriate) clinical evaluation. Validation must be performed on initial production units, units produced under equivalent conditions, or under controlled conditions per former QSR §820.30(g).
05Risk management — the ISO 14971 layer the DHF must integrate
Risk-management evidence can be linked to design inputs, risk controls and verification records through the design file. Current Part 820 incorporates ISO 13485:2016 and selected ISO 9000:2015 terms; it does not incorporate ISO 14971:2019 as a separate standard by reference. Determine applicable risk-management obligations and evidence using the actual sources.
Risk controls become design outputs. A risk control measure such as 'redundant occlusion alarm' becomes a design output (the alarm specification) which traces back through the design input chain to the hazard (occlusion) it controls. The traceability matrix is therefore three-dimensional in practice: inputs ↔ outputs ↔ risks.
06Design reviews — the formal milestones inspectors look for
former QSR §820.30(e) requires formal documented reviews of the design results at appropriate stages of the device's design development. 'Appropriate stages' is deliberately vague — the design plan defines them. Typical stages are inputs-approved, outputs-approved, verification-complete, validation-complete and design-transfer-complete. At each review, the participants, the date, the design under review, the issues identified and the actions assigned must be documented and the document signed by the participants.
Each review must include 'an individual(s) who does not have direct responsibility for the design stage being reviewed' (former QSR §820.30(e)). The independent reviewer is the equivalent of the second person on a Part 211 approval — they bring a perspective the immediate design team cannot. Inspectors verify the independent reviewer's signature by their role and reporting line.
07Design transfer — where the DHF produces the DMR
Design transfer (former QSR §820.30(h)) is the bridge between the DHF and the DMR. The procedure must ensure that the device design is correctly translated into production specifications. Practically, design transfer is the formal handover from the design team to the manufacturing team, and the artefact it produces is the initial released version of the DMR.
Transfer is not a single event — most modern programmes use a staged transfer (pilot, scale-up, full production) with formal sign-offs at each stage. The DHF holds the evidence of each transfer milestone; the DMR holds the released production specifications that emerged from them. After design transfer is complete, the DMR becomes the production system of record; the DHF continues to live, but is updated only on design changes.
08Design changes — the rule that keeps the DHF live
former QSR §820.30(i) requires the manufacturer to establish procedures for the identification, documentation, validation or verification, review, and approval of design changes before their implementation. Every change to a released design must be documented in the DHF as a design change record, must be reviewed and approved with the same rigour as the original design, and must be evaluated for impact on previously released devices.
Design changes interlock with change control on the DMR (former QSR §820.40) and on the production process (former QSR §820.70). A change to a design output that lives in the DMR has to update the DMR; if the change affects the production process it has to go through process change control; and if the change affects regulatory clearance (a 510(k) device whose modifications might require a new submission) it triggers a 21 CFR 807.81(a)(3) evaluation.
09Eight ways DHFs fail audit
- DHF is a folder of unsigned drafts — the design-control procedures were not performed, only their outputs were collected.
- Traceability matrix is missing or incomplete — inputs and outputs cannot be tied, former QSR §820.30(c)/(d) finding.
- Design validation performed on engineering units rather than production-equivalent units — former QSR §820.30(g) finding.
- Independent design reviewer is the same person as the design lead — former QSR §820.30(e) independence broken.
- Risk management activities recorded in a separate file with no DHF cross-reference — ISO 14971 integration broken.
- Design transfer happened informally — no transfer record, no first-released DMR version, no formal handover.
- Design changes recorded against the DMR but not against the DHF — the DHF becomes a stale snapshot of the initial design.
- Software design records (architecture, unit tests, integration tests) maintained outside the DHF — IEC 62304 integration broken.
10Frequently Asked Questions
See below for the regulator-grade answers to the questions buyers ask most often when scoping their DHF programme.
11IEC 62304 and the software-in-DHF overlay
For any device that contains software — and that is now the overwhelming majority of new market entries — the DHF must reference a parallel IEC 62304 software lifecycle file. IEC 62304:2006/A1:2015 (and the in-progress 2nd Edition) classifies software components by safety class (A, B, C) and prescribes the lifecycle deliverables accordingly. The DHF is incomplete unless every software item it references has a current, signed lifecycle record.
- Software safety classification per item, with rationale documented and reviewed by the design authority.
- Software Development Plan (SDP) — process, deliverables, tooling, configuration management, problem-resolution process.
- Software Requirements Specification (SRS) — derived from system requirements and risk-control measures; class C software requires a more granular SRS than class A.
- Software Architecture (class B+) and Detailed Design (class C only).
- Unit, integration and system test evidence with traceability to requirements and risk-control measures.
- Software configuration management records: every released build identifiable by version, source tagged in version control, build reproducible from tag.
- Software problem-resolution records: every defect found post-release tracked to root cause, fix, regression test, and risk-management update.
The DHF does not need to physically contain the software lifecycle records — they typically live in a software ALM such as Polarion, Jama or Codebeamer, or in a well-disciplined Git repository with linked issue tracker. What the DHF must contain is the explicit reference to those records, their location, their version state at design transfer, and the change-control link that keeps the DHF reference current as the software evolves.
12Post-market surveillance feeding the DHF
A DHF that stops being updated after design transfer is a DHF that fails audit within the first product-lifecycle cycle. former QSR §820.30(j) makes the DHF a living artefact for the life of the device. ISO 13485 §7.3.10 and EU MDR Articles 83–86 close the loop explicitly: post-market surveillance findings must flow back into design and the DHF must reflect every iteration.
- Complaint trending: complaints classified by failure mode, plotted against time, and reviewed quarterly by the design authority. Statistical signals (a complaint rate per UDI-DI exceeding the threshold) trigger a formal review.
- MDR / vigilance event review: every reportable adverse event is reviewed for design implications. If the root cause maps to a design input, the DHF is updated with a design-change record.
- PMCF / clinical follow-up: post-market clinical follow-up data (mandatory for class IIa+ under EU MDR) is summarised in the PSUR/PMCF Evaluation Report and referenced from the DHF.
- Field-experience design reviews: at least annually for class II+, a structured design review walks the cumulative field experience against the original design inputs. Outcomes are minuted and stored in the DHF.
- CAPA-driven design changes: every CAPA whose corrective action includes a design change generates a DHF entry, with the CAPA reference and the verification/validation evidence for the change.
- EUDAMED upload synchronisation: any DHF design-change record that affects the UDI-DI requires a corresponding EUDAMED update. The DHF carries the EUDAMED submission reference.
The DHF and the post-market surveillance file are two ends of a single feedback loop. Treating them as separate ring binders is the most common cause of EU MDR Notified Body findings. In V5, design changes and CAPAs share a unified workflow so that a CAPA whose corrective action is a design change automatically generates the DHF update task with the change-control gating intact.
13The QMSR transition — what changes for the DHF in 2026
Since 2 February 2026, FDA’s current QMSR incorporates ISO 13485:2016. Current 21 CFR 820.10(c) requires class II, class III and the listed class I device manufacturers to comply with ISO 13485 clause 7.3 and its subclauses. Former QSR §820.30 is historical, not current law. Apply current record controls through the applicable incorporated requirements and 21 CFR 820.35; detailed ISO provisions require the actual standard, not its publication landing page.
Preserve historical DHF identifiers, approvals and design-change history. Map evidence by its purpose and content to the current quality system. Do not assume identical clause wording, mandatory renaming, a merely cosmetic transition or automatic ISO 14971 incorporation.
Frequently asked questions
Q.Is the DHF the same as a Technical File or Technical Documentation under EU MDR?+
No, but they overlap. The DHF is the US (former QSR 21 CFR §820.30(j)) design-history compilation. The Technical Documentation under EU MDR Annex II / III is the conformity-assessment file submitted to the Notified Body. Most of the DHF content is reusable in the Technical Documentation, but the Technical Documentation has additional elements (clinical evaluation report, post-market surveillance plan) that go beyond the DHF.
Q.Does design transfer mean the DHF is frozen?+
No. The DHF is updated for the life of the device. Every design change creates an entry in the DHF, with verification and validation evidence attached. A DHF that has not been updated since initial transfer either means there have been no design changes (rare) or that the change-control procedure is not feeding the DHF.
Q.Who is the 'designated individual' who approves design inputs?+
former QSR §820.30(c) requires design inputs to be reviewed and approved by a designated individual. The QMS defines who that is — typically a design authority, a chief engineer, or a head of product. The same person should not also be the independent reviewer at former QSR §820.30(e); independence is the entire point.
Q.Are software design records part of the DHF?+
Yes. For software-as-a-medical-device (SaMD) and for software in a medical device (SiMD), the IEC 62304 lifecycle records (software development plan, requirements, architecture, detailed design, unit tests, integration tests, system tests, risk management file) are part of the DHF. They may be physically held in source control or a software ALM, but they are referenced from the DHF.
Q.Does the QMSR remove the DHF requirement?+
The named DHF definition and former §820.30(j) were removed from Part 820. Applicable design-and-development and record obligations continue under the QMSR. Retaining the internal DHF name does not establish completeness; map the actual evidence to current requirements.
Q.How long must the DHF be retained?+
Assess retention against the applicable current QMSR, incorporated record requirements and relevant market obligations. Former §820.180 was a historical QSR provision, not a retained current section. Preserve original evidence, versions and approvals for the applicable period; a familiar file name does not determine the duration.
Q.Does the DHF need to be a single document or system?+
No — and rarely is. The DHF is a compilation: it can be a binder, a folder structure in an eQMS, an index file pointing to source records in multiple systems (PLM, ALM, regulatory archive). What matters is the index, the version control on every referenced item, and the ability to reproduce the design state at any historical point.
Q.How does the DHF interact with the Design Master Record / DMR?+
DHF describes design evidence; DMR describes approved production specifications; DHR describes actual production history. These familiar industry names originated in former QSR provisions and are not three current named Part 820 mandates. Keep the evidence relationships controlled and map them to applicable QMSR requirements.
Primary sources
- eCFR — current 21 CFR 820.10, 820.35 and 820.45
- FDA — current QMSR overview and inspection approach
- FDA — current QMSR frequently asked questions
- 21 CFR 820.30 — Design controls (eCFR)
- FDA Design Control Guidance for Medical Device Manufacturers (1997, historical guidance)
- ISO 13485:2016 clause 7.3 — Design and development
- ISO 14971:2019 — Application of risk management to medical devices
- IEC 62366-1 — Application of usability engineering
Further reading
- Medical Device Design TransferProduction specifications, readiness responsibilities and acceptance evidence.
- FDA QMSRCurrent regulatory-framework reference.
- Medical-Device eDHR SoftwareCommercial production-record software evaluation.
- How V5 runs in medical-device manufacturingEnd-to-end workflow walk-through from design transfer to UDI release.
- DHR — Device History RecordThe per-build evidence file the DHF eventually transfers into.
- DMR — Device Master RecordThe master that the DHF produces at design transfer.
- ISO 13485The QMS standard whose 7.3 clause parallels former QSR §820.30.
- UDIThe identifier system the DHF must define.
Explore this topic
DHF sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
Master and executed records that prove a batch or device was made to spec.
Device-specific rules, submissions and the standards that bind them.
Want to see how DHF could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
