Price Transparency Healthcare Providers Can Use: A Guide to Comparable Commercial Rates

Your payer says your rates are competitive. Your contracting team has your fee schedule, but no clear answer to a more useful question: What does that payer publish for comparable providers delivering the same service in your market?

The files are public, yet a search can return several prices for one code, rates assigned to providers who never perform the service, and amounts that describe a different setting. According to MGMA's December 2025 poll, only 18% of 207 responding medical groups used Transparency in Coverage negotiated-rate data in payer contract talks. Nonusers cited limited time, tools, and skills, among other barriers. The challenge is deciding which figure answers the contracting question.

The price transparency healthcare providers can use is a rate they can explain and defend. Start with the right disclosure, match the service and provider context, test the reported rate, and frame a narrow finding. The example below shows both a comparison to keep and one to reject.

Price transparency healthcare providers can use starts with the right file

Choose a payer's in-network rate file when your question is what a commercial plan reports for a service and provider. Use a hospital price file when the question concerns a hospital's disclosed charges or payer-specific negotiated amounts at that hospital. Use a patient estimate when the question concerns one person's expected out-of-pocket cost. These sources describe different prices, so a comparison starts by naming the price you need.

Healthcare price transparency is the public disclosure of prices and related information under federal hospital and health plan rules. Since 2021, CMS has required hospitals to publish a machine-readable file of items and services and a consumer-friendly display of shoppable services. Under Transparency in Coverage, covered health plans and issuers publish in-network negotiated rates in machine-readable files. The payer files are the usual starting point for a provider that wants to compare its commercial reimbursement with local peers.

The sources answer different questions:

• Hospital machine-readable file. What it describes: Hospital standard charges, including payer-specific negotiated charges. Useful provider question: What does a named hospital disclose for this item or service?. What it does not establish: What a nonhospital provider receives, or what one patient owes
• Payer in-network rate file. What it describes: Rates the payer reports for covered services and participating providers. Useful provider question: What does this payer report for comparable providers in this market?. What it does not establish: The amount paid on a particular claim
• Patient-facing estimate or cost-sharing tool. What it describes: An estimate tied to a patient's coverage and circumstances. Useful provider question: What expense does a patient need to plan for?. What it does not establish: A peer commercial reimbursement benchmark

The CMS hospital guidance and TiC rule summary explain the first two disclosure duties. The TiC rules also address consumer cost-sharing tools, but those tools do not replace a provider-side rate comparison.

Keep the October 2026 rule change on the right timeline

Payer in-network and out-of-network files remain subject to the earlier monthly posting requirement until the 2026 amendments apply. In October 2026, CMS finalized changes that move those files to quarterly posting, organize in-network rates at the network level, and add contextual files and identifiers. According to CMS, the in-network and allowed-amount amendments apply five months after publication of the final regulations in the Federal Register; the new taxonomy, utilization, and text-file provisions apply 11 months after publication. Those future changes do not make an October 2026 file quarterly.

For a comparison today, record the publication date of the actual file you used. A rule's future posting cadence tells you what a payer must publish later. The file date tells you which reported rates you are examining now. Once you have the correct source and date, the next task is finding rates that belong in the same comparison.

Price transparency healthcare teams can trust requires matching the service

Match the billing code, payer and network, provider, geography, setting, rate type, and reporting date before calling two rates peers. A shared code is a starting filter. It does not establish that the services were delivered or paid under comparable arrangements. The Peterson-KFF Health System Tracker's TiC analysis documents why these details matter: payers report unlikely provider-service combinations, multiple rates for one apparent arrangement, and different payment types.

Begin with one decision, not a download of every file

Choose a service and payer that matter to your own commercial contract. A managed care team preparing a renewal can start with a high-volume code from its internal service mix, the payer in question, and the provider entity listed in the contract. Internal volume identifies priority; the public rate file does not tell you how often your organization billed that service. According to MGMA, practices using TiC data in payer talks apply it to CPT-level benchmarks and reimbursement targets.

Write down the comparison question before querying: “For this code and billing setting, what in-network dollar rates does Payer A report for comparable providers in this market and network?” This wording prevents a later chart from silently mixing commercial payers, inpatient and office settings, or different rate types.

The record you keep for each candidate rate needs the following context:

1. Service: billing code, code system, and modifier when one applies.
2. Contracting party: payer and the relevant plan or network label. Flag missing or ambiguous labels rather than guessing which product applies.
3. Provider: NPI and tax identification number where reported, plus the provider's type and specialty. Check whether that provider performs the service.
4. Care setting: professional versus institutional billing class and place of service where reported. A physician office rate is not a facility rate.
5. Payment form: negotiated dollar amount, per diem, percentage of charges, or another reported type. Do not put unlike forms into one dollar-rate distribution.
6. Time and provenance: file publication date, source URL or dataset version, and any notes attached to the rate.

These fields reflect the current TiC reporting schema described by Peterson-KFF. Some fields are missing or reported inconsistently in actual files. A blank field lowers confidence; it is not permission to fill in a convenient value.

Keep the comparable rows and reject the attractive outlier

A convincing rate gap survives the same-context test. Consider this fictional example. Every dollar amount and organization below is invented to show the method; it is not PayerPrice market data.

• Your group. Reported rate: $112. Context: Same commercial payer and network, selected outpatient professional code, local market. Decision: Baseline to check against your contract
• Peer A. Reported rate: $120. Context: Same payer, network, code, billing class, and market. Decision: Keep
• Peer B. Reported rate: $125. Context: Same matched fields. Decision: Keep
• Peer C. Reported rate: $128. Context: Same matched fields. Decision: Keep
• Provider D. Reported rate: $190. Context: Same code, but institutional facility billing. Decision: Reject from the professional peer set

