Design History File (DHF) Remediation for Medical Devices

A Design History File (DHF) is a critical regulatory record that demonstrates how a medical device was designed and developed in compliance with FDA design controls (21 CFR 820.30) and evolving FDA Quality Management System Regulation (QMSR), which aligns with ISO 13485:2016 requirements. A complete, well-structured DHF establishes end-to-end design traceability, supports verification and validation activities, reduces audit and inspection risk, and enables faster, more confident regulatory submissions while maintaining compliance throughout the product lifecycle.

With the implementation of QMSR (effective February 2026), DHF expectations are increasingly aligned with ISO 13485 design and development documentation, often referred to as a Design and Development File (DDF).

Speak to our Experts

Medical Device Design History File (DHF) - Overview

The medical device industry is facing increased regulatory scrutiny and growing expectations for design transparency, traceability, and lifecycle documentation. With the transition to the FDA’s Quality Management System Regulation (QMSR), greater alignment with ISO 13485, and the rise of software-driven and connected devices, manufacturers are expected to maintain more robust, well-structured design and development documentation (commonly referred to as DHF or Design and Development File (DDF) under QMSR) that clearly demonstrate controlled design and development practices across global markets.

At the same time, manufacturers face significant challenges in maintaining compliant DHFs. Common issues include legacy devices with incomplete design records, fragmented documentation across systems, weak traceability between requirements and verification or validation evidence, and design changes that were not adequately impact-assessed or documented. These gaps often surface during audits, inspections, or submission reviews, creating compliance risk, delays, and remediation pressure.

Freyr supports medical device manufacturers by addressing these challenges through both proactive DHF development and targeted DHF remediation. For new and in-development products, Freyr helps establish structured, audit-ready DHFs aligned with regulatory expectations from the outset. For legacy and in-market devices, Freyr conducts DHF gap assessments, restores traceability, updates documentation, and remediates deficiencies, enabling customers to strengthen compliance, improve inspection readiness, and maintain DHF integrity throughout the product lifecycle.

Regulatory Context and Design History File (DHF) Requirements

FDA Design Controls (21 CFR Part 820)

Under FDA design controls, manufacturers are required to establish and maintain a Design History File (DHF) to document that the design of a medical device was developed in accordance with an approved design and development plan. The regulation expects manufacturers to document critical design activities within the DHF, including:

  • Design and development planning

  • Design reviews

  • Design verification

  • Design validation

  • Design changes

Collectively, these records demonstrate that the device design was systematically planned, reviewed, verified, validated, and controlled throughout development and subsequent updates, forming a key focus area during FDA inspections.

ISO 13485 Alignment

ISO 13485:2016 requires manufacturers to maintain comprehensive design and development documentation, often referred to as a Design and Development File (DDF). Under QMSR, this ISO-aligned approach becomes the primary framework for organizing design documentation. This documentation must demonstrate controlled design processes, risk management, verification and validation, and change management throughout the product lifecycle. Many organizations adopt a harmonized DHF structure to efficiently support both FDA and ISO audit expectations

Common Triggers for DHF Remediation and Updates

Medical device manufacturers typically initiate Design History File (DHF) remediation or updates in response to regulatory, operational, or lifecycle-driven events, including:

  • FDA inspections, enforcement actions, or 483 observations related to design controls
  • ISO 13485 surveillance, recertification, or MDSAP audits identifying documentation gaps
  • Legacy or long-standing products with incomplete or historically undocumented design records
  • Design changes such as software updates, usability improvements, or risk control modifications
  • Regulatory submission preparation requiring clearer design traceability and V&V evidence
  • Manufacturing site, supplier, or process transfers impacting design assumptions
  • Mergers, acquisitions, or design ownership transfers requiring documentation harmonization
  • Transition to FDA QMSR, including alignment of legacy DHFs to ISO 13485-based Design and Development File (DDF) expectations

Design History File (DHF) Deliverables

Freyr delivers inspection-ready DHFs that are clearly structured and traceable. Deliverables are structured to align with both traditional DHF expectations and ISO 13485-aligned Design and Development File (DDF) frameworks under QMSR. Depending on product scope and lifecycle stage, deliverables may include:

  • DHF index and document map
  • Design and development plan documentation
  • Intended use and user needs documentation
  • Design inputs and design outputs
  • Risk management and hazard analysis records
  • Design review records with approvals
  • Design verification and validation evidence
  • Design transfer documentation
  • Design change documentation and impact assessments
  • End-to-end traceability matrix linking requirements, risks, and V&V

Freyr’s Design History File Services

For new products and active development programs, Freyr supports DHF creation alongside design activities to ensure documentation is complete, compliant, and up to date.

