Types of PBM oversight solutions for health plans

Pharmacy benefit manager (PBM) oversight solutions are the tools and services a health plan uses to verify that its PBM is executing the plan's contract terms, benefit design, and regulatory obligations accurately. The label gets applied to a wide range of offerings that answer very different questions on very different timelines, from a plan's own internal review processes to periodic audit engagements to continuous claims monitoring. Health plans evaluating the space are often comparing options that are not actually substitutes for one another, which makes the first useful step a map of the categories rather than a list of names.

This article lays out the six categories of oversight in use today, the question each one answers, and how they combine. It is written for pharmacy and finance leaders deciding where to invest next, and it deliberately describes solution types rather than specific firms, because the right structure depends on the plan's book of business, its PBM contract, and the oversight it already has in place.

Internal oversight: the foundation every plan already has

Every health plan runs some form of internal PBM oversight. Pharmacy teams review the annual benefit build, manage operational and member-focused meetings with the PBM, track scorecards and dashboards, raise discrepancies, and open tickets when something looks wrong. Contract negotiation itself is an oversight act: the terms the plan fights for are the standard everything else gets measured against.

This layer is the foundation, and nothing below replaces it. Its constraint is scale rather than effort. A team reviewing claims manually is always working a sample, and systemic issues do not reliably surface in small data sets. The categories that follow exist to extend what internal teams can see, not to substitute for their judgment.

Periodic audit firms

The traditional external check is the PBM audit: an independent firm tests a sample of claims against the contract's explicit terms, typically after the plan year closes or once per contract cycle. Audits verify guarantee performance, pricing benchmarks, and rebate commitments, and they produce findings that are concrete and contractually defensible.

The structural limits are cadence and coverage. Findings arrive months after the claims were paid, which means an error introduced early in a plan year can persist for 12 to 24 months before anyone acts on it, and sample-based review can miss issues that fall outside the sample frame entirely. Why the annual PBM audit is no longer enough covers this in detail. Audits remain useful, particularly where a contract requires them, but they answer a retrospective question at a fixed interval.

Procurement, benchmarking, and contract consultancies

A separate category focuses on the deal rather than the claims: market checks, rate benchmarking, RFP management, and PBM contract negotiation support. These firms help plans understand whether their contracted terms are competitive and help structure the next agreement.

This work operates on the renewal cycle. It shapes what the plan negotiates, but it does not verify how the negotiated terms perform in adjudication between renewals. A plan can hold a well-benchmarked contract and still experience meaningful divergence between that contract and claim-level execution, which is a different problem requiring different infrastructure.

Pricing and rebate specialists

Some offerings concentrate on a specific financial dimension: repricing claims against benchmark methodologies, validating rebate payments against guarantees, or performing forensic pricing analysis on a defined claim set. The depth on the targeted question can be considerable.

The tradeoff is scope. Pricing is one of several places where execution diverges from intent. Benefit design configuration, coordination of benefits logic, clinical program enforcement, and member cost-share application sit outside a pricing-only lens, and in Rivera's experience those categories carry a substantial share of avoidable spend.

Fraud, waste, and abuse tools

FWA programs detect bad actors: pharmacies billing improperly, prescribers with anomalous patterns, members misusing benefits. This is necessary work, and for government lines of business much of it is required.

It is also a different question from payment integrity. FWA asks whether someone in the claim chain behaved improperly. Pharmacy payment integrity asks whether claims were adjudicated according to the plan's contract, benefit design, and regulatory requirements, and the largest sources of leakage there involve no misconduct at all.

The line between these categories is drawn by data and cadence rather than by the question itself. A program already evaluating 100% of claims on a continuous basis can ask the misconduct question of the same claims stream alongside contract, configuration, and benefit questions, which is why FWA detection increasingly appears as a capability within continuous monitoring rather than as a separate purchase. What a standalone FWA tool cannot do is the reverse: it will not flag a misconfigured accumulator, a lesser-of rule that skips a drug category, or an incomplete formulary update, because nothing fraudulent occurred, and plans that assume an FWA program covers that territory leave the systemic category unwatched.

