Close

FDA Wraps Up The REMS Standards For Prescription Medicines

Note* - All images used are for editorial and illustrative purposes only and may not originate from the original news provider or associated company.

Related stories

Billerud Introduces New Pharmaceutical Packaging Option

Billerud has officially introduced PharmaKraft, a specialized fibre-based packaging...

AstraZeneca Advances AI Drug Discovery Deal with insitro

AstraZeneca has inked a billion-dollar AI drug discovery partnership...

Managing Quality and Regulatory Risks in Pharmaceutical Technology Transfer

Technology transfer moves more than manufacturing instructions. It moves process knowledge, supplier dependencies, labeling requirements, packaging specifications, and the evidence needed to demonstrate control. For medical device manufacturers, including those supporting drug-device combination products, these interfaces can become recurring sources of compliance gaps during site transitions, acquisitions, and remediation. The central problem is often not a missing procedure. It is a quality system that allows connected activities to change independently. A label revision may be approved while packaging artwork, supplier instructions, or production-system data still reflect an obsolete version. Staying inspection-ready requires manufacturers to manage these dependencies as one controlled system. Why Compliance Gaps Keep Recurring Findings are treated as documentation defects Revising a procedure can resolve an immediate discrepancy without changing the behavior that caused it. If unclear decision rights, weak escalation, or ineffective training remain, the same failure may surface elsewhere. Corrective and preventive action should distinguish the observed finding from its underlying cause and establish how effectiveness will be demonstrated. Ownership is divided across connected functions Quality, Regulatory Affairs, labeling, packaging engineering, operations, suppliers, and digital-system owners often maintain separate workflows. Each team may complete its assigned task while an interface remains uncontrolled. For example, changing an instruction for use can affect packaging configuration, translations, technical documentation, inventory disposition, and release controls. Transitions expose unresolved weaknesses Acquisitions and site transfers can introduce conflicting procedures, incomplete knowledge transfer, or different assumptions about validated processes. Regulatory changes add further demands. When these events coincide with CAPA or change-control backlogs, teams may prioritize administrative closure over risk reduction. Without a coordinated impact assessment, local fixes can create new gaps downstream. Establish the Regulatory Baseline Inspection readiness starts with knowing which requirements apply to the product, activity, and market. Pharmaceutical, device, and combination-product obligations are not interchangeable; transfer planning should identify the applicable requirements rather than assume one quality framework covers every operation. According to FDA’s Quality Management System Regulation overview and FAQs, the QMSR became effective on February 2, 2026, incorporates ISO 13485:2016 by reference, and introduced the updated device inspection process under Compliance Program 7382.850. ISO 13485 certification does not exempt a manufacturer from FDA inspection or guarantee compliance with FDA requirements. For devices marketed in the European Union, Regulation (EU) 2017/745, Annex I, Section 23, provides the primary requirements for information supplied with devices, including labels and instructions for use. Teams should assess the applicable provisions alongside relevant language, product-specific, and market requirements. A labeling review should therefore evaluate required content and consistency with the device’s intended purpose and supporting documentation—not merely artwork accuracy. How to Identify the Real Gaps Begin with a cross-functional assessment that follows actual product and information flows. Select representative transfers, label changes, supplier changes, and CAPAs, then trace each from initiation through implementation and effectiveness review. Map dependencies: Identify affected specifications, suppliers, packaging components, systems, validation activities, and training. Compare records with practice: Check whether approved procedures match what operators and reviewers actually do. Test traceability: Follow a requirement through technical documentation, labeling, production instructions, and release evidence. Examine recurrence: Look for repeated deviations, reopened actions, overdue changes, and findings shared across sites. Assess capacity: Determine whether qualified owners have enough time and authority to complete corrective work. Prioritize gaps by potential patient or user harm, regulatory impact, likelihood of recurrence, and detectability. Document the rationale; an old overdue item is not automatically more important than a newly identified high-risk weakness. Align Quality, Labeling, Packaging, and Change Control Create a coordinated remediation plan with one accountable owner for each action, named contributors, acceptance criteria, and required evidence. Separate immediate containment from systemic correction. Containment might prevent obsolete labels from being issued; correction might redesign approval and implementation controls so obsolete versions cannot return. Use change control as the integration point. Before approval, evaluate effects on regulatory submissions or notifications, technical documentation, supplier controls, packaging performance, validation, electronic master data, inventory, and training. Record both identified impacts and justified decisions that particular activities are unaffected. During technology transfer, define readiness gates before production or release responsibilities move. These should address the transfer of process knowledge, acceptance criteria, receiving-site capability, required qualification or validation, approved documents, and personnel competence. The appropriate evidence depends on the product and process; a generic checklist cannot replace a documented assessment. Finally, verify implementation where the work happens. Confirm that current instructions are available, suppliers received approved requirements, systems contain correct versions, and affected personnel can perform their tasks. A signed approval is not evidence that every downstream change took effect. Mistakes That Undermine Inspection Readiness Closing CAPAs on task completion alone: Effectiveness checks should test whether the underlying failure has been controlled. Updating labels in isolation: Assess packaging, supplier, system, documentation, and inventory consequences. Counting closures instead of evidence: Dashboards need defensible records behind their status indicators. ...
- Advertisement -

