A pharmacy report may not capture the full picture of an employer health plan’s drug spending. Medicines administered in a medical setting can appear in medical claims, including claims using J codes. Reviewing those claims alongside pharmacy information can help a plan identify questions that deserve follow-up.
The purpose is to understand the transactions and verify them against the plan’s arrangements. A high-dollar claim is a reason to investigate, not proof that a provider overcharged or that a different treatment setting is appropriate.
Start with the code, the units and the payment
Before comparing prices, identify what was billed and how the quantity was reported. A dollar amount without the drug, billing-code definition, units, date and setting can be misleading.
CMS billing guidance emphasizes using the appropriate code and reporting units accurately. Its rules are Medicare-specific; the commercial plan’s contract and claims administrator determine how its claims should be reviewed.
Ask the administrator to distinguish billed charges, allowed amounts, plan payments and member responsibility. These describe different parts of the transaction and should not be treated as interchangeable measures of cost.
Build a reviewable data set
Work through the plan’s authorized reporting process. Request only the information needed for the review and confirm who may receive it. A typical starting request can cover a defined period of medical drug claims, the relevant code and quantity fields, payment amounts, provider and setting information, and adjustment or reversal indicators.
Have the administrator explain missing fields and known reporting limitations. If a claim cannot be matched to a specific product or quantity, place it in a follow-up queue instead of filling the gap with an assumption.
- Use a consistent service or payment period.
- Separate original transactions from adjustments and reversals.
- Record whether totals represent allowed amounts or actual plan payments.
- Confirm the meaning of every quantity field before calculating a unit price.
Use benchmarks carefully
Begin by comparing similar transactions within the plan, while accounting for the product, quantity, service period and setting. Ask why a difference exists before labeling it avoidable spending.
CMS publishes Medicare Part B drug payment limits and code crosswalks. They can provide reference information, but a Medicare payment limit is not automatically the commercial plan’s contracted price. CMS also cautions that inclusion in these files does not itself establish Medicare coverage.
A useful review identifies which benchmark was used, why it is relevant and what adjustments remain unresolved. Present a potential variance as a question until the administrator or reviewer has confirmed the applicable contract terms.
Investigate transactions that need explanation
Prioritize claims with missing product information, quantities that do not reconcile with the billing description, unusual payment patterns or possible overlap between medical and pharmacy transactions. Ask for supporting documentation through the authorized process.
An apparent duplicate may be a reversal, a related service or a separate component of treatment. The review should establish the transaction history before requesting a recovery. Track findings as confirmed, explained or still unresolved.
Evaluate changes with the right people involved
If the review suggests a different purchasing arrangement, pharmacy vendor or site-of-care process, involve the administrator and qualified clinical advisers. Ask about coverage, network participation, treatment suitability, exceptions and transition support.
Compare the complete proposed arrangement, including administration, member costs and implementation requirements. Do not describe a change as delivering the same care for less unless the relevant financial and clinical details support that conclusion.
Privacy remains part of the work. HHS explains the standards for de-identifying health information. Replacing a name with an internal identifier is not, by itself, a basis for assuming a report is de-identified.
Use a 90-day review schedule
In the first month, agree on the scope, authorized recipients and data definitions. In the second, reconcile the data and select a manageable set of transactions for review. In the third, document responses, confirmed findings and any proposed changes.
Assign each action to a named owner and retain the supporting explanation. Report confirmed recoveries separately from projected future savings. That distinction gives leadership a usable picture of what the review has established and what still needs work.