Continuous pharmacy claims monitoring

The newest category evaluates 100% of pharmacy claims on an ongoing basis, retrospectively and post-adjudication, against the full set of rules that should govern each claim: contract terms, benefit design, clinical edits, and regulatory requirements. Proprietary algorithms encoded from the plan's own documents flag divergence, pharmacists validate findings, and each confirmed issue is documented with the affected claims, the contractual basis, and the quantified impact so the plan can pursue recovery with its PBM and correct the root cause.

The distinguishing property is timing plus completeness. Issues surface while they are current rather than at year end, the review covers every claim rather than a sample, and monitoring continues after a correction to confirm it holds. That combination is what catches configuration drift, systemic integrity issues that are not contract violations, and errors that recur after being fixed, which are precisely the categories the other solution types are not built to see. What to expect from an independent program walks through how these engagements work in practice.

How the categories combine

These solution types answer different questions, which means the practical decision is portfolio construction rather than either-or selection. A plan with a strong internal team, a periodic audit, and procurement support at renewal has the deal and the annual retrospective covered. What that structure leaves open is the space between: whether the negotiated terms and designed benefit are executing accurately at the claim level, every week, across the full book.

A reasonable way to pressure-test your current structure is to ask which existing tool would catch a specific failure. If a mid-year formulary update fails to propagate to every adjudication rule in March, which layer of your oversight surfaces it, and when? If the answer is next year's audit, the gap is cadence. If the answer is the sample might not include those claims, the gap is coverage. Plans that can answer with a specific mechanism and a short timeline have the structure working; plans that cannot have found their next investment.

For plans adding the continuous layer, the evaluation criteria that separate offerings are independence, coverage, specificity, validation, follow-through, and fee alignment.

Frequently asked questions

What types of PBM oversight solutions are available to health plans?

Six categories are in common use: the plan's internal oversight function, periodic audit firms that test sampled claims against contract terms, procurement and benchmarking consultancies focused on contract competitiveness, pricing and rebate specialists focused on specific financial questions, fraud, waste, and abuse tools focused on misconduct, and continuous pharmacy claims monitoring, which evaluates 100% of claims on an ongoing basis against contract, benefit design, and regulatory rules.

Do health plans need more than one type of PBM oversight?

Typically yes, because the categories answer different questions. Procurement work shapes the contract, audits test it retrospectively, FWA programs watch for misconduct, and continuous claims monitoring verifies day-to-day execution across every claim. These functions complement rather than replace one another, and the gaps appear when a plan assumes one category covers a question it was not built to answer.

How is fraud, waste, and abuse detection different from pharmacy payment integrity?

FWA detection looks for improper behavior by pharmacies, prescribers, or members. Pharmacy payment integrity verifies that claims were adjudicated according to the plan's contract, benefit design, and regulatory requirements, where the largest sources of leakage are configuration and execution issues involving no misconduct at all. An FWA program will not flag a misconfigured pricing rule or an incomplete formulary update, because nothing fraudulent occurred. Some continuous monitoring programs incorporate FWA detection as a capability on the same claims data, while the reverse does not hold.

When should a health plan add continuous claims monitoring to its oversight structure?

The clearest indicator is an unanswerable timing question: if a configuration or pricing error were introduced mid-year, no existing layer of the plan's oversight would surface it before the next audit cycle. Common catalysts include an upcoming PBM contract renewal where the plan wants independent claim-level data, audit findings that suggest issues were not isolated, and benefit or regulatory changes that increase the volume of configuration activity.

Can a plan's internal pharmacy team provide continuous PBM oversight on its own?

Internal teams already provide essential oversight, and their judgment anchors every other layer. The constraint is infrastructure: continuous oversight means testing every claim against the full set of contract, configuration, and benefit rules on an ongoing basis, which is not achievable through manual review at any team size. Independent continuous monitoring extends the internal team's reach rather than replacing its role.