Updated for FDA QMSR 2026

Design History File for Medical Devices — Expert DHF Consulting

A complete, traceable design history file for medical devices is your single most important document during an FDA audit. We build it right — from day one — so you never face a Form 483, a Warning Letter, or a rejected submission.

200+ DHF Projects Completed

98% First-Attempt Approval Rate

48hr Query Resolution Time

15+ Yrs. Regulatory Experience

Quick Answer

A design history file (DHF) for a medical device is a mandatory compilation of all records proving that the device was designed and developed under FDA-compliant design controls. Required under 21 CFR Part 820.30(j) and ISO 13485 Clause 7.3.10, the DHF must document design planning, inputs, outputs, reviews, verification, validation, risk analysis, design transfer, and all design changes. Under FDA’s updated QMSR (effective February 2, 2026), the DHF is now aligned with the ISO 13485 term “Design and Development File (DDF)” — but the documentation requirements remain essentially unchanged. Without a complete, audit-ready DHF, medical device manufacturers risk FDA inspectional findings, 510(k) delays, and PMA rejection.

Definition & Overview

What Is a Design History File (DHF) in Medical Devices?

A design history file is not just paperwork — it is the documented proof that your medical device was developed safely, systematically, and in full compliance with FDA and international standards.

The design history file (DHF) for a medical device is a structured compilation of records documenting the complete design and development history of a finished device. It is mandated by the FDA under 21 CFR Part 820.30(j) and must demonstrate that the device was built according to an approved design plan and the requirements of FDA’s quality system regulations.

Think of the DHF as the complete documentary biography of your device’s design. Every decision made during development — from early user needs to final validation testing — must be captured, organized, and traceable within this file. FDA auditors and inspectors rely on the DHF to verify design integrity during inspections, 510(k) reviews, and PMA evaluations.

Internationally, ISO 13485:2016 Clause 7.3.10 requires an equivalent “Design and Development File” for all device types or families. Under the FDA’s 2026 QMSR update, these terminologies are now aligned — the DHF concept maps directly to the Design and Development File (DDF) in the new regulatory framework.

Unlike the Device Master Record (DMR), which contains manufacturing specifications, or the Device History Record (DHR), which captures batch production data, the DHF is specifically focused on documenting how and why the device was designed the way it was.

DHF AT A GLANCE

FDA Regulation

21 CFR 820.30(j)

ISO Standard

ISO 13485 Cl. 7.3.10

EU MDR Equivalent

Technical Documentation

QMSR 2026 Term

Design & Dev. File (DDF)

Who Must Have It

Class I*, II & III

Maintained By

Device Manufacturer

Storage Format

Physical or eQMS

REGULATORY HISTORY

DHF Regulatory Evolution: From 1990 to QMSR 2026

Understanding the regulatory history helps you stay ahead of compliance requirements as the framework continues to evolve.

1990

Safe Medical Devices Act — FDA given authority to require design controls

1997

FDA QSR published: DHF requirement under 21 CFR 820.30(j)

2016

ISO 13485:2016 updated — Design & Development File aligned with FDA DHF

2024

FDA announces QMSR final rule aligning 21 CFR 820 with ISO 13485:2016

Feb 2026

QMSR effective — DHF now aligned with "Design & Development File (DDF)"

DHF Contents

What Must Be in Your Design History File?

A complete DHF medical device file covers every stage of the design controls process. Missing even one section can trigger a Form 483 observation during an FDA inspection.

