Understand what is driving your pharmacy spend

A useful dashboard starts with a clear question: what changed, what contributed to it, and what needs a closer look? A total alone rarely answers all three.

1. Define the view. Identify the reporting period, included population and data source. Note whether the report uses paid dates or service dates and when the data was refreshed.
2. Name the cost measure. Plan cost, member cost and gross cost answer different questions. Check which fees, rebates and adjustments are included before treating two totals as comparable.
3. Show the drivers. Explore trends by therapy class and drug. Separate a change in utilization from a change in cost per prescription when the available data supports that distinction.
4. Record the next question. Connect each finding to an owner and a follow-up, such as checking a data exception or asking for supporting claim detail.

Before comparing two periods, confirm that the definitions and population are consistent. Where they differ, explain the difference alongside the chart.

For context on the categories used in federal prescription drug cost reporting, see the CMS RxDC overview. A dashboard review does not replace that reporting process.

Use your review to connect the reported result with its definitions, supporting data and next steps.

1. What changed? Ask which drugs, therapy classes or utilization patterns contributed to the difference from the prior period.
2. Are we comparing the same things? Confirm the population, dates, cost measures and treatment of reversals or adjustments.
3. What is included in the reported cost? Ask how member payments, administrative fees and rebates are reflected. Identify anything reported separately or still outstanding.
4. How does the result relate to our agreement? Review the applicable definitions and supporting detail with your contract and benefit advisers.
5. What happens next? Assign an owner, due date and evidence needed for each open item.

Keep the reporting discussion specific. A useful follow-up identifies the question, the data needed to answer it and how the result will be confirmed.

A savings estimate describes a possible result under stated assumptions. An achieved result needs evidence from the relevant period. Labeling them clearly helps a team understand what is proposed, what has been implemented and what has been verified.

• For an estimate: record the baseline, population, time period, assumptions, expected implementation date and included costs.
• For an implemented change: confirm when it took effect and which claims or members were within scope.
• For a measured result: compare a consistent baseline and period, explain material changes in utilization or population, and account for relevant fees and adjustments.
• For payments or rebates: distinguish amounts expected, amounts reported and amounts actually received.

A lower total spend does not, by itself, show what caused the change. Present the calculation and any limitations with the result, and keep unresolved amounts visible for follow-up.