In March, a payer that accounts for a fifth of a dermatology practice's revenue published a reimbursement policy update in its monthly bulletin: starting June 1, a second destruction code on the same date would need a specific modifier and supporting documentation or it would deny. The bulletin went to the practice's general inbox, where it sat unread beneath 40 other payer emails. In July the denials began. By the time the biller connected them to the policy, the practice had 260 denied lines, half of them past the payer's 60-day reconsideration window.
The payer did nothing wrong here. It gave 90 days notice in the channel the contract specifies. The practice had no routine for reading that channel, and so a policy change that would have taken 20 minutes to handle in March cost a month of rework and a permanent write-off in July.
This piece describes payer policy monitoring as a monthly routine: which sources to check and on what cadence, how to triage what applies to your practice, the fields a change log needs, how a notice becomes a scrubber rule, and how to confirm after the effective date that the rule worked.
Key takeaways
- Every major payer publishes policy changes on a predictable schedule, usually 60 to 90 days before the effective date, and Medicare's changes land on quarterly and annual dates you can put on a calendar today.
- One owner, one list of sources and about two hours a month is enough for a practice with fewer than ten payers that matter.
- A change log with published date, effective date, codes affected, impact estimate and the action taken is the record that turns reading into results, and it is what a manager reviews at month end.
- The work is done when the change is in the claim scrubber, the fee schedule, the prior authorization list or the provider's documentation habit, not when the bulletin has been read.
Where the changes are published
Payers announce reimbursement policy, medical policy and administrative changes in provider bulletins, and most contracts say the bulletin counts as notice. The names and cadences differ. UnitedHealthcare publishes a Network Bulletin monthly. Aetna publishes OfficeLink Updates quarterly, in March, June, September and December. Anthem and most Blue plans publish provider news monthly by state. Cigna, Humana and the regional plans each have their own newsletter, and state Medicaid agencies and their managed care plans publish provider bulletins on their own schedules. Most also post the full text of reimbursement policies on their provider websites with an effective date and a change history, which is where you go once a bulletin flags something.
Medicare is the most predictable. The physician fee schedule final rule arrives around November 1 for January 1. CPT changes are effective January 1 and HCPCS Level II updates land quarterly on January 1, April 1, July 1 and October 1. National Correct Coding Initiative edits update quarterly on the same dates. ICD-10-CM changes take effect October 1, with a smaller April 1 update. Your Medicare Administrative Contractor publishes local coverage determination changes and billing articles continuously, and CMS sends the MLN Connects newsletter weekly. Medicare Advantage plans generally follow Medicare coverage but publish their own prior authorization lists and administrative rules.
| Source | Cadence | Typical notice before effective date | Check on |
|---|---|---|---|
| UnitedHealthcare Network Bulletin | Monthly | 60 to 90 days for reimbursement policies | First week of the month |
| Aetna OfficeLink Updates | Quarterly (March, June, September, December) | Usually 90 days | Mid-month in those months |
| Anthem / Blue plan provider news | Monthly, by state | Varies, often 60 to 90 days | First week of the month |
| State Medicaid and MCO bulletins | Irregular | Sometimes under 30 days | Twice a month |
| CMS physician fee schedule final rule | Annual, around November 1 | About 60 days | First week of November |
| HCPCS and NCCI quarterly updates | January 1, April 1, July 1, October 1 | Files posted a few weeks ahead | Second week of the prior month |
| MAC LCD and article updates | Continuous | 45-day notice for new or revised LCDs | Monthly, filtered by specialty |
The two-hour monthly routine
Assign one person. In a small practice that is usually the billing lead or the practice manager; in a group with an in-house billing team it is a senior biller with payer relations experience. Give that person a written list of sources with login details where portals are involved, a standing calendar block, and a place to record what they find. The job is not to read everything. It is to scan each source for items that touch the practice and to log those.
The triage question for each item is simple: does it involve a payer we bill, a code we bill, or a process we use? A new policy on inpatient DRG validation does not apply to an office-based practice. A change to modifier 25 documentation expectations applies to nearly everyone. A change to prior authorization for a list of genetic tests applies if you order them. When the answer is yes, the item goes in the log with an impact estimate: how many claims a month, at what average allowed amount, are exposed if we do nothing.
Here is a worked example. A payer's May bulletin announces that effective August 1, HCPCS code 96127 (brief emotional or behavioral assessment) will be limited to two units per date of service and will require a distinct diagnosis code for each instrument. A pediatric practice bills 96127 with most well visits, often three units when it screens for depression, anxiety and substance use at adolescent visits. The billing lead pulls three months of claims: 410 claims a month with 96127, 90 of them with three units, at an allowed amount around $5 per unit. Exposure if nothing changes: 90 denied units a month, about $450, plus the follow-up time, plus the diagnosis coding problem that will deny the other two units too. Small in dollars, but the fix is 20 minutes: a scrubber rule that flags 96127 with more than two units for that payer, and a note to the clinicians to pair each screening tool with its own Z13 code. That is the kind of change that costs almost nothing in May and a great deal in September.
What the change log needs
The log can be a spreadsheet. What matters is the fields. Record the payer, the source and its date, the effective date, the policy name or number, the codes or modifiers affected, a two-sentence summary in plain language, the monthly impact estimate in claims and dollars, the actions required, the owner of each action, the status, and the date the last action was completed. Add a column for the date you verified the change after the effective date, which we cover below.
Two habits make the log useful. First, review it at the monthly billing meeting, sorted by effective date, so that anything due in the next 30 days is visible to the manager and the physicians. Second, keep the entries after they close. A year from now, when a denial trend appears and nobody remembers why a scrubber rule exists, the log is the only record. It is also the document our team asks for first when a practice engages us for denial management, because a practice with a log usually has a denial problem with a known cause, and a practice without one is starting from remits.
From notice to scrubber rule
A claim scrubber is the software layer, in the practice management system or at the clearinghouse, that checks each claim against rules before it is sent and holds the ones that fail. Most policy changes become a scrubber rule, and writing the rule is where the monitoring routine pays for itself.
A good rule is specific to the payer, the codes and the condition, and it tells the biller what to do. "Payer X, CPT 96127, units greater than 2: hold, reduce to 2 units or split by diagnosis" is a rule. "Check 96127" is not. Write the rule with an effective date matching the policy so it does not fire early on claims the payer will still pay under the old policy, and put the log entry number in the rule description so anyone can trace it. Then test it: run a handful of past claims that would have failed through the rule before turning it on for live claims. A rule that fires on the wrong claims holds clean revenue, and billers learn to override rules that cry wolf, which defeats the rule you actually needed.
Not every change is a scrubber rule. A fee schedule change goes into the contract rates loaded in the billing system so underpayments are caught. A new prior authorization requirement goes on the front desk's authorization list and into the scheduling workflow. A documentation change, like the modifier 25 example, goes to the providers as a one-paragraph note with an example, and into the coder's review checklist. The log's action column should name which of these the change requires, and often it is two or three.
Verifying after the effective date
The routine is not finished at the effective date. Thirty to forty-five days after a policy takes effect, when the first affected remittances have arrived, run two checks. First, look at denials for the affected codes with that payer: if the rule worked, there should be none or very few, and any that appear tell you the rule missed a case. Second, look at what the scrubber held: if it held far more claims than the policy justifies, tighten the rule. Record the result in the log's verification column and close the entry.
Over a year, the log tells you something about each payer: how many changes it made, how much notice it gave, and how often its changes cost you. That is useful in contract negotiations. It is also the evidence you need when a payer applies a policy retroactively or denies claims before the announced effective date, which happens more than it should and is a straightforward appeal when you have the bulletin and the log.
Questions we hear
We have three people in the office. Who has time for this?
Two hours a month is less time than one afternoon of reworking denials from a missed policy. Give it to whichever of the three reads payer correspondence anyway, put the sources in one bookmark folder, and accept that the first two months will be slower while the list of sources settles. Practices that outsource billing should ask the vendor to show them its change log; if there is none, that is your answer about how the vendor handles policy changes.
Do we need to read Medicare Advantage bulletins if the plans follow Medicare?
Yes, for the parts that do not follow Medicare: prior authorization lists, timely filing limits, claim submission rules and administrative requirements. Coverage usually tracks Medicare, but the operational rules are the plan's own, and they change.
How do we catch changes payers do not announce in bulletins?
Through the denial data. A new denial reason code appearing on a payer's remits, or a familiar one rising sharply, is a policy change that reached you without notice. Add a monthly denial trend review by payer and reason code to the same meeting where you review the log, and when a new pattern appears, ask the payer's provider relations contact for the policy behind it in writing.
What to do this week
- List your payers by revenue and identify the bulletin source and cadence for each of the top eight, plus your MAC and state Medicaid agency.
- Name the owner, block two hours on the calendar in the first week of each month, and create the change log with the fields above.
- Go back through the past three months of bulletins from your top three payers and log anything with an effective date still ahead.
- Write and test one scrubber rule from that backlog, with the log entry referenced in the rule description.
- Add "changes due in the next 30 days" and "verification of changes past their effective date" as standing items on the monthly billing meeting agenda, and consider a payer rules review if the backlog turns out to be large.