The $190 row makes the gap look larger, but it answers a different reimbursement question. The three retained peers report $120 to $128, compared with your group's $112. That observation justifies a closer review. Three peers do not establish a market percentile or a guaranteed increase. Expand the peer set, confirm entity and rate type, and document exclusions before treating the range as a contracting benchmark.

The example deals with an obvious setting mismatch. Real files contain less visible problems, including duplicate or implausible rows. Those require a validation pass before the retained range reaches a CFO or payer.

How price transparency healthcare data can mislead a benchmark

A published rate is evidence of what was reported, not automatic proof of a clean peer price or an actual claim payment. The Peterson-KFF analysis found rates for providers unlikely to furnish the listed service and multiple amounts for the same apparent service, provider, and network. CMS's October 2026 fact sheet cites large files, ambiguous data, and difficulty comparing disclosures as reasons for its final-rule changes. The contracting team needs to make its judgment visible.

Run five checks before calculating a market range

Test relevance, identity, context, payment form, and completeness for each rate you retain. This short review does not fix a payer's source file. It tells the reader which observations support the specific question.

1. Relevance: Does this provider actually furnish this service? An unrelated specialty with a reported rate is a reason to investigate or exclude the row. CMS identifies unlikely provider-service combinations as a cause of oversized files.
2. Identity: Does the NPI identify the intended individual, group, or facility? Are multiple NPIs tied to one organization? The Peterson-KFF study shows that rates across an institution's NPIs do not always line up neatly.
3. Context: Do payer, network, code, modifier, billing class, and setting match? If a network label is unclear or a required setting is absent, mark the observation uncertain instead of treating it as a direct peer.
4. Payment form: Is this a comparable negotiated dollar rate? A per diem, percentage of charges, or fee-schedule entry requires separate interpretation. Peterson-KFF found multiple rate types for the same apparent arrangement.
5. Completeness: Does the payer report several rates where one applies, or leave critical information blank? Preserve the source rows and flag the ambiguity. Choosing the largest or smallest number without a reason changes the answer.

This is also a check on the team’s capacity. According to MGMA's poll analysis, practices that do not use TiC data frequently cite the time, tooling, and skills needed to turn large files into usable benchmarks. A normalized dataset or analytics platform reduces manual work, but the reviewer still needs a record of the chosen peer set and exclusions. PayerPrice's product overview describes searches by payer, provider, billing code, and location; coverage and source quality still vary by payer and service.

Separate the contracted rate from the payment on a claim

Use published negotiated rates to compare commercial contract positions; use your agreement and claims or remittance records to test an actual payment. A TiC rate does not contain your organization's claims volume, a patient's deductible, or the full set of terms that determines a particular adjudicated amount. The Peterson-KFF analysis notes that price data do not reveal whether or how often a rate is used.

Kevin Barron, vice president of payer relations at University Health San Antonio, describes why this boundary matters. In an MGMA podcast interview, he explains that his team audits contracts and expected payments, and that contract language and payer policies affect what the organization receives. A below-peer published rate signals a contracting question. A claim paid below the amount your agreement requires signals a separate payment review. Neither finding proves the other.

Keep one sentence beside every chart: “Published in-network rate, source date, matched fields, exclusions, and known limits.” That label makes the result reviewable. The final step is turning a reviewed comparison into a question leadership and the payer can address.

Turn a vetted rate into a contracting question

Present the matched comparison, its limits, and the action you want the contracting team to take. A long export forces leadership to repeat the analysis. A one-page evidence brief shows the service, payer, market, peer definition, rates, exclusions, and source date. It also states which data come from the public file and which come from the provider's own contract or claims system.

Here is the core of that brief for the fictional example:

For the selected outpatient professional service, Payer A reports our group's in-network rate at $112 and three matched local peer rates at $120, $125, and $128 in the reviewed file. We excluded a $190 institutional rate because it is a different billing class. Confirm the contract's effective rate and expand the peer set before setting a renewal target.

The statement makes no claim about what the payer owes on past claims. It also resists a payer's selective comparison. If a payer points to a lower published price, ask whether that row matches the same code, network, provider type, setting, and rate form. In an HFMA roundtable, Laurie Hurwitz, then senior vice president of revenue cycle and managed care at OSF HealthCare, described using local comparisons to answer a payer's claim that her system was already paid too much:

“When payers tell me that they’re paying us too much, I can point out where they are paying us less than market.”

- Laurie Hurwitz, OSF HealthCare, in HFMA

That is a use for the data, not a guarantee that the payer agrees to a higher rate. In HFMA's report on provider negotiations, Scott Ellsworth says price transparency comparisons help set targets and build internal agreement, while a negotiation still depends on strategy and leverage. A contracting leader can use the evidence brief to decide which rates deserve verification, which services need a larger sample, and which payer conversations deserve priority.

PayerPrice lets provider teams search commercial negotiated rates and compare them by payer, provider, code, and location. Bring your top codes, payer, provider identifiers, and market to a focused review. The useful output is a finding your team can trace back to a source file and defend in the room.

Start with one rate question

Pick one commercial payer, one service code, and one market, then write down the exact rate comparison you need. Find the relevant in-network file, keep only comparable providers and payment forms, record the source date, and flag every exclusion. The price transparency healthcare providers can use has a defined question behind it and a clear limit beside it.

That work produces a specific next step: verify the apparent rate gap against your own agreement, expand the peer set, and decide whether the finding belongs in the next payer discussion. It also prevents a public rate from being mistaken for a paid claim or a patient's bill.