Skip to main content
Matrix One>Blog>Design History File (DHF) for Medical Devices: FDA and MDR Compliance

Design History File (DHF) for Medical Devices: FDA and MDR Compliance

Last updated on

Design history file (DHF) for medical devices: Short answer: a DHF is the compilation of records that proves a device design was developed according to its approved design plan, from inputs and outputs through reviews, verification, validation, transfer and changes. Since 2 February 2026 the FDA QMSR no longer uses the term: 21 CFR 820.30 is reserved, and the same records are the design and development file of ISO 13485:2016 clause 7.3.10, which the EU MDR summarises in its Annex II technical documentation. Matrix Req is the tool we build to generate that file from live, traced design data.

We work at Matrix One, the company that builds Matrix Req, so read every product reference on this page as our view. Regulatory statements name the clause or the FDA page they come from, and product statements cite the matrixone.health page we read on 11 November 2026.

What is a design history file?

A design history file is the evidence trail of design controls. It holds the design and development plan and every record the plan produced: the inputs, the outputs, the minutes of each design review, the verification and validation results, the design transfer and every approved change. Its job is to let an auditor follow the design from the first user need to the released device without asking anyone to explain a gap.

The DHF records how the device was designed. It is not the recipe for making it, and it is not the record of a production batch. Our DHF and DDF explainer compares the US and ISO names for the file in more detail.

Does the FDA still require a design history file after the QMSR?

It requires the records, under a different name. FDA's Quality Management System Regulation became effective on 2 February 2026 and incorporates ISO 13485:2016 by reference into 21 CFR Part 820. The same day FDA began inspecting under compliance program 7382.850 (FDA QMSR page, read 11 November 2026).

In the current eCFR text of Part 820, sections 820.20 to 820.30 are reserved, so the old 820.30(j) design history file paragraph is gone. Section 820.10 now requires a quality management system that complies with ISO 13485 (eCFR, read 11 November 2026). An investigator therefore checks your design records against clause 7.3.10. Many US teams keep the label DHF, which is fine as long as the contents meet the clause. Our 21 CFR Part 820 guide covers the rest of the regulation.

WhereRequirementWhat the file is called
US, before 2 February 202621 CFR 820.30(j)Design history file
US, from 2 February 202621 CFR 820.10, applying ISO 13485:2016 clause 7.3.10Design and development file
ISO 13485:2016Clause 7.3.10Design and development file
EU MDR 2017/745Annex II and Annex IIITechnical documentation, which draws on the design file

Is EU MDR technical documentation the same as a DHF?

No, and treating them as synonyms is a common mistake. Annex II technical documentation is broader: the device description and specification, the information supplied with the device, design and manufacturing information, the general safety and performance requirements, the benefit risk analysis and risk management, and product verification and validation including clinical evaluation. Annex III adds the post-market surveillance documentation.

The design file is a source for that dossier. The technical documentation summarises and references the design records, so a complete clause 7.3.10 file makes Annex II much faster to write. Our guide to structuring a technical file walks through the sections, and our ranking of the best EU MDR technical documentation software compares the tools.

What goes into a design history file?

One record set per design control clause. Use this map as the index of the file.

RecordClauseWhat it shows
Design and development planISO 13485:2016 clause 7.3.2Stages, reviews, verification, validation, transfer and who is responsible
Design inputsClause 7.3.3Functional, performance, usability, safety and regulatory requirements, plus risk outputs
Design outputsClause 7.3.4Specifications, drawings, software and acceptance criteria
Design reviewsClause 7.3.5Who reviewed what, when, and the actions agreed
Design verificationClause 7.3.6Plans, methods, acceptance criteria and results against each input
Design validationClause 7.3.7Evidence on representative product that user needs are met
Design transferClause 7.3.8Outputs confirmed as suitable for manufacturing
Design changesClause 7.3.9Each change reviewed, verified or validated, and approved before use
Risk management fileISO 14971:2019 clause 4.5Hazards, risk controls and the verification of each control

Our guides to design control in a medical device, design verification and validation and ISO 14971 risk management cover each record in depth, and the design freeze guide covers when outputs are locked.

How does a DHF differ from the DMR and DHR?

The DHF records how the device was designed. The device master record, now the medical device file of ISO 13485:2016 clause 4.2.3, defines how to make, label and service it. The device history record shows how each batch or unit was actually built. Design transfer is the hand-off point: approved outputs from the design file become the specifications in the device file. Our comparison of DHF, DMR, DHR, DDF and MDF and the DMR explainer set out the differences.

Why do design history files draw audit findings?

Because they are assembled after the fact. A file reconstructed at submission time has review minutes without dates, test reports that do not name the input they verify, and changes with no record of what they affected. The common gaps:

  • Verification results that cannot be traced to a specific design input.

  • Design changes approved without a recorded impact on tests and risks.

  • Documents with unclear versions, or approvals that sit outside the file.

  • A risk management file kept apart from the requirements its controls satisfy.

Our own data points at the tools. In real feedback from sales calls between February and September 2026, the most common trigger for looking at a new tool was a team still running on Word, Excel and paper (Matrix One prospect pain point study, September 2026). Technical buyers also named traceability in Excel and change impact worked out by hand among their top pains (Matrix One technical buyer study, October 2026).

One customer, a medical imaging software company, told us that generating complete documentation for an FDA submission used to take around six months, and that after two months on Matrix Req FDA preparation became a continuous process close to zero extra effort (Matrix One customer case study, read 11 November 2026). Our guide to moving a design history file out of Word and Excel covers that migration.

Should you keep the DHF as documents or as linked items?

