Dhf Missing for drug-device combination products: risk assessment and change control template


Published on 30/12/2025

Addressing Missing DHF in Drug-Device Combination Products: A Comprehensive Investigation Guide

In the dynamic landscape of pharmaceutical manufacturing, the integration of drug-device combination products presents unique challenges. One critical issue that can arise is the absence or incompleteness of the Design History File (DHF). This scenario can trigger a range of complications, including regulatory concerns and quality deviations. In this article, we will explore actionable steps for professionals in the pharmaceutical sector to effectively investigate missing DHFs, ensuring compliance with regulatory standards set forth by the FDA, EMA, and MHRA.

By the end of this article, you will be equipped with a robust framework for conducting a thorough investigation into missing DHFs and implementing effective corrective and preventive actions (CAPA). This knowledge will not only aid in immediate response but also foster ongoing quality improvement and compliance across your operations.

Symptoms/Signals on the Floor or in the Lab

The

initial identification of missing DHF components can surface through various signals, including:

  • Incompleted documentation during routine audits or inspections.
  • Requests for information from regulatory bodies resulting in warning letters or citations.
  • An increase in out-of-specification (OOS) reports related to the combination product quality.
  • Employee observations of unavailable or poorly organized documentation during checks.
  • Nonconformities reported in quality control (QC) assessments or testing outputs.

Timely recognition of these symptoms is crucial. When deviations are observed, the manufacturing and quality teams must act swiftly to assess the scope of the issue and initiate an investigation into its root causes.

Likely Causes (by category)

Understanding the potential reasons behind a missing DHF is fundamental to effective investigation. Here are categorized likely causes:

Category Cause
Materials Inadequate documentation from suppliers or missing information on component compatibility.
Method Improper procedures during the design phase leading to incomplete records.
Machine Equipment malfunction during the development process; resulting records not being generated or maintained.
Man Lack of training or awareness among personnel responsible for documentation.
Measurement Failures in quality control testing leading to undocumented changes in specifications.
Environment Inadequate storage conditions resulting in damage or loss of vital documents.
Pharma Tip:  Software Validation Gap after device supplier change: batch release impact and documentation pack

By evaluating these categories, investigators can prioritize which areas to examine more closely during the investigation process.

Immediate Containment Actions (first 60 minutes)

Upon identifying a missing DHF issue, the first hour is critical. Immediate containment actions should include:

  • Stop Production: If any production is ongoing, stop it to prevent further complications.
  • Secure Records: Investigate where documents are stored and ensure they are secured to prevent further disorganization.
  • Alert Key Stakeholders: Notify management and relevant teams such as quality assurance (QA) and regulatory affairs.
  • Initiate a Preliminary Assessment: Conduct an initial review to understand the extent of missing documentation. This could involve checking all related files for compliance.

These actions serve to mitigate risk while facilitating a more thorough investigation into the missing DHF.

Investigation Workflow (data to collect + how to interpret)

An effective investigation workflow is paramount in determining the root cause of missing documentation. Key steps include:

  1. Form an Investigation Team: Assemble a multidisciplinary team, including QA, manufacturing, and regulatory experts.
  2. Gather Documentation: Collect all relevant documentation that relates to the drug-device combination product, including development records, project plans, and change controls.
  3. Conduct Interviews: Speak with employees involved in the product’s design and manufacturing phases to gather insights about procedures followed.
  4. Review Equipment Maintenance Logs: Verify if equipment-related records may contribute to missing documentation due to operational failures.
  5. Analyze Compliance with Established Procedures: Assess whether existing SOPs (standard operating procedures) for documentation were followed or if gaps exist.

Evaluating this data will help paint a clearer picture of where the investigation should focus, guiding subsequent analysis and resolution efforts.

Root Cause Tools (5-Why, Fishbone, Fault Tree) and when to use which

Employing root cause analysis tools is essential for identifying the fundamental reasons behind missing DHFs. Here’s how to use specific techniques:

  • 5-Why Analysis: This technique involves drilling down into the problem by asking “why” multiple times (typically five) until the root cause is identified. Use this for straightforward issues with clear causal paths.
  • Fishbone Diagram: Known as Ishikawa charts, this method helps visually organize potential causes across categories. This is useful when multiple factors may contribute to the missing DHF.
  • Fault Tree Analysis: This top-down and deductive approach is beneficial for complex situations where multiple failures could occur simultaneously. It helps determine how specific failures lead to the missing documentation.

Choosing the right tool depends on the complexity of the situation and the preliminary findings gathered from your workflow.

Pharma Tip:  Complaint Handling Deficiency during lifecycle management: ownership between drug GMP and device QMS

CAPA Strategy (correction, corrective action, preventive action)

