DEA Controlled Substance Rules (Healthcare) — Regulatory Reference

Under 21 CFR Parts 1304 and 1311, organizations must maintain strict access controls and tamper-evident audit records for all controlled substance data. For AI agent deployments, this means any agent that can read, process, or route Schedule I–V prescription records must be operating under documented, role-scoped access policies — and every access decision must produce an auditable record. The regulations do not distinguish between human and automated access; the recordkeeping obligation follows the data. Organizations deploying clinical decision support or prescribing workflow agents need to demonstrate that those agents cannot access controlled substance records outside their authorized clinical function.

21 CFR Part 1311 applies to any electronic system that creates, transmits, or processes electronic prescriptions for controlled substances. If an AI agent assists a prescriber in drafting, routing, or validating a controlled substance prescription — even as a step in a larger workflow — the audit trail requirements under Part 1311 apply to that system. The rule requires logical access controls, an auditable record of every prescription event, and protection against unauthorized modification. Organizations running AI-assisted prescribing tools must ensure the agent's access and output events are captured in a tamper-evident log that satisfies the EPCS audit expectations.

Controlled substance prescription records sit at the highest sensitivity tier under any defensible access control scheme. Schedule II records carry the strictest separation requirement under 21 CFR 1304 — they must be maintained separately from other prescription records and are subject to two-year minimum retention. For AI agent governance purposes, this means controlled substance data sources should be classified at CRITICAL sensitivity, with access limited to agents operating in explicitly authorized clinical roles. Billing agents, administrative agents, and general-purpose query agents should be denied access at the data layer, not just at the application layer — because retrieval-time enforcement is the only control that prevents the data from entering an agent's context window.

AutoPIL enforces access policy before controlled substance data reaches an AI agent's context window. Source registry entries for Schedule I–V prescription data are classified at CRITICAL sensitivity. Policy HC-DEA-1304-001 defines the sensitivity floor; policy HC-DEA-1311-001 enforces EPCS audit trail requirements. Per-role rules allow clinical agents access while denying billing and administrative agents — enforced at retrieval time, not application logic. Every access decision writes to a cryptographic audit chain that satisfies the tamper-evident record requirement under 21 CFR 1311. The audit log captures agent identity, source accessed, policy applied, allow/deny outcome, and timestamp — producing the documented access record DEA audits require.

DEA enforcement under the Controlled Substances Act can include civil penalties, revocation of DEA registration, and in cases of willful noncompliance, criminal referral. Registration revocation is operationally catastrophic for any dispensing or prescribing organization. Beyond DEA, uncontrolled AI agent access to controlled substance records can trigger parallel liability under state prescription monitoring program statutes and HIPAA (as PHI). Regulators increasingly treat automated system access as equivalent to human access — meaning an agent that reads Schedule II records without documented authorization is a compliance violation regardless of whether a human directed it. The risk is compounded by the tamper-evident record requirement: if the audit log can be altered, the entire EPCS compliance posture is undermined.