On January 20, 2023, the Drug Enforcement Administration (DEA’s) issued a Guidance Document reiterating DEA’s long-held position regarding the detection and reporting of suspicious orders. Specifically, DEA “clarified” that “neither the Controlled Substance Act (CSA) nor [DEA] regulations establish quantitative thresholds or place limits on the volume of controlled substances DEA registrants can order and dispense.”
Why the need for a clarification?
On June 5, 2020, the Office of Management and Budget (OMB) received an Interim Final Rule from the Drug Enforcement Administration titled, Implementation of the SUPPORT Act: Dispensing and Administering Controlled Substances for Medicated-Assisted Treatment. This rule implements certain provisions of the SUPPORT Act “relating to the expansion of medication-assisted treatment providers and to the delivery of a controlled substance by a pharmacy to a practitioner.”
On January 20, 2020, the Government Accountability Office (GAO) released its report Drug Control: Actions Needed to Ensure Usefulness of Data on Suspicious Opioid Orders. The report, mandated by Congress in the SUPPORT Act, focuses almost exclusively on the need for the Drug Enforcement Administration (DEA) to beef up its capabilities for analyzing the vast amount of data provided to DEA by registrants. GAO’s investigation revealed, among other things, that DEA conducted “limited proactive and robust analysis of industry reported data” and that DEA did not have the appropriate data governance structure in place to manage drug transaction data.
Note: The following is my best guess for what to expect in the coming year regarding controlled substance compliance obligations. I have relied on publicly available information, my experience and expertise with all things involving pharmaceutical controlled substance, and a Magic 8 Ball in creating the list below.
Suspicious Orders
This is the year (I think) that DEA will publish a Notice of Proposed Rule Making (NPRM) updating 1301.74(b). While industry is anxiously awaiting the new regulations, I fear that many will be disappointed. My best guess is that the new regulations will be more about changing the process for reporting suspicious orders and less about guidance for industry on the metrics to use for detecting suspicious orders. This is in part because Congress recently codified the existing definition of suspicious orders that has been in DEA’s regulations for decades, which takes away a great deal of DEA’s interpretative authority and discretion. There is also an argument to be made that DEA would prefer suspicious order guidance and definitions to be vague, providing the agency significant enforcement discretion.
On October 23, 2019, the Drug Enforcement Administration (DEA) announced the launch of its Suspicious Orders Report System (SORS) Online, a portal allowing for the centralized reporting of suspicious orders, as required by the SUPPORT ACT.
According to DEA’s announcement, 12 registrant business activity classes will utilize this reporting system:
Reverse distributors and exporters are excluded from the requirement.
Is “Suspicious Order” about to be defined?
The recently-released DOJ OIG Review of the Drug Enforcement Administration’s Regulatory and Enforcement Efforts to Control the Diversion of Opioids has met with extensive media coverage focused on the sexier aspects of the story. What did DEA do or not do to stem the opioids crisis? What internal battles may have led DEA to drop the ball in some aspects of the response? These are important questions, but they have been well-covered.
Instead, we are going to focus on a handful of the nine recommendations (listed below) made by the IG and DEA’s and ODAG’s responses.
As required by the “SUPPORT for Patients and Communities Act” (Public Law 115-217), DEA just announced that it has implemented a new tool to provide drug manufacturers and distributors with access to anonymized ARCOS information.
This an enhancement to DEA’s existing tool that previously provided very limited ARCOS information. The new functionality in the tool