Key activities include:

  • Establishing DHF structure, indexing, and naming conventions
  • Aligning DHF structure with Design and Development File (DDF) expectations under QMSR
  • Mapping design control procedures to DHF records
  • Developing traceability between user needs, design inputs, risks, and V&V
  • Reviewing design documentation for completeness and audit readiness

Freyr conducts targeted DHF gap assessments to identify compliance risks early and provide clear remediation roadmaps.

Assessment outcomes include:

  • Identification of missing or weak DHF elements
  • Traceability and documentation gaps
  • Practical recommendations aligned to regulatory expectations

Legacy devices, transferred products, and acquisitions often have incomplete or inconsistent DHFs. Freyr’s remediation services focus on efficiently restoring compliance and inspection readiness.

Our remediation approach includes:

  • DHF gap assessment against FDA QMSR and ISO 13485 design and development requirements
  • Identification and recovery of existing design evidence
  • Gap closure planning and prioritized remediation
  • Traceability restoration across design, risk, and verification/validation
  • Assembly of an inspection-ready DHF package

In practice, DHF remediation is most commonly triggered by audits, inspections, legacy documentation gaps, or regulatory submissions requiring clearer traceability and verification or validation evidence.

Why Partner with Freyr?

  • Deep expertise in medical device design controls and documentation
  • Expertise in transitioning legacy DHFs to QMSR-aligned Design and Development File (DDF) structures
  • Proven experience supporting FDA inspections and ISO 13485 audits
  • Scalable support for new development, legacy remediation, and global portfolios
  • Practical, audit-focused approach to traceability and DHF structure

Frequently Asked Questions

01. What is a Design History File (DHF)?

A DHF is a structured compilation of records that describes the design history of a finished medical device, ensuring it was developed according to an approved plan and regulatory requirements under FDA 21 CFR 820.30. It demonstrates traceability and compliance throughout the design lifecycle, from planning through verification, validation, and transfer.

02. Why is a DHF important for medical device compliance?

A DHF is essential for regulatory compliance because it provides documented evidence that design controls were applied throughout development, supports audit readiness, and helps demonstrate that the device meets safety and performance expectations. It also facilitates inspections and submissions by making design decisions and outcomes traceable and accessible.

03. Which regulatory requirements govern DHF or design documentation?

Under FDA’s Quality System Regulation (FDA 21 CFR 820.30), manufacturers must establish and maintain a DHF for each medical device type to demonstrate compliance with design controls. ISO 13485 similarly requires design and development documentation that aligns with DHF expectations, ensuring global regulatory consistency.

04. How does FDA QMSR impact the Design History File (DHF)?

With the implementation of FDA’s Quality Management System Regulation (QMSR) in February 2026, the traditional concept of a Design History File (DHF) is evolving to align with ISO 13485:2016. While the core intent remains the same, demonstrating that a device was designed in accordance with approved requirements, the terminology and structure are shifting toward a more integrated Design and Development File (DDF) approach. This change emphasizes risk-based design processes, stronger traceability across the product lifecycle, and closer integration with broader documentation such as the Medical Device File (MDF). Manufacturers are expected to assess and update legacy DHFs to ensure alignment with these new expectations.

05. What is the difference between DHF, DMR, and DHR?

A DHF documents how a medical device was designed and developed, focusing on design controls and evidence. A Device Master Record (DMR) contains specifications and instructions for manufacturing the device, while a Device History Record (DHR) demonstrates that a specific unit or batch was manufactured according to the approved DMR.

06. When should a DHF be created and maintained?

A DHF should be initiated early in the design and development process and maintained throughout the product lifecycle, including updates for design changes, verification, and validation. Continuous maintenance ensures that the DHF accurately reflects current design status and supports inspection readiness at all times.

07. What are common pitfalls in DHF documentation?

Common pitfalls include late assembly of design documents, incomplete traceability between requirements and test results, missing design review evidence, and poorly documented design changes. Addressing these gaps proactively strengthens compliance and reduces risk during regulatory inspections.

08. What is the difference between DHF update and DHF remediation?

A DHF update involves maintaining and refreshing existing design documentation to reflect changes such as design modifications, risk updates, or lifecycle events. DHF remediation addresses significant gaps or deficiencies in historical design records, often identified during audits or inspections, to restore compliance, traceability, and regulatory confidence.

09. Why is Freyr considered a leading partner for Medical Device Design History File (DHF) services?

Freyr combines deep medical device regulatory expertise with structured, global experience across design controls and compliance frameworks, helping manufacturers navigate FDA and ISO requirements with clarity. With a decade of industry focus, a broad international footprint, and a multidisciplinary approach to quality and traceability, Freyr supports both proactive DHF planning and legacy remediation for audit readiness.