DHF Component	What It Must Contain	FDA Reference	Status
Design & Development Plan	Defined stages, responsibilities, review points, interfaces, and approved design plan	$820.30(b) / ISO 7.3.2	Required
Design Inputs	User needs, regulatory requirements, performance & safety standards	$820.30(c) / ISO 7.3.3	Required
Design Outputs	Drawings, specifications, labeling, acceptance criteria — mapped to inputs	$820.30(d) / ISO 7.3.4	Required
Design Review Records	Review minutes, participants, findings, and follow-up actions	$820.30(e) / ISO 7.3.5	Required
Design Verification Reports	Test protocols, results, confirming outputs meet inputs	$820.30(f) / ISO 7.3.6	Required
Design Validation Data	Clinical/simulated testing, usability, software validation	$820.30(g) / ISO 7.3.7	Required
Risk Management File	Risk analysis, evaluation, controls (ISO 14971)	ISO 14971	Required
Design Transfer Records	Final specifications transferred to production & SOPs	$820.30(h) / ISO 7.3.8	Required
Design Change Records	All changes with impact assessment & approvals	$820.30(i) / ISO 7.3.9	Required
Traceability Matrix	Links inputs → outputs → verification → validation	Best Practice	Strongly Recommended
Biocompatibility Testing	ISO 10993 reports for patient-contact materials	ISO 10993	Device-Specific

Common FDA Form 483 Observations Related to Design History File

Incomplete or missing design validation records — especially for software and usability testing
No traceability between design inputs and design outputs (most frequently cited DHF finding)
Design changes made without documented impact assessment or updated V&V evidence
Design reviews conducted without formal records, participant lists, or follow-up closure evidence
Risk management file not cross-referenced with the DHF or not following ISO 14971
DHF maintained as static document — not updated to reflect post-market design changes

Key Distinctions

DHF vs. DMR vs. DHR — Understanding the Difference

Many manufacturers confuse these three critical record types. Understanding what belongs in each file is essential for FDA compliance and audit readiness.

Focus: Design History

Design History File (DHF)

Focus: Manufacturing Instructions

Technical Section

Focus: Production Records

Design History File (DHF)

Step-by-Step Process

How to Build a Compliant Design History File — Phase by Phase

The DHF is not assembled at the end of development. It is built concurrently with your device, starting at day one. Here is how the compliant process works under FDA QMSR and ISO 13485.

Design & Development Planning

Before any design work begins, establish a formal design plan that defines development stages, team responsibilities, review milestones, and interdepartmental interfaces. This living document must be updated as the project evolves. Your DHF opens with an approved, signed design plan — without it, everything downstream is unanchored. TraccGlobal's experts help you structure a realistic, regulation-compliant plan that integrates your real project timeline.

Capturing Design Inputs

Design inputs are the measurable, objective requirements your device must meet — derived from user needs, intended use, regulatory standards, and safety requirements. The FDA requires that inputs address ambiguous requirements before design begins. Poorly defined inputs are the root cause of most downstream DHF failures because they make verification impossible. Every input must be traceable forward to a corresponding output.

Documenting Design Outputs

Design outputs are the tangible results of your engineering work — drawings, specifications, software code, labeling, manufacturing procedures. Every output must trace back to a specific design input. The DHF must contain approved, version-controlled output documents with evidence that they meet input requirements. Outputs also form the foundation of your Device Master Record (DMR).

Design Reviews at Each Stage

Formal design reviews must be conducted at defined stages with representatives from each design function. FDA expects documented minutes, attendee lists, the design version reviewed, findings, and evidence that action items were closed. Design reviews are among the most common Form 483 observations when they are informal, incomplete, or retrospective. Build them into your stage gates, not after them.

Design Verification

Verification answers the question: "Did we build the design right?" It confirms that design outputs meet design inputs through objective testing — benchtop tests, analysis, inspection, or demonstration. Each verification activity needs a protocol (approved before testing), test results, and a summary report. The DHF must show a clean chain from each input → output → verification test → result.

Design Validation (Including Risk Analysis)

Validation answers: "Did we build the right design?" It must be performed under actual or simulated use conditions using initial production units, not prototypes. For SaMD and software-containing devices, IEC 62304 software validation and IEC 62366 usability engineering are required. Risk analysis per ISO 14971 must be integrated and referenced within the DHF. This is the most scrutinized section during FDA inspections and 510(k) reviews.

Design Transfer to Manufacturing

The design transfer phase documents how your validated design is handed off to manufacturing. The DHF must include final device specifications, approved procedures (SOPs), process validation evidence, and manufacturing sign-off confirming that production can consistently replicate the design. Many companies treat transfer as informal — this creates compliance gaps that surface during audits.

Design Change Control (Ongoing)

