ProcessDHF

Design History File

An FDA-mandated compilation of all records that demonstrate a medical device was designed in compliance with its approved design plan.

A Design History File (DHF) is a compilation of records that describes the design history of a finished medical device, as required by FDA 21 CFR Part 820.30 (Quality System Regulation) and ISO 13485:2016. The DHF must contain or reference all records necessary to demonstrate that the design was developed in accordance with the approved design plan. It is the audit trail that proves the product was developed through a controlled process that meets regulatory requirements.

A complete DHF contains: design and development planning records, design inputs (requirements), design outputs (specifications, drawings, BOMs), design review records, design verification records (testing showing outputs meet inputs), design validation records (testing showing the product meets user needs), design transfer records (evidence the design can be consistently manufactured), and design change records (ECOs). The DHF must be maintained for the life of the device plus the required record retention period.

The DHF is not only a regulatory requirement — it is a valuable engineering asset. When a device failure occurs in the field, the DHF enables root cause analysis by revealing what was known at each design stage, what was tested, what risks were identified but accepted, and what changes were made after initial release. DHFs have prevented costly recalls by enabling rapid determination of which device configurations are affected by a specific component failure.

Standard reference: FDA 21 CFR Part 820.30 'Design Controls'; ISO 13485:2016 Section 7.3 'Design and Development.'

Practical Example

A pulse oximeter DHF contains: user needs document, design inputs (17 functional requirements, 8 non-functional requirements), design outputs (schematic, PCB layout, housing drawings, BOM Rev D), V&V protocol and test report, software documentation (IEC 62304), 510(k) submission records, and design change history for 6 ECOs.

How SpecZero handles this

While SpecZero is not a regulatory-compliant DHF system, its requirements, decision log, timeline, and BOM structure capture the core elements of a DHF in a lightweight, accessible format during early-stage development. The structured data can inform formal DHF compilation in a qualified system.

Back to GlossaryTry SpecZero free