Design History File Explained: The DHF Under the QMSR

Design and development file binder and tablet showing a medical device design, with records linked from plan to release

Since 2 February 2026, 21 CFR Part 820 has been the Quality Management System Regulation (QMSR), incorporating ISO 13485:2016 by reference. The final rule was published on 2 February 2024. The former regulation required a design history file (DHF) for each type of device; the QMSR no longer uses the term.

The term has gone from the regulation, but the evidence FDA expects has not. This article covers what the former rule required, what replaced the DHF, what the file holds, how FDA inspects it, and where the equivalent evidence sits under the EU MDR.

What the former rule required

Under the former 21 CFR 820.30(j), "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" (former 21 CFR 820.30, historical text).

The activity paragraphs fed the file:

  • former 820.30(e) required design review results to be documented in the DHF;

  • former 820.30(f) required design verification results to be documented in the DHF;

  • former 820.30(g) required design validation results, including software validation and risk analysis where appropriate, to be documented in the DHF.

Design controls applied to class II and class III devices and to listed class I devices, including class I devices automated with computer software.

What replaced it

In its response to Comment 31 of the final rule, FDA explained that ISO 13485 has no DMR, DHF or DHR. FDA said it is "not retaining separate requirements" for these record types, because their elements are "largely required to be documented by ISO 13485, including Clause 4.2 and its subclauses, and Clause 7 and its subclauses".

In their place, FDA points to ISO 13485 Clause 7.3.10: "Clause 7.3.10 requires the design and development file to contain or reference all the records necessary to establish compliance with design and development requirements, including the design and development plan and design and development procedures." FDA describes this as "consistent with the former DHF".

Former QS record What it held Under the QMSR Source
DHF Records showing the design was developed in line with the approved design plan Design and development file (Clause 7.3.10) Final rule, Comment 31
DMR Device specifications and production procedures Medical device file (Clause 4.2.3) Final rule
DHR Production records for each batch or unit Largely the record required by Clause 7.5.1 Final rule

Source: QMSR final rule.

According to the final rule, the medical device file under Clause 4.2.3 contains or references current procedures and specifications, and the final design output kept in the design and development file "forms the basis or starting point for the MDF".

In our view, the change is mostly one of terminology. A DHF built as an index of controlled records moves to the QMSR more easily than a copied binder.

Who must comply

Under 21 CFR 820.10(c), class II and class III devices, and the class I devices listed in 820.10(c)(1) and table 1, including devices automated with computer software, must comply with ISO 13485 Clause 7.3 and its subclauses. For a class I device, check the table, not just the class.

Our article on the ISO 13485 quality management system covers the wider requirements.

What the file holds

Element What the record shows Source
Plan and procedures The design and development plan and procedures Clause 7.3.10, per the final rule
Design inputs The requirements the design must meet CP 7382.850
Design outputs The specifications the design is released against CP 7382.850
Design review Review results and actions Former 820.30(e); CP 7382.850
Verification Results showing outputs meet inputs Former 820.30(f); CP 7382.850
Validation Evidence the device meets user needs and intended uses Former 820.30(g); CP 7382.850
Software validation Validation of the device software Former 820.30(g); CP 7382.850
Design transfer Evidence the design was correctly translated into production specifications CP 7382.850
Change control Records of design changes CP 7382.850

Sources: FDA Compliance Program 7382.850; former 21 CFR 820.30 (historical).

For software, IEC 62304 life cycle documentation is typically referenced from the file rather than copied into it.

In our view, the design and development file and the medical device file should be built from the same controlled records, not maintained twice. The design file shows how the device was developed; the medical device file holds what is current.

Inspection

According to CP 7382.850, manufacturers designing under contract must "maintain or have reasonable accessibility to copies of a design and development file for each medical device type or medical device family".

Records created before 2 February 2026 remain relevant. According to the QMSR FAQ (Q7), investigators may review them, and FDA suggests a comparative analysis may be useful. Our article on 21 CFR Part 820 explains how the QMSR works.

EU technical documentation

Under the MDR, the comparable evidence sits in the technical documentation (Article 10(4); Annexes II and III). The MDR does not use the term DHF. Our article on SaMD technical documentation covers its structure for software.

A hypothetical example

Hypothetical example: a class II SaMD manufacturer for the US market has a DHF index built under the former 820.30(j).

  1. Rename: it renames the index the design and development file.

  2. Check: it confirms the file references the design and development plan and procedures (Clause 7.3.10).

  3. Split: it moves the current release specifications into the medical device file (Clause 4.2.3).

  4. Older records: it records a comparative analysis for records created before 2 February 2026 (QMSR FAQ Q7).

Conclusion

The DHF is no longer a QMSR term, but the design and development file under Clause 7.3.10 holds the same evidence. The final design output forms the starting point for the medical device file, and pre-2026 records remain open to review.

In our view, keep the file as an index of controlled records, check it references the plan and procedures, and build the US and EU evidence from one set of records.

If you need help aligning your design records with the QMSR, our management system team can help, or contact MedQAIR.

Frequently asked questions

Does the DHF still exist under the QMSR?

Not as a term. FDA is not retaining separate requirements for the DHF; the design and development file under ISO 13485 Clause 7.3.10 holds the equivalent records.

Must I rename my DHF?

The QMSR does not use the term. What matters is that the file contains or references all the records Clause 7.3.10 requires, including the plan and procedures.

What is the difference between the design and development file and the medical device file?

The design and development file records how the design was developed. The medical device file (Clause 4.2.3) contains or references current procedures and specifications, starting from the final design output.

Do class I software devices need a design and development file?

Class I devices listed in 820.10(c)(1) and table 1, including devices automated with computer software, must comply with Clause 7.3.

Will FDA look at design records created before 2 February 2026?

Yes, investigators may review them. FDA suggests a comparative analysis may be useful (QMSR FAQ Q7).

Does the MDR use the term design history file?

No. Under the MDR, the comparable evidence sits in the technical documentation (Article 10(4); Annexes II and III).

Latest Blogs

November 19, 2026

Since 2 February 2026, FDA's Quality Management System Regulation (21 CFR Part 820) has incorporated ISO 13485:2016 by reference. Even

November 18, 2026

Since 2 February 2026, 21 CFR Part 820 has been the Quality Management System Regulation (QMSR), incorporating ISO 13485:2016 by

November 17, 2026

The MDR has applied since 26 May 2021 and sets out the duties of importers in Article 13. MDCG 2021-27,

logo

Unlock Your Quick Guide to AI Act
Compliance!

Explore AI-enabled SaMD requirements with our easy step-by-step guide.

Cookies help us improve your experience on our website. By using our site, you consent to the use of cookies as described in this policy.