The FDA’s Final Guidance on REMS programmes for prescription medications, has just been published. The document is officially titled Format and Content of a REMS Document: Guidance for Industry.

The FDA may demand a risk management strategy known as REMS, or Risk Evaluation and Mitigation Strategy, to make sure that the advantages of particular medications outweigh their hazards. All prescription medications have dangers and advantages; this is the reason why a prescription is necessary in the first place. While it comes to product liability, these risks and benefits are most frequently controlled by telling doctors about established and fairly identifiable dangers so they can assess those risks and advantages when treating patients.

A REMS is used when the FDA determines that a more organised approach is necessary for a particular medicine. The FDA has the authority to impose extra conditions to ensure the safe use of medications that have substantial health hazards. A REMS may call for the creation of materials for dissemination to patients or pharmacists by the drug manufacturer or extra communication with healthcare providers regarding specific safety concerns. For prescribers or distributors, it can necessitate further education or licensing, or it might even call for particular therapeutic actions, including specialist patient monitoring or specialised consent. It might also call for a mix of all of the aforementioned or even more.

The idea is that a REMS can take many different forms, but safety is always the main priority. In accordance with the FDA’s Structured Product Labeling, or SPL format, the new guidance aims to make sure that REMS papers are unambiguous, comprehensible, and provided in a uniform style. The guidance also offers current suggestions for a REMS document for a prescription medicine, including biologics, in terms of both format and content. The guidance itself is unenforceable and does not have legal effect, just like every other FDA guidance. However, an FDA-adopted REMS is a formal FDA mandate, similar to FDA-required product labelling in terms of the law. As lawyers who specialise in product liability cases, they are concerned because a REMS can affect a maker of prescription drugs’ potential culpability in at least two ways.

First, the sufficiency of the drug’s warnings is virtually always contested in product liability claims involving prescription drugs. Every prescription drug must have the FDA-mandated labelling, but a REMS may occasionally call for extra warnings on a specific danger, providing prescribers with yet more knowledge and the manufacturer with more security. The finest illustration one could find is in Nelson v. Biogen Idec, a case from a few years ago. Before obtaining the prescribed medication in Nelson, each patient has to accept receiving a medication guide under a REMS. The manufacturer won summary judgement on the plaintiff’s failure-to-warn claim because the manufacturer had supplied a thorough set of warnings on the precise risk that the plaintiff claimed to have experienced.

Second, as it has already been mentioned, the REMS Guidance document is not binding law; however, a REMS that has been approved by the FDA is required by federal law and is therefore preemptive law, as required by even the most stringent interpretation of the Supremacy Clause in the Supreme Court’s Albrecht decision. Therefore, any state law requirements that conflict with a REMS should be preempted, such as any additional warnings required by a state-law product liability case. One should keep an eye on this. REMS are specifically designed to address safety in the context of particular risks; they are created especially for specific drugs or types of drugs, and they place specific limitations and restrictions on the medication and use of those drugs. Preemption should be used when a state obligation clashes with a REMS.

Preemption and REMS are uncharted territory. Only the non-product liability ruling in PhRMA v. McClain, 2022, which hints that safety-related claims may very well be prohibited while rejecting the preemption argument in that case, has been considered a post-Albrecht preemption decision using REMS.

Never miss a pharmaceutical headline

The pharmaceutical industry moves fast – stay on top of it with our must - read briefings.

  • The top pharma and life sciences stories, straight to your inbox
  • The biggest news, features, interviews, and analysis
  • Dedicated coverage of the key developments driving the global pharmaceutical sector

Subscribe

- Never miss a story with notifications

- Gain full access to our premium content

- Browse free from any location or device.

Media Packs

Expand Your Reach With Our Customized Solutions Empowering Your Campaigns To Maximize Your Reach & Drive Real Results!

– Access the Media Pack Now

– Book a Conference Call

– Leave Message for Us to Get Back

Latest stories

Related stories

Billerud Introduces New Pharmaceutical Packaging Option

Billerud has officially introduced PharmaKraft, a specialized fibre-based packaging...

AstraZeneca Advances AI Drug Discovery Deal with insitro

AstraZeneca has inked a billion-dollar AI drug discovery partnership...

Managing Quality and Regulatory Risks in Pharmaceutical Technology Transfer

