← PolicyChanges blog

Payer operations · July 21, 2026

A payer is not one publisher

The newsletter and the coverage policy library are different systems with different cadences. Following one and calling it payer coverage is a common way to miss most of what changed.

By Ben Rodrigue, Founder

117payers tracked
34,262changes in the corpus
1channel most teams followusually the newsletter

Large payers publish provider-facing changes through several channels at once, and the channels do not carry the same content, the same volume, or the same schedule.

A typical national payer maintains a provider newsletter that publishes on a monthly cycle and carries perhaps a dozen items a year. The same payer separately maintains a coverage policy library holding hundreds of individual policies, each with its own review date, revised on a rolling basis with no announcement.

Both are that payer. Only one of them looks like news.

The volume gap is not subtle

A monthly newsletter producing roughly one policy-relevant item per issue sits alongside a bulletin library that can hold several hundred documents, a meaningful share of which are revised in any given year. Following the newsletter and treating it as payer coverage captures a small fraction of what actually changed.

The newsletter is also the channel that most resembles a feed, which is why it tends to be the one that gets followed.

Where else the same payer speaks

Beyond the newsletter and the policy library, changes surface through:

A single change can appear in one of these and none of the others.

Managed Medicaid is the sharpest example

In a state where Medicaid is delivered through managed care organizations, the state agency sets requirements that bind every plan, and each plan separately maintains its own manual, notices, and policy pages. The agency and the plan are both authoritative, on different things.

Following only the agency misses plan-specific operational rules. Following only the plans misses the requirements that override them. The plans are distinct organizations with their own landing pages and their own publishing schedules, and treating a state program as a single source flattens that distinction.

Coverage is a per-channel question

Asking whether a payer is covered has no useful answer on its own. The question that resolves is which of that payer's channels are covered, and what each one actually publishes.

Keep reading

A payer is not one publisher | PolicyChanges.app