The DHF is a living document. Every design change — post-market or during development — must go through formal change control with documented impact assessment, updated verification or validation evidence as needed, and approval signatures. Undocumented design changes are a serious compliance violation and among the most common FDA enforcement actions in the medical device industry.

Real-World Experience (EEAT)

Real DHF Case Studies — How We've Helped Medical Device Companies

These cases reflect actual challenges our clients faced with their design history file documentation and how TraccGlobal resolved them. Company names are kept confidential for privacy.

Case Study 1: Retroactive DHF Remediation — Saved a 510(k) Submission

A US-based startup with a Class II surgical robotic system had been in development for 26 months before engaging TraccGlobal. Their existing documentation was scattered across multiple engineering tools, Google Drive folders, and email threads. When they started preparing their 510(k) submission, they discovered their design inputs had never been formally approved, their verification testing lacked approved protocols (tests were run before protocols were written), and there was no formal design review record for any development stage.

TraccGlobal conducted a full DHF gap assessment, mapped all existing documentation to FDA requirements, identified 34 specific gaps, and executed a structured remediation plan over 11 weeks. We rebuilt the traceability matrix from scratch, facilitated retroactive design reviews with proper documentation, drafted missing verification protocols retrospectively with objective evidence, and reorganized the entire DHF into an eQMS-structured format ready for FDA review.

510(k) submission filed on schedule. FDA Additional Information request received — only 2 minor documentation questions, both resolved in 10 days. Device cleared without additional submission cycle.

Case Study 2: DHF for Software as a Medical Device (SaMD) — De Novo Success

A digital health company sought a De Novo classification for their AI-based radiology diagnostic software. SaMD DHF requirements are significantly more complex than traditional hardware devices — they require IEC 62304 lifecycle documentation, AI/ML model validation under FDA’s predetermined change control plan guidance, IEC 62366 usability engineering, and cybersecurity documentation per FDA’s 2023 guidance.

TraccGlobal’s SaMD regulatory team built a purpose-specific DHF structure covering the full IEC 62304 software lifecycle, documented the AI model training data governance, validation testing across diverse patient populations, post-deployment monitoring plan, and a comprehensive usability engineering file including summative usability studies. We also structured the DHF to support the De Novo special controls being proposed.

De Novo request granted. The company's DHF structure was cited by FDA as "well-organized and thorough" in their review correspondence — a rare and direct acknowledgment of documentation quality.

Case Study 3: PMA-Grade DHF for Class III Cardiac Device

A medical device manufacturer developing a next-generation cardiac rhythm management device needed a PMA-grade DHF that would survive the most rigorous FDA review. Class III PMA DHFs require the highest level of documentation depth — comprehensive clinical evidence, extensive risk management documentation under ISO 14971, and full design control traceability across a multi-year development program spanning five engineering teams across two countries.

TraccGlobal embedded a regulatory consultant within the client’s development team for 18 months, building the DHF concurrently with development rather than retrospectively. We implemented a cloud-based eQMS with real-time traceability matrix updates, standardized design review templates used across all five engineering teams, and monthly DHF readiness reviews to identify and close gaps before they accumulated.

PMA submission filed with zero requests for additional information on design control documentation — an exceptional result for a Class III cardiac device. Device received PMA approval in 14 months.

Our Services

TraccGlobal's Design History File Services for Medical Devices

Whether you are starting a new device program, preparing for an FDA inspection, or remediating an incomplete DHF, TraccGlobal has a proven solution. Contact us for a free assessment.

DHF Gap Assessment & Audit

Complete review of your existing design history file against FDA 21 CFR 820.30, QMSR 2026, and ISO 13485 Clause 7.3. We identify every gap, prioritize by inspection risk, and provide a detailed remediation roadmap.

DHF Build from Scratch (New Devices)

For new medical device programs, we establish your complete design history file structure, templates, and workflows from day one — concurrently with your development — so you are audit-ready at every stage gate.

Retroactive DHF Remediation

Your device is developed but the DHF is incomplete or disorganized? We reconstruct and remediate your design history file with objective evidence mapping, retroactive design reviews, and full traceability restoration.