Technology transfer moves more than manufacturing instructions. It moves process knowledge, supplier dependencies, labeling requirements, packaging specifications, and the evidence needed to demonstrate control. For medical device manufacturers, including those supporting drug-device combination products, these interfaces can become recurring sources of compliance gaps during site transitions, acquisitions, and remediation. The central problem is often not a missing procedure. It is a quality system that allows connected activities to change independently. A label revision may be approved while packaging artwork, supplier instructions, or production-system data still reflect an obsolete version. Staying inspection-ready requires manufacturers to manage these dependencies as one controlled system. Why Compliance Gaps Keep Recurring Findings are treated as documentation defects Revising a procedure can resolve an immediate discrepancy without changing the behavior that caused it. If unclear decision rights, weak escalation, or ineffective training remain, the same failure may surface elsewhere. Corrective and preventive action should distinguish the observed finding from its underlying cause and establish how effectiveness will be demonstrated. Ownership is divided across connected functions Quality, Regulatory Affairs, labeling, packaging engineering, operations, suppliers, and digital-system owners often maintain separate workflows. Each team may complete its assigned task while an interface remains uncontrolled. For example, changing an instruction for use can affect packaging configuration, translations, technical documentation, inventory disposition, and release controls. Transitions expose unresolved weaknesses Acquisitions and site transfers can introduce conflicting procedures, incomplete knowledge transfer, or different assumptions about validated processes. Regulatory changes add further demands. When these events coincide with CAPA or change-control backlogs, teams may prioritize administrative closure over risk reduction. Without a coordinated impact assessment, local fixes can create new gaps downstream. Establish the Regulatory Baseline Inspection readiness starts with knowing which requirements apply to the product, activity, and market. Pharmaceutical, device, and combination-product obligations are not interchangeable; transfer planning should identify the applicable requirements rather than assume one quality framework covers every operation. According to FDA’s Quality Management System Regulation overview and FAQs, the QMSR became effective on February 2, 2026, incorporates ISO 13485:2016 by reference, and introduced the updated device inspection process under Compliance Program 7382.850. ISO 13485 certification does not exempt a manufacturer from FDA inspection or guarantee compliance with FDA requirements. For devices marketed in the European Union, Regulation (EU) 2017/745, Annex I, Section 23, provides the primary requirements for information supplied with devices, including labels and instructions for use. Teams should assess the applicable provisions alongside relevant language, product-specific, and market requirements. A labeling review should therefore evaluate required content and consistency with the device’s intended purpose and supporting documentation—not merely artwork accuracy. How to Identify the Real Gaps Begin with a cross-functional assessment that follows actual product and information flows. Select representative transfers, label changes, supplier changes, and CAPAs, then trace each from initiation through implementation and effectiveness review. Map dependencies: Identify affected specifications, suppliers, packaging components, systems, validation activities, and training. Compare records with practice: Check whether approved procedures match what operators and reviewers actually do. Test traceability: Follow a requirement through technical documentation, labeling, production instructions, and release evidence. Examine recurrence: Look for repeated deviations, reopened actions, overdue changes, and findings shared across sites. Assess capacity: Determine whether qualified owners have enough time and authority to complete corrective work. Prioritize gaps by potential patient or user harm, regulatory impact, likelihood of recurrence, and detectability. Document the rationale; an old overdue item is not automatically more important than a newly identified high-risk weakness. Align Quality, Labeling, Packaging, and Change Control Create a coordinated remediation plan with one accountable owner for each action, named contributors, acceptance criteria, and required evidence. Separate immediate containment from systemic correction. Containment might prevent obsolete labels from being issued; correction might redesign approval and implementation controls so obsolete versions cannot return. Use change control as the integration point. Before approval, evaluate effects on regulatory submissions or notifications, technical documentation, supplier controls, packaging performance, validation, electronic master data, inventory, and training. Record both identified impacts and justified decisions that particular activities are unaffected. During technology transfer, define readiness gates before production or release responsibilities move. These should address the transfer of process knowledge, acceptance criteria, receiving-site capability, required qualification or validation, approved documents, and personnel competence. The appropriate evidence depends on the product and process; a generic checklist cannot replace a documented assessment. Finally, verify implementation where the work happens. Confirm that current instructions are available, suppliers received approved requirements, systems contain correct versions, and affected personnel can perform their tasks. A signed approval is not evidence that every downstream change took effect. Mistakes That Undermine Inspection Readiness Closing CAPAs on task completion alone: Effectiveness checks should test whether the underlying failure has been controlled. Updating labels in isolation: Assess packaging, supplier, system, documentation, and inventory consequences. Counting closures instead of evidence: Dashboards need defensible records behind their status indicators. ...

State of API & Peptide CDMO Capacity

Pharmaceutical companies planning peptide or complex small-molecule launches are...

Subscribe

- Never miss a story with notifications

- Gain full access to our premium content

- Browse free from any location or device.

Media Packs

Expand Your Reach With Our Customized Solutions Empowering Your Campaigns To Maximize Your Reach & Drive Real Results!

– Access theMedia Pack Now

– Book a Conference Call

– Leave Message for Us to Get Back

Translate »