FDA REMS Programs — Regulatory Reference

FDA Risk Evaluation and Mitigation Strategies (REMS) impose strict controls on how restricted drug information is accessed, shared, and acted upon. When AI agents query dispensing systems, prescription records, or patient eligibility data tied to REMS-controlled medications, those accesses fall within the ETASU (Elements to Assure Safe Use) compliance boundary. REMS programs require that access to controlled medication data be limited to certified prescribers, certified pharmacies, and enrolled patients. AI agents must be identifiable, their access bounded to authorized roles, and every decision logged. AutoPIL enforces this by classifying REMS medication data at CRITICAL sensitivity and binding agent identities to applicable ETASU certification records before any retrieval occurs.

REMS requirements apply whenever an organization dispenses, distributes, or manages patient data for drugs with an active REMS program — currently over 60 drug products including isotretinoin (iPLEDGE), clozapine, and certain opioid formulations. If your AI agent touches dispensing workflows, clinical decision support, or patient outreach for any REMS-covered drug, REMS controls apply. This includes hospital pharmacy systems, specialty pharmacy platforms, EHR-integrated agents, and automated prior authorization tools. The threshold is contact with restricted distribution data, not just the act of dispensing. Health systems and pharmacy benefit managers building agentic workflows should evaluate REMS applicability at the data source level, not only at the point of dispensing.

Elements to Assure Safe Use (ETASU) are the mandatory conditions a REMS program may impose to ensure a drug's benefits outweigh its risks. ETASU can require prescriber certification, pharmacy enrollment, patient registries, required lab monitoring, and controlled dispensing through designated facilities only. For AI systems, ETASU creates a hard access boundary: an agent cannot legitimately retrieve or act on REMS-controlled dispensing data unless the downstream workflow satisfies all applicable ETASU conditions. AutoPIL maps ETASU compliance obligations directly into policy enforcement — agent registry entries can be bound to certification status, and policies can deny retrieval at the source level when certification is absent or expired, producing an audit record that constitutes ETASU compliance evidence.

AutoPIL enforces pre-retrieval access control on REMS-controlled medication data before it enters an agent's context window. Two policies address this directly: PHM-FDA-REMS-001 (REMS Medication Boundary) classifies restricted drug and dispensing data at CRITICAL sensitivity, and PHM-FDA-ETASU-001 (ETASU Compliance Evidence) ties agent access to certification and registry requirements. Every evaluation — allow or deny — is written to a tamper-evident cryptographic audit chain that can serve as compliance evidence during FDA inspection or audit. The agent registry captures agent identity, owner team, and governing policy at registration time, so access decisions are traceable to a specific certified workflow rather than an anonymous process.

FDA can pursue civil money penalties, injunctions, and consent decrees for REMS non-compliance. Under 21 U.S.C. § 355-1, failure to comply with REMS requirements — including failure to maintain required records or distribute through unapproved channels — can trigger Warning Letters, mandatory corrective action plans, and in serious cases, product market withdrawal. For organizations deploying AI agents, the enforcement risk is compounded: if an agent retrieves and acts on REMS-controlled data outside authorized channels, FDA may treat that as a REMS distribution violation even if the underlying dispensing transaction was compliant. Maintaining a documented, auditable record of every agent access decision is the primary mitigation against this exposure.