Traceability Matrix Development

We build comprehensive traceability matrices linking user needs → design inputs → design outputs → verification tests → validation studies. This is the backbone of any audit-ready DHF and the first thing FDA inspectors request.

SaMD & Software DHF Consulting

Specialized DHF services for Software as a Medical Device (SaMD) under IEC 62304, IEC 62366 usability engineering, FDA cybersecurity guidance, and AI/ML predetermined change control plans.

FDA Inspection Readiness — DHF Focus

Pre-inspection mock audits with your DHF as the primary focus. We identify every potential Form 483 observation before FDA does, prepare your team for inspector questions, and organize documents for rapid retrieval during inspections.

DHF for 510(k) & PMA Submissions

While you don't typically submit the DHF itself in a 510(k), FDA expects your design documentation to be complete and available. We ensure your DHF supports your submission narrative and withstands any FDA request for additional information.

QMSR 2026 DHF Transition Support

Under FDA's QMSR effective February 2026, your DHF must align with ISO 13485 Design and Development File (DDF) terminology and requirements. We assess your current DHF against the new framework and guide the transition with minimal disruption.

TraccGlobal DHF Documentation Deliverables

Why Choose Us

Why Medical Device Companies Choose TraccGlobal for DHF Services

Not all regulatory consultants understand the depth of DHF requirements. TraccGlobal brings real regulatory expertise — not just document templates.

Device-Type Expertise

From simple Class II instruments to complex Class III implants, AI-driven SaMD, and IVD devices — our consultants have hands-on DHF experience across every device category. We know the specific documentation requirements for your device type, not just the general framework.

Built for Speed Without Gaps

Most DHF consultants either move fast and leave gaps, or move carefully and blow your timeline. TraccGlobal's structured DHF methodology delivers both — faster than average with a 98% first-attempt inspection pass rate across our client portfolio.

FDA Inspection Mindset

Our consultants approach every DHF the way an FDA investigator would review it. We pre-empt the specific questions inspectors ask, ensure your documentation survives hostile scrutiny, and prepare your team to answer confidently during audits.

Global Regulatory Alignment

If you need your DHF to support both FDA 510(k)/PMA submissions and EU MDR Technical Documentation, TraccGlobal structures it for dual use — saving you from building two parallel document systems. We serve USA, EU, and global market entries.

QMSR 2026 Ready

We have already updated all DHF frameworks, templates, and review processes to align with FDA's QMSR (effective February 2, 2026) and ISO 13485:2016. Your DHF will be built on current regulatory requirements — not outdated QSR templates.

Long-Term Compliance Partnership

A DHF is never truly "done" — it requires maintenance through design changes, post-market feedback, and regulatory updates. TraccGlobal stays with you beyond the initial build, providing ongoing DHF maintenance, change impact reviews, and continuous compliance support.

Frequently Asked Questions

The questions real medical device professionals search for — answered with regulatory accuracy and practical insight.

Real questions asked on Google — answered clearly so you can make informed decisions about your CDSCO compliance journey.

What is a Design History File (DHF) for a medical device?

A design history file (DHF) for a medical device is a structured compilation of all records that document how a device was designed and developed. Required under FDA 21 CFR Part 820.30(j), the DHF must demonstrate that the device was developed in accordance with an approved design plan and FDA’s design control requirements. It covers everything from initial user needs and design inputs through design outputs, formal reviews, verification testing, validation studies, risk management, and design transfer. Under the FDA QMSR effective February 2, 2026, the DHF concept is now aligned with the ISO 13485 term “Design and Development File (DDF),” but the documentation requirements remain essentially identical.

What is required in a DHF for a medical device under FDA regulations?

Under 21 CFR Part 820.30, a complete DHF must contain or reference: (1) Design and development plan, (2) Design input requirements, (3) Design output documents, (4) Design review records with attendees and results, (5) Design verification protocols and results, (6) Design validation data including risk analysis and software validation, (7) Design transfer documentation, and (8) All design change records with impact assessments. Every document must be version-controlled, approved, dated, and traceable. Under ISO 13485 Clause 7.3.10 (now incorporated into FDA’s QMSR), the file must also reference records for any design and development changes.