Implementing a strong CAPA process is vital after identifying the root cause of missing DHFs. Each component includes:

  • Correction: Immediately rectify the missing documentation by recompiling and organizing DHF elements. Ensure that all relevant data is accurate and complete.
  • Corrective Action: Address the systemic issues discovered during the investigation, such as revising procedures, enhancing training, or improving documentation practices to prevent recurrence.
  • Preventive Action: Establish mechanisms to monitor ongoing compliance. This may involve internal audits, scheduled reviews of DHF alignment with regulatory standards, and reinforcing training for personnel.

By taking comprehensive CAPA steps, organizations can significantly reduce the likelihood of recurrences and improve internal processes.

Control Strategy & Monitoring (SPC/trending, sampling, alarms, verification)

A robust control strategy can further help in monitoring documentation integrity and quality management:

  • Statistical Process Control (SPC): Utilize SPC charts to monitor trends in documentation adherence and detect anomalies quickly.
  • Sampling Strategies: Establish a regular sampling of documents for completeness checks as part of an ongoing quality check system.
  • Set Alarms: Implement alarms for potential deviations in documentation processes to ensure immediate action if errors or missing documents are detected.
  • Verification Practices: Regularly audit the DHF files to verify consistency with production records and ensure no documentation is neglected over time.

A comprehensive control strategy will safeguard against future issues while enhancing overall quality management systems.

Related Reads

Validation / Re-qualification / Change Control impact (when needed)

Upon addressing the missing DHF issue, it’s critical to evaluate the impacts on validation, re-qualification, and change control:

  • Validation: Ensure that any product using the updated DHF undergoes thorough validation to verify that it meets all intended specifications and quality standards.
  • Re-qualification: Evaluate whether any processes or equipment involved that might have been affected by the missing documentation require re-qualification.
  • Change Control: Implement changes prompted by the investigation findings within the change control system to maintain a comprehensive record of alterations.

These validations and controls ensure compliance and product quality, preserving the integrity of your operations post-investigation.

Inspection Readiness: what evidence to show (records, logs, batch docs, deviations)

In preparation for inspections, organizations must maintain a clear roadmap of evidence showing compliance and corrective measures taken:

  • Records and Logs: Ensure all investigation records, CAPA documentation, and updates to SOPs are readily available and organized.
  • Batch Documentation: Verify that all batch records are complete and match updated DHF contents, demonstrating robustness in production processes.
  • Deviations: Keep a detailed log of any deviations and the corrective actions taken, demonstrating a proactive approach to quality management.
Pharma Tip:  Regulatory Classification Issue during PAI readiness: risk assessment and change control template

Viewing the investigation through the lens of inspection readiness will enhance your organization’s credibility during regulatory audits and inspections.

FAQs

What is a DHF?

A Design History File (DHF) is a compilation of records that describe the design and development of a medical device or combination product. It demonstrates compliance with regulatory requirements.

Why is a missing DHF a significant issue?

A missing DHF can lead to regulatory non-compliance, quality deviations, and a lack of clarity regarding product specifications, impacting approval and patient safety.

How can I prevent missing DHFs?

Implement strict documentation controls, regular audits, and employee training to ensure that all design and development aspects are appropriately documented.

What should I do first when I identify a missing DHF?

Immediately initiate containment actions, such as halting production and securing existing documentation before starting the investigation process.

What tools can help in root cause analysis for missing DHFs?

Common tools include 5-Why Analysis, Fishbone Diagrams, and Fault Tree Analysis to identify the underlying causes effectively.

Are there specific regulatory considerations for missing DHFs?

Yes, missing DHFs may violate FDA, EMA, or MHRA guidelines, leading to potential fines or product recalls if not addressed promptly.

How can I ensure my investigation is inspection-ready?

Maintain thorough and organized records of the investigation process, including documentation of CAPA actions, audits, and results that align with regulatory expectations.

Is CAPA the same as Quality Improvement?

While related, CAPA is focused on addressing specific issues after they arise, whereas quality improvement is a broader, ongoing process to enhance overall quality management.

What is an out-of-specification (OOS) report?

An OOS report documents results that fall outside predetermined acceptance criteria, requiring further investigation to determine the cause and potential impact.

How can employees be trained on documentation best practices?

Provide structured training sessions, create clear documentation guidelines, and establish a culture that values accuracy and thoroughness in record-keeping.

What impact does a missing DHF have on product validation?

A missing DHF may necessitate re-evaluation of product validation, as it could mean that the design and development processes were not fully documented and verified.

What are the potential consequences of not having a complete DHF?

Consequences may include regulatory penalties, product recalls, operational disruptions, and damage to company reputation.