Medicare’s 2019 drug plan rules put four controls on the path to the pharmacy, fed by data from elsewhere
CMS’s April 2018 Part D package checked the prescriber, the patient and the quantity at the pharmacy counter, and changed the message that carried the prescription there. Each check depended on data a health system, a plan or CMS held somewhere else.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
CMS’s April 2018 Part D package checked the prescriber, the patient and the quantity at the pharmacy counter, and changed the message that carried the prescription there. Each check depended on data a health system, a plan or CMS held somewhere else.
- The week On Monday, April 2, 2018, the Centers for Medicare & Medicaid Services released two documents that set the rules for Medicare Advantage and Part D drug plans in 2019.
- The prescriber: a list replaced an enrollment requirement Before April 2018, CMS’s approach to prescriber oversight in Part D rested on enrollment.
- The patient: drug management programs added a beneficiary-level limit The second part of the package concerned the patient rather than the prescriber.
- The quantity: safety edits set thresholds at the counter The third part came from the Call Letter rather than the rule.
- The message: a SCRIPT update without a transition period The fourth part concerned the channel rather than the decision.
- Why the pharmacy transaction attracted all four controls The four parts came from different authorities.
- How the controls fell on different organizations The effects of the package depended on what an organization owned.
- Objections: plan burden, clinical judgment and data limits Three objections deserve a direct answer.
- What a health system technology leader could check The four parts translate into checks that a health system can run without waiting for a plan or a regulator.
- With hindsight Medicare’s preclusion list took effect in stages.
The week
On Monday, April 2, 2018, the Centers for Medicare & Medicaid Services released two documents that set the rules for Medicare Advantage and Part D drug plans in 2019. One was a final rule, CMS-4182-F, covering policy and technical changes to both programs. The other was the 2019 Rate Announcement and Call Letter, which sets payment methods and gives plans operational guidance for the coming year.
CMS’s fact sheet on the final rule said it would save an estimated $295 million a year for the Medicare program over five years, 2019 through 2023. It framed the rule as part of the agency’s “Patients over Paperwork” initiative. A good part of the rule eased requirements on plans. It dropped the “meaningful difference” limits on plan variety, narrowed the definition of marketing and let plans deliver some documents electronically.
Three provisions in the package changed how a prescription is checked when it reaches a pharmacy. The first replaced a requirement that every prescriber of Part D drugs enroll in Medicare. In its place CMS said it would compile a “Preclusion List” of prescribers, individuals and entities. These were people revoked from Medicare and under a reenrollment bar, or people whose conduct could have led to revocation had they been enrolled. In either case CMS had to find the conduct “detrimental to the best interests of the Medicare program.” Plans would be required to deny payment for claims tied to anyone on the list.
The second implemented section 704 of the Comprehensive Addiction and Recovery Act of 2016, known as CARA. The fact sheet said CARA required CMS to set up, through regulation, a framework under which Part D sponsors could run drug management programs. Under them, a sponsor could limit an at-risk beneficiary’s access to coverage for frequently abused drugs, beginning with the 2019 plan year. CMS said it would designate opioids and benzodiazepines as frequently abused drugs.
Those programs would be integrated with CMS’s existing Overutilization Monitoring System, or OMS. The fact sheet said the clinical guidelines for flagging a potentially at-risk beneficiary were based on opioid use from multiple prescribers or multiple pharmacies. A sponsor could limit such a beneficiary to selected prescribers or pharmacies, a step known as lock-in. It could also apply beneficiary-specific point-of-sale claim edits. It could do neither until it had carried out case management with the prescribers, and the beneficiary could state preferences for prescribers and pharmacies. Beneficiaries with active cancer-related pain, in hospice or long-term care, or receiving palliative or end-of-life care were exempt.
The third updated the electronic prescribing standard for the Part D program. CMS adopted version 2017071 of the National Council for Prescription Drug Programs SCRIPT standard, beginning January 1, 2020. The fact sheet noted that the version it replaced, 10.6, had been adopted on November 1, 2013.
The Call Letter added a set of opioid policies that worked through the same pharmacy claim. CMS said it expected all Part D sponsors to implement a hard safety edit limiting initial opioid fills for acute pain to no more than a 7 days supply for patients new to opioids. It expected all sponsors to implement an opioid care coordination edit at 90 morphine milligram equivalents (MME) a day. When that edit fired, the pharmacist was to consult the prescriber, document the discussion and use an override code if the prescriber confirmed intent. Sponsors could also set hard edits at 200 MME or more. CMS also expected soft edits warning pharmacists of duplicate opioid therapy and of opioids taken with benzodiazepines.
The Call Letter explained the two kinds of edit in a footnote. A hard reject “stops the pharmacy from processing a claim unless or until an override is entered or authorized by a plan representative.” A soft reject stops it until the pharmacist enters a drug utilization review code. CMS recommended excluding the same groups of patients from these edits, and said access to medication-assisted treatment such as buprenorphine should not be affected. It also said all Part D sponsors were expected to have “a documented, written strategy” for addressing opioid overutilization.
The documents had a history. The Advance Notice for 2019 had been posted in two parts, on December 27, 2017 and February 1, 2018, when the draft Call Letter was also posted. CMS took comments on them through March 5, 2018. The OMS dated from July 2013, and CMS had revised its criteria for 2018 to use a 90 MME threshold over six months, paired with counts of prescribers and pharmacies. In the Call Letter, CMS reported that beneficiaries meeting its earlier outlier criteria had fallen from 29,404 in 2011 to 6,931 in 2017.
Medicare drug policy can look like a matter for plan actuaries and pharmacy benefit managers. We read the April 2018 package as an architecture decision. Several unrelated policy goals were assigned to one technical moment: the few seconds in which a pharmacy claim is adjudicated. Fraud control, opioid safety and prescriber oversight all moved to that point. So did the message format that carries the prescription there.
For a health system, that choice mattered because the health system was on both sides of the claim. Its clinicians wrote the prescriptions. Its outpatient and specialty pharmacies, where it had them, submitted the claims. Some systems also sponsored Medicare Advantage plans with drug coverage, and those plans ran the edits. An ambulatory network felt the same effects with fewer moving parts. In each case, a rule written for plans ended up shaping work at the prescriber’s desk and the pharmacy counter.
We take the package in four parts. Three parts are questions the claim now had to answer, and the fourth governs the message that brings the prescription to the counter. Together they cover what the April 2 documents changed at the point of sale and on the way to it:
- The prescriber: whether the person who wrote the prescription was allowed to have it paid for, which the Preclusion List decided.
- The patient: whether this beneficiary had been limited to particular prescribers or pharmacies, which a drug management program decided.
- The quantity: whether the days supply and daily dose crossed a threshold that required a pharmacist or a plan to intervene, which the Call Letter’s safety edits decided.
- The message: what format the prescription traveled in between prescriber and pharmacy, which the SCRIPT 2017071 update decided.
Our argument is that the claim was a sound place to enforce each rule, but that each rule depended on data produced somewhere else. The list came from CMS’s enrollment and revocation records. The beneficiary limits came from case management and notices. The thresholds depended on accurate days supply and dose information, and the message depended on software in every prescriber’s electronic health record. A health system that saw only the rejected claim would miss where the failure began. After the four parts, we look at why the pharmacy transaction attracted all four controls, how the effects differed by type of organization, the main objections, and what a leader could check.
The prescriber: a list replaced an enrollment requirement
Before April 2018, CMS’s approach to prescriber oversight in Part D rested on enrollment. A final rule of May 23, 2014 had required prescribers of Part D drugs to enroll in Medicare or opt out. CMS had announced phased-in enforcement and said full enforcement would be delayed until January 1, 2019. The final rule repeated the reason the proposed rule had given: based on internal CMS data as of July 2016, approximately 420,000 prescribers, or 35 percent of the 1.2 million who prescribed Part D drugs, had yet to enroll or opt out. In its burden estimates the final rule revised the count of unenrolled prescribers to approximately 340,000. From January 1, 2016, the regulations required plans to give a beneficiary a 3-month provisional supply and written notice when a claim would otherwise be rejected for an unenrolled prescriber. The idea was to give the patient time to find a prescriber who would enroll.
The April 2018 rule abandoned that model. The final rule described the proposal it adopted as replacing the enrollment requirement “with a claims payment-oriented approach.” Instead of asking every prescriber to prove standing, CMS would name the small group who should not be paid. The fact sheet listed the two categories. The first was prescribers currently revoked, under a reenrollment bar, whose conduct CMS found detrimental. The second was people CMS could have revoked had they been enrolled, again on a detrimental-conduct finding.
What the regulation told plans to do
The final text of 42 CFR 423.120(c)(6) set out the mechanics. A Part D sponsor “must reject, or must require its PBM to reject, a pharmacy claim” for a drug prescribed by someone on the list. It must deny a beneficiary’s request for reimbursement on the same basis. And a sponsor could not submit a prescription drug event record to CMS without the prescriber’s active and valid individual National Provider Identifier. The prescriber also had to be off the list for the date of service.
That last clause tied the list to the plan’s own data submission to CMS as well as to the pharmacy transaction. A plan that paid a claim it should have rejected would also hold a drug event record it could not submit. The rule therefore gave plans a reason to check the list at adjudication rather than after the fact.
The rule built in notice before rejection. A sponsor could not reject a claim on preclusion grounds until it had given the beneficiary written notice. The notice had to reach the beneficiary “no later than 30 days after publication of the most recent preclusion list.” The sponsor also had to make reasonable efforts to notify the prescriber. CMS itself would send the prescriber a letter giving the reason for inclusion and explaining appeal rights under 42 CFR part 498. CMS kept discretion to leave someone off the list where beneficiary access to drugs would otherwise be impaired.
How the list would travel
Responding to comments, CMS said it would make the list available every 30 days via a secure server. It warned that a plan that failed to use the latest version was at risk of paying for prescriptions written by precluded prescribers. The agency put the burden of keeping current on the plan. CMS also said that, for dual-eligible beneficiaries, a Part D claim rejected because of the prescriber could not be covered by Medicaid with federal matching funds.
Medicare Advantage plans received a parallel rule. They would deny payment for items and services furnished by individuals and entities on the list. The list therefore reached beyond prescriptions to any service a precluded provider furnished to an enrollee.
Where the list met the health system
A health system’s first exposure was its own medical staff. A precluded clinician could still hold privileges or employment, because preclusion governs Medicare payment, not licensure. If that clinician kept prescribing, patients would receive notices from their plans and, later, rejections at the pharmacy. The health system would hear about it first through complaints, not through any feed of its own.
The second exposure was the system’s pharmacy. A pharmacy owned by the system would see the rejection at the counter, with a patient waiting. Its staff would need to know what a preclusion reject meant, how it differed from a formulary reject, and that the remedy lay with the prescriber, not the plan. The rule did not require the pharmacy to do anything new. Yet its workflow carried the consequences.
The third exposure applied only to systems that sponsored Medicare Advantage plans with drug coverage. Those plans had to download the list, load it into claims processing through their pharmacy benefit manager, send notices and track timing. That made the list a monthly data load with a compliance deadline attached.
What a credentialing file would need
Hospital credentialing and privileging files may record licensure, board certification, sanctions and exclusions. A preclusion decision is a different kind of fact. It concerns eligibility for Medicare payment through Medicare Advantage and Part D, and CMS communicates it to the clinician by letter. A credentialing office that checked only licensure boards and exclusion databases would not see it.
A simple addition to the file would close that gap. The medical staff bylaws or employment terms could ask clinicians to report any CMS revocation, reenrollment bar or preclusion notice. The office could then record the date, the reason given and any appeal. The point is not to discipline the clinician, which is a separate question. The point is to know in advance that patients will start receiving plan notices and pharmacy rejections.
In our reading, the enrollment model and the list model put the work in different places. Under enrollment, the prescriber did the work and the plan verified a status. Under the list, CMS did the work of identifying the few to exclude, and the plan did the work of applying it on time. For a health system, the change meant fewer enrollment chores for clinicians who never billed Medicare directly. It also meant that the signal of a problem would arrive as a claim rejection rather than as an enrollment gap the credentialing office could see in advance.
The patient: drug management programs added a beneficiary-level limit
The second part of the package concerned the patient rather than the prescriber. CARA gave Part D sponsors a new tool: limiting an at-risk beneficiary to particular prescribers or pharmacies. The April 2018 rule built the framework and, for 2019, left adoption to each sponsor. The final rule said that “although drug management programs are voluntary,” it codified a framework of requirements for sponsors that set them up.
How a beneficiary entered a program
The process began with data. CMS’s OMS identified potential at-risk beneficiaries using clinical guidelines and reported them to the sponsor. The final regulation set four tests for those guidelines. They had to be developed with stakeholder consultation and based on use from multiple prescribers or pharmacies, or on the level of use. They also had to be derived from expert opinion and Medicare data, and include a program size estimate. The Call Letter gave the 2018 OMS criteria in a footnote. They were an average daily dose of 90 MME or more over six months, with opioids from more than three prescribers and more than three pharmacies, or from more than five prescribers.
The footnote added a detail that mattered for health systems. “Prescribers associated with the same single Tax Identification Number (TIN) are counted as a single prescriber.” A patient seeing several clinicians in one group practice would count as seeing one prescriber. A patient whose care was split across practices billing under different tax identifiers would count as seeing several. How a health system organized its billing entities could therefore affect whether its patients appeared in the OMS reports.
Case management came before any limit
The regulation required the sponsor’s clinical staff to conduct case management for each potential at-risk beneficiary. Staff had to send prescribers written information that the patient met the guidelines, elicit information about the patient’s treatment, and make reasonable further attempts when prescribers did not respond. Only after that could the sponsor decide the beneficiary was at risk.
For a health system’s clinicians, this meant letters and calls from plans about specific patients. The letters asked whether the prescriptions were appropriate and whether the patient fell into an exempt group. A clinic that had no process for routing those inquiries would lose them in general correspondence. The regulation let plans act on limited prescriber response in some cases, so an unanswered letter could still end in a limit.
Notices, preferences and the limit itself
The regulation required an initial notice to the beneficiary. It had to request, within 30 days, any information the beneficiary thought relevant, including which prescribers and pharmacies the beneficiary would prefer. A second notice confirmed the decision. The regulation set its timing at not less than 30 days and not more than the earlier of the determination date or 60 days after the initial notice.
Section 423.153(f)(3) allowed two kinds of limit, alone or together. The sponsor could implement a point-of-sale claim edit specific to the beneficiary. It could also limit coverage of frequently abused drugs to those prescribed by selected prescribers, dispensed by selected network pharmacies, or both. The identification ended after one year unless the sponsor found a clinical basis to extend it, in which case it could last up to two years. A successful appeal ended it sooner.
Sponsors had to report what they did. The final rule said they would report case management results through OMS and coverage limitations through MARx, CMS’s system for payment and enrollment transactions. The regulation also required sponsors to share information with other sponsors when an at-risk beneficiary moved between plans.
What the limit looked like from the pharmacy
At the counter, a beneficiary-level limit appeared as a rejection that had nothing to do with the drug or the prescriber in general. The same prescription that another patient could fill would be refused for this patient at this pharmacy. A pharmacist needed to see from the reject code that the issue was a lock-in, and to direct the patient to the selected pharmacy or prescriber. The exempt groups added a judgment call, since a patient newly enrolled in hospice or newly diagnosed with cancer might not yet appear exempt in the plan’s data.
This part of the package touched individual patients directly. In our reading, its risk to a health system lay less in the rule than in the gaps between data sources. The plan knew about the limit. The prescriber might not. The pharmacy learned at the moment of dispensing. A health system that wanted its clinicians to know which patients were under a limit would need to capture the plan’s letters in the patient’s record.
The quantity: safety edits set thresholds at the counter
The third part came from the Call Letter rather than the rule. CMS said it expected sponsors to implement opioid safety edits for 2019. Unlike drug management programs, which applied to a small population after case management, these edits applied to every claim that met their conditions.
Three thresholds, three behaviors
The first edit covered patients new to opioids. Sponsors were to implement a hard safety edit limiting initial fills for acute pain to no more than a 7 days supply. The Call Letter recommended a look-back period of at least 60 days to decide whether a patient was opioid naïve. It reported that, in CMS’s analysis of 2017 prescription drug event data, 95% of opioid Part D fills were for 30 days supply or less. Sponsors were to include short-acting and long-acting opioids, except buprenorphine for medication-assisted treatment.
The second covered cumulative dose. The care coordination edit would trigger when a beneficiary’s total daily dose across opioid prescriptions reached or exceeded 90 MME. The pharmacist was to consult the prescriber, document the discussion and, if the prescriber confirmed intent, use an override code stating that the prescriber had been consulted. Sponsors could add prescriber or pharmacy counts to the edit. They could also implement hard edits with a threshold of 200 MME or more.
The third covered combinations. Sponsors were to implement soft edits alerting the pharmacist to duplicate opioid therapy and to opioids taken with benzodiazepines.
How an override worked
The Call Letter spelled out what should happen when the 7-day edit rejected a claim. If the patient did not receive the full days supply as written, the sponsor had to have its network pharmacy give the patient the standard CMS notice, “Medicare Prescription Drug Coverage and Your Rights.” The patient, a representative or the prescriber could request a coverage determination. Absent other utilization requirements, the sponsor should approve the full supply once the prescriber attested it was intended and medically necessary.
CMS acknowledged a data problem in the same passage. Plans “may not always be able to automatically apply all of the exemptions to this edit through claims data.” Nor could they always tell initial from continuing use for new enrollees at the start of a plan year. CMS expected sponsors to let pharmacists supply that information through help desks or override codes, and expected pharmacies and customer service staff to be trained on the edits.
Why thresholds depended on clean data
Each edit computed its result from fields on the claim and in the plan’s history. The 7-day edit relied on days supply. The 90 MME edit relied on drug, strength, quantity and days supply across every opioid claim in the plan’s data. A prescription written with an unusual sig, or a days supply entered loosely at the pharmacy, could push a claim over or under a threshold. A patient whose earlier fills were paid by another plan or in cash would look opioid naïve to the plan when the patient was not.
For a health system’s prescribers, the edits added a new kind of interruption. A pharmacist might call to confirm intent on a dose the clinician had already considered. For a system’s pharmacies, they added steps: the consult, the documentation and the override. Neither the rule nor the Call Letter changed what a clinician was allowed to prescribe. They changed what had to happen before the plan would pay without further review.
CMS described the 2019 opioid policies as giving plans additional tools for their drug utilization review programs. It said it would reassess whether an MME edit for opioid-naïve patients was feasible after sponsors gained experience. It also said it was contemplating pilot tests of the 7-day and care coordination edits with sponsors in 2018. We read that as an acknowledgment that the thresholds would be tuned by experience with real claims.
What documentation the edits produced
Each edit left a trail in a different system. The pharmacy recorded the reject, the consult and the override code. The prescriber’s chart recorded the call, if the clinician documented it. The plan recorded the claim and any coverage determination. The three records were not designed to be read together.
For a health system that owned both the clinic and the pharmacy, joining them was possible. A report that matched care coordination overrides to chart notes would show whether the consults the Call Letter described were taking place. It would also show which prescribers generated the calls. That kind of report is a management tool, not a requirement, and it depends on the organization’s own data governance for pharmacy and clinical records.
For an organization that owned neither, the documentation question was simpler and harder at once. Its clinicians still needed to record what they told pharmacists. Without that note, a later question from a plan or an auditor about why a high dose continued would have no answer in the chart.
The message: a SCRIPT update without a transition period
The fourth part concerned the channel rather than the decision. Part D’s electronic prescribing rules name the standard that prescribers, plans and pharmacies use for specified transactions. The April 2018 rule adopted NCPDP SCRIPT version 2017071 for those transactions from January 1, 2020, and retired version 10.6.
The final rule explained why this update was harder than earlier ones. Version 2017071 was “not fully backward compatible” with version 10.6, so CMS said it was unable to propose a transition period in which either version would count as compliant. All parties would move on one date. The rule said the new version offered the opportunity to standardize additional transactions and to improve existing ones.
Why the message belonged with the other three parts
The first three parts decided whether a claim would pay. The fourth decided what information reached the pharmacy to begin with. A prescription that arrived with a clear days supply, dose and diagnosis context gave the safety edits better inputs. A prescriber who knew a patient was locked in to a pharmacy could route the prescription there. Those benefits depended on prescribers’ systems sending structured data rather than free text.
For a health system, the SCRIPT update was a vendor dependency. The electronic health record vendor had to build version 2017071. The system had to test it with its intermediary and pharmacies, then switch on the date CMS set. Ambulatory networks running several record systems faced the same work for each. A practice on an older product version could find that its vendor’s upgrade path ran through a larger migration.
What the update did not do
The update did not require prescribers to send controlled substances electronically. That came later, by statute. It did not make any of the new edits visible to the prescriber at the time of writing. A prescriber writing an opioid prescription in 2019 would still learn about a 7-day edit or a care coordination edit after the fact, from a pharmacist’s call. In our reading, that gap showed that the 2018 package addressed the pharmacy end of the transaction before the prescriber end.
Why the pharmacy transaction attracted all four controls
The four parts came from different authorities. The Preclusion List grew out of program integrity and a stalled enrollment requirement. Drug management programs came from a 2016 statute. The safety edits came from annual guidance. The SCRIPT update came from the e-prescribing program. Yet three acted at the same moment, the adjudication of the claim, and the fourth set the format of the message that fed it. We think that was not an accident.
The pharmacy claim had three properties that suited enforcement. It was real time, so a control could act before the drug left the counter. It was standardized, so a rule written once could be applied by every plan and pharmacy benefit manager. And it was already the point where Part D sponsors exercised utilization management, so the machinery for rejects, overrides and notices existed.
The same properties created limits. A claim carries only what the pharmacy sends and what the plan already holds. It does not carry the prescriber’s reasoning, the patient’s full history outside the plan, or the reason a dose was chosen. Controls that depend on that context have to obtain it through side channels: a phone call, a coverage determination, a case management letter.
Which party held each input
The table of inputs makes the dependency visible. CMS held the revocation records that fed the Preclusion List and the claims analysis that fed OMS. The plan held claims history, notices and case management records. The pharmacy held the dispensing record and, with the prescriber’s confirmation, the override. The prescriber held the clinical reasoning and the patient relationship. The health system, where it employed the prescriber and owned the pharmacy, held parts of three of these four.
That made the health system an unusual participant. It was not the regulated party for any of the April 2018 rules, which addressed Part D sponsors and Medicare Advantage organizations. Yet it controlled much of the data that determined whether those rules produced good outcomes for its patients. In our view, that is the central fact a health system technology leader should take from the package.
What the four parts did not cover
The package left two gaps that a reader should note. It did not address patients paying cash, whose fills sat outside any plan’s claim history. And it did not address prescriptions dispensed under Part A or Part B, such as drugs given in a hospital outpatient department. The point-of-sale model reached only what passed through a Part D or Medicare Advantage drug claim.
How the controls fell on different organizations
The effects of the package depended on what an organization owned. We look at four kinds of organization separately, because the same rule produced different work for each.
Integrated health systems with employed prescribers and owned pharmacies
A system that employed its prescribers and owned outpatient pharmacies saw all four parts. Its credentialing office needed a way to learn that a clinician had been placed on the Preclusion List, since CMS’s letter went to the clinician. Its pharmacies needed staff trained on new reject types. Its clinics needed a way to receive plan letters about at-risk patients and to answer pharmacists’ calls about dose. Its informatics team needed to plan the SCRIPT upgrade.
One useful step for such a system was to treat Part D rejects as a data stream. Pharmacy systems record reject codes. A system that reported those codes by prescriber and clinic could see where edits were firing and why. That would show training needs, documentation gaps and, in rare cases, prescribers whose patterns warranted review.
Systems that sponsored Medicare Advantage plans
A system that also sponsored a Medicare Advantage plan with drug coverage was the regulated party for the plan. Through its pharmacy benefit manager, the plan had to load the Preclusion List, configure the edits, decide whether to adopt a drug management program in 2019, and staff the case management the regulation required. The plan’s compliance officer would own the written strategy on opioid overutilization the Call Letter expected.
Such a system also faced a conflict that the rule did not resolve. Its plan might send case management letters to its own employed prescribers about its own patients. That could be an advantage, since the plan could reach prescribers through internal channels. It could also blur roles. We think the plan’s clinical staff and the delivery system’s clinicians should keep separate records of the required case management. An auditor could then see that the plan, as sponsor, did what the rule asked.
Ambulatory networks and independent practices
An ambulatory network without its own pharmacies saw the package mainly through phone calls and letters. Its prescribers would hear from pharmacists about the 7-day and 90 MME edits, and from plans about at-risk patients. Its practice management staff would field patient complaints about rejected fills. The SCRIPT update would come through its record vendor.
For these organizations the main question was capacity. A practice with a small staff could not easily absorb more pharmacy calls without a process. Deciding in advance who would answer them, and how the answer would be documented in the chart, would reduce the burden at the moment of care.
Hospitals at discharge
Hospitals faced a narrower but sharper version of the same problem at discharge. A patient leaving after surgery with an opioid prescription for more than 7 days, and no opioid fills in the plan’s look-back period, would meet the hard edit at the pharmacy. The hospital’s discharge prescriber might be unreachable by then. Discharge workflows that anticipated the edit, either by writing for 7 days or by documenting the reason for more, would avoid a patient leaving the pharmacy without medication.
Objections: plan burden, clinical judgment and data limits
Three objections deserve a direct answer. Each has force, and none, in our reading, changes the argument that the claim had become the control point and depended on data from elsewhere.
That this was the plans’ problem
The first objection is that the rules applied to Part D sponsors and Medicare Advantage organizations, so health systems had no compliance duty. That is correct as a matter of who is regulated. But the effects of each control landed on prescribers, pharmacies and patients. A health system that waited for plans to solve the problem would find its clinicians answering calls and its patients leaving pharmacies empty-handed. The work did not need a legal duty to fall on the health system.
That thresholds would override clinical judgment
The second objection is clinical: hard limits on dose or days supply could disrupt stable treatment for patients with chronic pain. The Call Letter itself acknowledged risks of opioid withdrawal, disruptions in care, patients obtaining opioids from other sources, and suicide risk. CMS’s design responded with exemptions, an override path and a coverage determination process. Whether those responses were enough is a clinical and policy question beyond this article. Our narrower point is that each response also ran through data and communication between the pharmacy, the plan and the prescriber.
That claims data could not support these decisions
The third objection is technical. Claims data is a record of payment, not of care. CMS acknowledged that plans might not identify every exemption from claims alone. An edit computed from incomplete data will misfire in both directions. We agree, and that is why we think the health system’s role mattered. The health system held the clinical context that could correct the claim’s picture: a hospice election, a cancer diagnosis, a prior fill. Getting that context to the plan or pharmacy at the right moment was a systems problem the April 2018 rules did not solve on their own.
What a health system technology leader could check
The four parts translate into checks that a health system can run without waiting for a plan or a regulator. They are not legal requirements on the health system. They are ways to see where the controls touch its own operations.
- For prescribers: how the organization would learn that one of its clinicians had been placed on the Preclusion List, and who would act on that information.
- For patients: where plan letters about at-risk beneficiaries arrive, how they reach the treating clinician, and whether the chart records any prescriber or pharmacy limit.
- For quantity: whether pharmacy reject codes for safety edits are reported by prescriber and clinic, and whether discharge prescribing accounts for the 7-day edit.
- For the message: which version of the SCRIPT standard each record system sends, who at the vendor owns the upgrade, and when it was tested with the organization’s pharmacies.
- For sponsored plans: whether the plan’s case management records are kept apart from the delivery system’s records of the same patients.
Each check produces a record. Together, they show that the organization understood the pharmacy claim as a place where its own data met Medicare’s rules, and that it could trace a rejection back to where it began.
With hindsight
Medicare’s preclusion list took effect in stages. A CMS fact sheet dated April 1, 2019 said the first list was made available to Medicare Advantage and Part D plans on December 31, 2018, with approximately 1,300 providers and prescribers on it. CMS suggested that payment denials and claim rejections for that list begin on April 1, 2019. It said updates would be made available approximately every 30 days, around the first business day of each month.
The same fact sheet described the protections around the list. CMS said it would add a provider or prescriber only if the first-level appeal had been denied or the time to request one had passed. Plans had 30 days to review the list and notify affected beneficiaries. Beneficiaries were to receive at least 60 days’ advance notice before claims began to reject or deny. For monthly updates, plans would follow the same process, which the fact sheet described as a 90 day timeframe for review of the list and beneficiary notification.
Those dates show that the list arrived as a recurring data feed with notice periods attached, as the 2018 rule had implied. When a health system’s clinician appeared on it, the exposure came with a timetable of notices that the organization did not control.
Congress then made the drug management programs mandatory. The SUPPORT for Patients and Communities Act was enacted on October 24, 2018. It amended the Social Security Act so that, for plan years beginning on or after January 1, 2022, a PDP sponsor “shall” have such a program. The same law, in section 2007, provided for automatic escalation to external review under those programs. Section 2003 required that Part D prescriptions for controlled substances in schedules II through V be transmitted electronically, with exceptions, for drugs prescribed on or after January 1, 2021.
The current regulation reflects those changes. As checked on November 15, 2026, 42 CFR 423.153(a) says that no later than January 1, 2022, a Part D plan sponsor “must have established a drug management program.” The clinical guidelines in section 423.153(f)(16) now include a second basis for identifying potential at-risk beneficiaries. It applies beginning January 1, 2022: a history of opioid-related overdose. That history is shown by a recent claim with a principal diagnosis of opioid overdose and a recent claim for an opioid other than one used for medication-assisted treatment.
That addition matters for health systems. In our reading, an overdose diagnosis on a hospital or emergency department claim can now feed a Part D sponsor’s identification of at-risk beneficiaries. The current section 423.153(g) also provides that, beginning in plan year 2020, a PDP sponsor may request certain Medicare Parts A and B claims data about its enrollees. We think the data gap the 2018 package left between the pharmacy claim and the rest of a patient’s care has narrowed. It has narrowed through the claims stream, not through the health record.
The e-prescribing standard also moved. As checked on November 15, 2026, 42 CFR 423.160 no longer names a single SCRIPT version. It requires transactions to comply with a standard in 45 CFR 170.205(b), part of the federal health IT standards regulations in 45 CFR part 170. Its list of transactions now includes electronic prior authorization messages. The section also requires Part D sponsors to implement electronic real-time benefit tools. From January 1, 2027, formulary and benefit information between prescribers and sponsors must comply with a standard in 45 CFR 170.205(u).
Two things held up from 2018. The pharmacy claim remained the place where Medicare enforces prescriber and patient limits, and CMS said in 2019 that it would update the preclusion list approximately every 30 days. The structure of drug management programs, with case management, notices and limits that end after a set period, survived the move from voluntary to mandatory.
What did not hold up was the gap between the prescriber and the claim. The 2018 package told the pharmacy and the plan, not the prescriber at the moment of writing. Later rules and the SUPPORT Act moved information toward the prescriber: real-time benefit tools, electronic prior authorization transactions and mandatory electronic prescribing of controlled substances. For a health system, the lesson of the period is that its record system has become part of Medicare’s drug benefit infrastructure. That infrastructure is governed by standards it does not set and dates it does not choose.
Spotted an error? Tell us and we will check it and correct the article where needed.