Has the DHF requirement changed with FDA QMSR 2026?

Yes, terminology has changed. FDA’s QMSR became effective February 2, 2026, incorporating ISO 13485:2016 by reference into 21 CFR Part 820. The traditional term “Design History File (DHF)” under the old QSR is now conceptually aligned with “Design and Development File (DDF)” under ISO 13485 Clause 7.3.10. FDA also introduced the broader “Medical Device File (MDF)” concept. Practically speaking, the documentation requirements are essentially unchanged — you still must maintain all design control records. However, if your DHF is structured around old QSR terminology, a QMSR gap assessment is recommended to ensure alignment. Many companies continue using “DHF” internally as shorthand while structuring documentation to meet the updated standard.

What is the difference between a DHF medical device file and a DMR?

These are two distinct but complementary record systems. The Design History File (DHF) documents the design and development process — why and how the device was designed. It is built during product development. The Device Master Record (DMR) contains the manufacturing instructions — drawings, specifications, SOPs, labeling — used to reproduce the device consistently in production. Think of it this way: the DHF tells the story of how the design was created and validated; the DMR tells the factory how to build it. Under FDA’s QMSR 2026, the DMR concept is incorporated into the broader “Medical Device File (MDF)” framework aligned with ISO 13485.

Do you need to submit the Design History File with your 510(k)?

No — you generally do not submit the complete DHF with a standard 510(k) submission. However, the DHF must be complete, organized, and readily available because: (1) FDA may request design documentation during the review process, (2) FDA investigators will review your DHF during Quality System Inspections (QSIs) following 510(k) clearance, and (3) Summary of design control activities is required in some 510(k) sections. For a PMA (Premarket Approval) for Class III devices, FDA’s review is much more intensive and design control documentation is thoroughly reviewed as part of the application. A complete, traceable DHF directly supports faster PMA approval.

What happens if your DHF is incomplete during an FDA inspection?

An incomplete or poorly maintained design history file is consistently one of the most common FDA Form 483 inspection observations in the medical device industry. Consequences range from minor to severe: a Form 483 observation requiring a written response and corrective action; a Warning Letter (public and serious) if the agency believes violations are significant; a product hold or import alert if the DHF gaps relate to safety; or, in extreme cases, consent decrees requiring third-party oversight of your entire quality system. For companies with pending submissions, DHF deficiencies discovered during inspection can delay or block clearance. TraccGlobal conducts pre-inspection DHF mock audits to eliminate these risks before FDA arrives.

How long does it take to build or remediate a Design History File?

Timeline depends on device complexity and the state of existing documentation. For a new device built correctly from day one, the DHF is built concurrently throughout the development program — typically 12 to 36 months for Class II/III devices. For a DHF gap assessment of an existing device, TraccGlobal typically completes the assessment in 2 to 4 weeks. Full retroactive DHF remediation for a Class II device usually takes 6 to 12 weeks depending on how many gaps exist. Complex Class III devices or multi-site programs may take 3 to 6 months for full remediation. The most critical factor is starting early — DHF gaps that are identified during development are far cheaper to fix than those discovered 30 days before an inspection.

What is a "device history file" — is it the same as a DHF?

The terms are often used interchangeably in casual conversation, but they technically refer to different records in FDA’s quality system framework. The Design History File (DHF) documents the design and development process. The term “Device History File” is sometimes used loosely to mean the same thing, but it can also refer to the Device History Record (DHR) — which is the manufacturing record for each production unit or batch. In formal FDA regulatory language, always use “Design History File (DHF)” for design control documentation and “Device History Record (DHR)” for production records. Under QMSR 2026, the DHF is now aligned with ISO 13485’s “Design and Development File (DDF).”

Is Your Design History File Truly Audit-Ready?

Most medical device companies discover DHF gaps at the worst possible moment — during an FDA inspection or after a 510(k) Additional Information request. Don’t wait. TraccGlobal offers a free, no-obligation DHF readiness assessment for qualified medical device manufacturers.