Price Transparency Needs an Operating Owner
A Midwest CFO asks for a comparison of what the company’s health plan pays for a common procedure at three nearby facilities. The answer should be useful. Instead, the team gets a link to a giant data file, a note that the administrator has its own portal, and a reminder that health care pricing is complicated.
All of that may be true. None of it answers the business question. A self-funded employer does not need to become a data publisher or a hospital negotiator. It does need a clear way to turn available information into a decision.
The source idea: disclosure is becoming more accountable
CMS recently finalized updates to the Transparency in Coverage rules. The agency’s stated aim is to make required machine-readable price data easier to locate, more standardized, and more reliable. Among other changes, the rules call for clearer file-location information, a standard format specified in guidance, and an attestation by a designated senior official that applicable information is complete and accurate to that person’s knowledge and belief.
This is not a promise that a raw data file will answer every employer question. It is a practical signal: transparency is moving beyond a box-checking exercise. If the information is hard to find, hard to interpret, or never reaches a purchasing conversation, its value to the plan sponsor is limited.
Separate the file from the decision
Price files can be enormous and technical. They are not a CFO dashboard, a provider recommendation, or a guarantee of what a particular member will owe. Rates can vary by contract, location, billing code, benefit design, and clinical circumstance. A responsible comparison needs enough context to avoid a false conclusion.
That is why the operating question comes first: what decision are we trying to make? It might be whether to examine a high-cost service category, test a direct-contracting opportunity, improve member navigation, or ask better questions during a network or TPA review. Start with that question, then decide what data is needed to answer it.
Give transparency a named path through the organization
The plan sponsor should name a business owner for transparency requests. That person is not expected to calculate every rate or handle protected health information. Their job is to make sure a request has a purpose, the right vendor receives it, assumptions are documented, and leadership gets an answer that separates fact from interpretation.
For example, a simple request log can track the service category, geography, source of the data, date range, comparator, limitations, owner, and next decision. Keep individual claim details in the systems and processes designed to protect them. Executive reporting should focus on patterns and options, not member-identifiable stories.
Ask vendors questions that produce a usable answer
“Send us the transparency file” is rarely enough. A better request says what the company wants to understand and how it will use the result. Ask the administrator or analytics partner to explain the relevant allowed amounts, utilization context, service definition, network status, and material limits on the comparison. Ask what would change the conclusion.
Then make the next step proportionate. A meaningful price difference may justify deeper analysis, a member-navigation pilot, or a focused provider conversation. It may also turn out to be a data issue, a coding issue, or a category where the plan has little practical ability to redirect care. Good governance allows any of those answers.
Why this matters to a self-funded employer
When an employer pays claims from plan assets, health care purchasing is not just an annual renewal event. It is an ongoing set of choices about contracts, navigation, benefit design, and oversight. Transparency data can support those choices, but only when a plan has an operating rhythm for using it.
For Paul H. Flowers Jr. at Superior Insurance Advisors and Paul.Health, the goal is plain-English control: identify the business question, put the right people around it, use the available evidence carefully, and document the decision. More data is not automatically better. Better decisions are.
Source: CMS, “Transparency in Coverage Final Rules (CMS-9882-F)”. This article is original educational commentary, not legal, compliance, or fiduciary advice. Plan documents, vendor agreements, and applicable law govern.
Five questions for the next plan meeting
- What purchasing or plan-design decision are we trying to inform?
- Who owns the request, vendor follow-up, and decision-ready summary?
- Which rates, service definitions, utilization facts, and limitations belong in the comparison?
- How will we protect individual claim information while reporting useful trends?
- What action, if any, will we take if the evidence shows a material opportunity or risk?
If your team can find a price file but cannot connect it to a business decision, who owns the missing step?