Medicare’s opioid risk-management rules don’t wait for a routine medication review. CMS (the federal agency that runs Medicare) requires Part D drug plans to flag a patient for mandatory case management the moment certain thresholds are crossed — a given daily opioid dose, combined with multiple prescribers and multiple pharmacies. It doesn’t matter how clean the rest of that person’s medication record looks. A pharmacy’s auto-clear policy — a rule that lets attestations close automatically without a pharmacist’s review — encodes a smaller version of the same idea: certain drug classes, opioids among them, are excluded from automatic clearance no matter how clean an attestation otherwise looks.
Here’s what CMS’s rule actually requires, how a pharmacy-level exclusion mirrors its shape, and exactly where that comparison has to stop.
CMS runs a separate, mandatory override layer for opioid risk
Standard eligibility for Medicare Part D’s Medication Therapy Management (MTM) program is based on how many chronic conditions a patient has, plus a drug-cost threshold. A separate program runs alongside it: the Drug Management Program, required by a 2016 law called CARA. It’s tied into CMS’s Overutilization Monitoring System, which tracks opioid and benzodiazepine use across the program. Under it, plan sponsors must identify and case-manage any patient who crosses specific opioid or benzodiazepine overuse thresholds — whether or not that patient meets standard MTM eligibility at all (CMS, 2019 Part D Drug Management Program Policy Guidance, Nov. 20, 2018; HHS CARA guidance, same date).
- Standard MTM eligibility is usually based on a count of chronic conditions plus a drug-cost threshold.
- Drug Management Program case-management rules are instead based on opioid dose, number of prescribers, and number of dispensing pharmacies — commonly described as roughly 90 morphine-milligram-equivalents (a standard way of measuring opioid dose) a day, with three or more prescribers and three or more pharmacies.
- A beneficiary can be flagged for case management under this program whether or not they meet standard MTM eligibility criteria.
- This requirement comes from the 2016 Comprehensive Addiction and Recovery Act (CARA) — not from the MTM program’s own rules.
A pharmacy’s own auto-clear rule draws a similar line
ConfirmMyMeds’s pharmacy console has an auto-clear policy that only the pharmacist-in-charge can turn on. It lets a clean, unescalated patient attestation close automatically instead of sitting in a human review queue. That policy always carries a fixed exclusion list — anticoagulants (blood thinners), insulin, opioids, and immunosuppressants — and any class on that list is excluded from auto-clear regardless of how clean the attestation otherwise looks. The logic follows the same shape as CMS’s rule: certain drug classes always get a second look, no matter what the rest of the record suggests.
Same shape of rule, two different jobs — don’t mix them up
It’s easy to overstate this parallel, so here’s exactly where it stops. CMS’s Drug Management Program governs an earlier decision: who gets offered case management, which can include locking a patient to one prescriber or one pharmacy, before any medication review has happened. Auto-clear governs a later decision: which already-submitted patient attestations still get a pharmacist’s eyes despite looking clean. These are different systems. They run at different points in the workflow, built by different parties, for different purposes. There is no evidence that CMS’s criteria shaped this product’s exclusion list, and no claim here that auto-clear does anything resembling case management, prescriber lock-in, or pharmacy lock-in. The honest parallel is narrow: both systems separately decided that certain drug classes — opioids chief among them — don’t get to clear automatically just because the record looks clean.
CMS’s opioid program and a pharmacy’s auto-clear policy run at different points, in different workflows, built for different reasons — but both follow the same instinct: this drug class always gets a second look, no matter how clean everything else looks.
What this does and doesn’t claim
This isn’t a claim that ConfirmMyMeds’s auto-clear policy was built to comply with, or was shaped by, CMS’s Drug Management Program — no evidence supports that, and the two were compared here only for the shape of the rule, not a shared origin. It’s also not a claim that auto-clear does anything CMS’s program does: it doesn’t case-manage a patient, it doesn’t lock a patient to a prescriber or pharmacy, and it has no connection to the Overutilization Monitoring System or any CMS reporting pathway. What the exclusion list actually does is narrower and procedural — it keeps a pharmacist’s attention on a fixed set of higher-risk drug classes within this product’s own review queue, and nothing about that queue, or this product generally, has outcome data showing it improves opioid safety, overutilization detection, or any other result.
ConfirmMyMeds is a working application. It asks the patient to confirm their clinic’s medication list before the appointment — outside the portal, with the bottles in hand — and returns what they confirmed, what they flagged, and what they never started, timestamped and attributed. It never writes to your record; the clinician decides what goes in the chart and what to do about a gap. We have no outcome data and make no claims about adherence or affordability outcomes. We’re looking for clinics to help us learn where it fails.
This article discusses Medicare Part D’s opioid risk-management program and a pharmacy software setting in general terms. It isn’t medical, legal, or regulatory-compliance advice.