As linked items, then generate the documents. In a document based file, a changed requirement has to be found and edited in every document that quotes it. In an item based file, each requirement, risk and test is one versioned item with its own review history, and the plan, specifications and reports are generated from those items. One change then updates every document that uses it, with the trace links intact.

That is how design records stay current through agile iterations instead of being written up at the end. Our comparison of the item based and document based approaches goes further, and the traceability guide from user needs to CE marking shows the chain the items form.

Matrix Req product requirement linked to its verification test, implementing component and related specification

Screenshot: a product requirement in Matrix Req, from the Matrix Req product page. The requirement is linked to the verification test that proves it, the component that implements it and the specification it relates to: the links a design history file has to show for every design input.

How does Matrix Req build a design history file?

Matrix Req generates documents from live requirements, risks, tests and design items as PDF, Word or HTML. It organises the technical file from project templates, including CE mark and DHF/DMR, links document versions to technical file versions, and exports the selected documents as a ZIP archive of PDFs. Review workflows and FDA 21 CFR Part 11 compliant electronic signatures cover approval (technical documentation features, read 11 November 2026).

Test protocols and test cases are traced to requirements, and every test run creates a timestamped result record. When an item changes, Matrix Req shows the affected requirements, risks and tests in real time and flags traceability that is broken, missing or outdated (design control and impact analysis page, read 11 November 2026). Risks use ISO 14971 templates with your own scoring, each linked to the requirement that controls it and the test that proves it (Matrix Req product page, read 11 November 2026).

What do you need in place before Matrix Req works?

  • A named owner for the requirements structure, who also administers the tool.

  • A decision on which items live in Jira and which in Matrix Req.

  • Your current design file, trace matrix and test reports exported, so sections and columns can be mapped to items with their links.

  • The onboarding sessions booked; the onboarding page lists the packages and what to prepare (read 11 November 2026).

Where can you read more about the design history file?

Summary: what is a design history file for medical devices?

A design history file is the record set that proves a device design followed its approved plan: inputs, outputs, reviews, verification, validation, transfer and changes. Since 2 February 2026 the FDA QMSR applies ISO 13485:2016, so in the US the same records are the clause 7.3.10 design and development file, and the EU MDR draws on them for its Annex II technical documentation. Matrix Req keeps those records as traced items and generates the file from them.

  1. Index the file by design control clause, 7.3.2 to 7.3.9, plus the ISO 14971 risk management file.

  2. Trace every verification and validation result to the input or user need it proves.

  3. Record the impact of every design change before it is approved, and keep one file for the FDA and the EU.

To compare tools for this work, see our ranking of the best design controls software for medical devices, where Matrix Req ranks first.

Last updated: 11 November 2026.

Questions teams ask about the design history file

Does the FDA still use the term design history file?

Not in the regulation. Since the QMSR took effect on 2 February 2026, 21 CFR 820.30 is reserved and section 820.10 applies ISO 13485:2016, so the requirement is the clause 7.3.10 design and development file (eCFR Part 820, read 11 November 2026). Keeping the DHF label internally is fine if the contents meet the clause.

Is a design history file the same as EU MDR technical documentation?

No. The design file records how the design was developed. Annex II technical documentation is a wider dossier covering the device description, labelling, safety and performance requirements, risk, verification and validation and clinical evaluation, and it summarises and references the design records.

Can one design file serve both the FDA and the EU MDR?

Yes. Since the QMSR, a design and development file kept to ISO 13485:2016 clause 7.3.10 is what the FDA and a notified body both check, and the EU technical documentation draws on it. Our DHF vs DMR vs DHR vs DDF vs MDF guide maps the other files.

How long must we keep the design history file?

ISO 13485:2016 clause 4.2.5 requires records to be kept for at least the lifetime of the device as you define it, and never less than two years from release. Under EU MDR Article 10(8) the technical documentation stays available for at least 10 years after the last device is placed on the market, or 15 years for implantable devices.

When a requirement changes, how do we see every test and risk it touches?

ISO 13485:2016 clause 7.3.9 expects each design change to be reviewed, and verified or validated as needed, before use. In Matrix Req a change shows the affected requirements, risks and tests in real time (design control and impact analysis page, read 11 November 2026), so the impact record goes straight into the file.

Our trace matrix is a 900 row spreadsheet. How do we move it without losing links?

Import it as items, not as a document, so each row keeps its links. The Matrix Req Premium onboarding package covers a full migration from Jama, Polarion, Jira, Excel and other legacy systems, with trace links carried across with the items (onboarding page, read 11 November 2026).

Is the tool that holds our design history file validated, and how long does validating it take us?

ISO 13485:2016 clause 4.1.6 requires you to validate software used in the quality management system. Matrix One provides a validation package for Matrix Req with plans, reports, test scripts and traceability matrices (Matrix Req product page, read 11 November 2026), and customers complete it in about 4 hours on average, a figure our team gives in Matrix Req demos (April 2026).

Written by
Eva Kautenburger
CCO

Eva Kautenburger is Chief Customer Officer at Matrix One, where she leads Customer Success & Supp across the full portfolio of regulatory and quality management solutions for the medical device industry. A certified I. and II. Party Auditor with deep expertise in ISO 13485, EU MDR/IVDR, IEC 62304, and 21 CFR Part 820, she brings both the technical fluency and regulatory grounding that MedTech customers need to navigate complex compliance landscapes. In her role, Eva oversees a cross-functional team of Solution Consultants, Solution Engineers and Account Managers, driving onboarding, retention, support and strategic growth for customers ranging from emerging device companies to global enterprises as well as consulting intiatives to support customers in their regulatory journey.

View profile →

Request a demo and get started today.

See how Matrix One connects your requirements, risks, tests, and documentation in one platform.

Request A Demo Today

Thank you

A member of our team will be in contact within 48 hours.