Governance and Responsibility Splits in Pharma–Diagnostic Partnerships

Governance and Responsibility Splits in Pharma–Diagnostic Partnerships

Governance and Responsibility Splits in Pharma–Diagnostic Partnerships

Context

In the rapidly evolving landscape of pharmaceuticals and diagnostics, the integration of companion diagnostics, in vitro diagnostics (IVDs), and Software as a Medical Device (SaMD) creates unique regulatory challenges. These challenges are borne from the necessity to clearly delineate responsibilities and regulatory pathways when developing combination products that often straddle both the pharmaceutical and diagnostic realms. This article serves as a comprehensive guide for regulatory affairs professionals navigating these complexities, with a specific focus on the roles of key stakeholders and the intersection of regulations across the US, EU, and UK.

Legal/Regulatory Basis

The governance of pharmaceutical and diagnostic partnerships is guided by a multitude of regulations and guidelines, most notably:

  • 21 CFR (Code of Federal Regulations) – Especially Parts 312 (Investigational New Drug Application), 814 (Premarket Approval), and 820 (Quality System Regulation) in the USA.
  • EU Regulation 2017/745 – Concerning medical devices, which also encompasses certain diagnostics, setting forth rigorous requirements for safety and efficacy.
  • EU Regulation 2017/746 – Specified for in vitro diagnostic medical devices.
  • MHRA Guidelines – In the UK, the Medicines and Healthcare products Regulatory Agency (MHRA) oversees both medicinal products and devices.

In the context of

href="https://www.fda.gov" target="_blank">FDA and EMA regulations, the definition of combination products (Pharmaceuticals and Devices) is particularly crucial as it determines the specific pathway for regulatory approval and the requisite responsibilities of the involved stakeholders.

Documentation

Accurate and comprehensive documentation plays a pivotal role in the regulatory process. The following are essential documentation types that must be meticulously prepared and maintained:

  • Regulatory Submission Dossiers: This includes Investigational New Drug Applications (IND), New Drug Applications (NDA), and Market Authorization Applications (MAA) specific to the product class.
  • Technical Documentation: Evidence demonstrating compliance with the applicable regulatory standards; includes design and manufacturing processes, risk analysis, and performance data of diagnostic capabilities.
  • Quality Management System (QMS) Records: Documentation of the QMS must be aligned with ISO 13485 or equivalents, along with compliance to Good Manufacturing Practice (GMP).
  • Clinical Investigation Reports: Essential for demonstrating safety and efficacy; the design, results, and analysis of trials must be aligned with Good Clinical Practice (GCP).
See also  Interfacing Drug, Device and Software Regulatory Teams in One Program

Key Considerations for Documentation

When facing the regulatory scrutiny of FDA or EMA, certain considerations should guide the documentation process:

  • Clarity and Transparency: All documents must be concise and unequivocal to minimize confusion during regulatory reviews.
  • Comprehensive Bridging Data: In case of leveraging existing data from related products, providing explicit studies or justifications for bridging data is imperative.

Review/Approval Flow

The regulatory review process for companion diagnostics and IVDs typically involves several critical stages:

  1. Pre-Submission Meetings: Engaging with regulatory authorities prior to dossier submission can help align expectations and identify potential pitfalls in the submission.
  2. Submission of Dossiers: Regulatory submissions must include all necessary documentation, detailing the product’s safety, effectiveness, and quality. Ensure to differentiate between variations vs. new applications based on the scope of changes to utilize the correct pathway.
  3. Regulatory Authority Review: Upon submission, agencies like the FDA, EMA, or MHRA undertake a thorough assessment of the documentation, which often includes direct communication with the applicant to clarify discrepancies.
  4. Post-Approval Commitments: Many applications result in the requirement for post-market surveillance and pharmacovigilance, emphasizing continual oversight of product performance post-launch.

Common Deficiencies

Understanding common deficiencies in regulatory submissions can significantly improve the chances of approval. Some prevalent issues include:

  • Inadequate Risk Management: Failure to provide comprehensive risk assessments can lead to delays in approval. It’s critical to demonstrate how risks have been identified and mitigated.
  • Poor Justification for Bridging Data: Regulatory authorities expect clear reasoning and supporting datasets for leveraging existing clinical data; ambiguous justifications can result in request for further data.
  • Unclear Clinical Outcomes: Efficacy data needs to be robust and clearly linked to clinical outcomes. Ambiguity can raise questions about the validity of the diagnostic’s clinical relevance.
  • Insufficient Collaboration Documentation: In partnerships, clear delineation of responsibilities and documented agreements between pharmaceutical and diagnostic entities must be in place to avoid misunderstandings.
See also  SaMD and Software-Enabled Diagnostics: Regulatory Basics for RA Teams

RA-Specific Decision Points

The interaction between regulatory affairs and other departments—such as Quality Assurance (QA), Clinical Development, and Pharmacovigilance (PV)—is crucial for successful product development. Here are several decision points to consider within RA:

Filing Variations vs. New Applications

Determining whether to file a variation or a new application hinges on the nature and impact of proposed changes to the product. Key decision factors include:

  • The extent of modifications: Minor changes such as formulation adjustments might qualify for a variation, while significant alterations like a new intended use generally require a new application.
  • The regulatory classification: Novel indications or changes that alter the risk profile will usually necessitate a full reassessment under a new application route.

Justifying Bridging Data

Bridging data, or the leveraging of existing data to support new applications or indications, is crucial in saving resources and time but must be well-justified:

  • Clearly articulate how existing data applies to the new context, ensuring that it encompasses similar populations and relevant endpoints.
  • Provide comprehensive evidence demonstrating that the safety and efficacy profiles are preserved under the new conditions or uses.

Collaborative Responsibilities

Understanding the governance structure in diagnostics-pharmaceutical collaborations can streamline the regulatory pathway. Responsibilities typically manifest in the following roles:

Pharmaceutical Company Roles

The pharmaceutical partner is generally accountable for:

  • Management of clinical trials associated with drug efficacy and safety.
  • Regulatory submissions concerning the pharmaceutical aspects.
  • Post-market surveillance of the drug.

Diagnostic Company Roles

In contrast, the diagnostic enterprise usually oversees:

  • Development of the companion diagnostic including clinical validation studies.
  • Compliance with device regulations, including quality system implementations.
  • Post-market performance and pharmacovigilance related to the diagnostic device.

Effective Communication Strategies

Establishing strong communication channels between regulators, pharmaceutical, and diagnostic companies is instrumental for success:

  • Regular updates through meetings and reports help in aligning expectations and clarifying responsibilities.
  • Use of common language and definitions to articulate complex technical terms ensures all stakeholders are on the same page.

Practical Tips for Interaction with RA Teams

Effectively engaging with regulatory authorities requires diligence and proactive strategies, including:

  • Prepare well for pre-submission meetings, focusing on presenting a cohesive narrative that outlines the clinical and developmental pathway.
  • Create an internal cross-functional team to ensure that all parts of the product development reflect the regulatory strategy.
  • Monitor legislation and guideline changes that could impact both the pharmaceutical and in vitro diagnostic product landscapes.
See also  Labeling and IFU Alignment Between Drug and Companion Diagnostic

Conclusion

The convergence of pharmaceuticals and diagnostics brings forth both opportunities and challenges that regulatory affairs teams must navigate with keen attention. By understanding the regulatory frameworks, fostering collaborative governance, and ensuring comprehensive documentation, organizations can position their products for seamless market entry and sustained compliance. Grasping and implementing the elements detailed in this guide will provide a foundational comprehension of the complexity inherent in pharma-diagnostic partnerships, thereby aiding in efficient regulatory navigation.