A 2026 federal rule will change how commercial health plans disclose negotiated rates. For practice leaders, better public data is useful only when it is matched to the right contract and claim.
A public payer rate can look precise without answering the question a practice manager actually has: Is this the amount our practice should receive for this service?
The distinction matters after a new federal Transparency in Coverage rule finalized on October 5, 2026. The rule is designed to make health plans' public pricing data easier to find and interpret. But a posted rate is still not a substitute for a practice's signed payer agreement or a review of how an individual claim was processed.
What changed in October
The Departments of Health and Human Services, Labor, and the Treasury finalized amendments to the federal Transparency in Coverage rules (CMS-9882-F). The regulation was published in the Federal Register on October 6, 2026, and becomes effective December 7, 2026. Different disclosure requirements phase in after that date; the initial utilization-file posting is scheduled for 2028.
The requirements principally apply to non-grandfathered group health plans and health insurance issuers offering non-grandfathered group or individual health coverage. They do not create a new obligation for an ordinary physician practice to publish its own negotiated rates. They also should not be confused with the Medicare Physician Fee Schedule or treated as a new payment rule for Original Medicare claims.
Plans and issuers already publish machine-readable files containing in-network negotiated rates and out-of-network allowed amounts. The new regulation changes how those disclosures are organized, what context accompanies them, and how easily the public can locate them.
Four changes practice leaders should understand
One file per provider network, rather than per insurance product. For in-network rates, the rule moves reporting toward the provider-network level instead of requiring a separate file for every plan or policy. A practice comparing rates will need to identify the relevant network and product, not simply recognize the insurer's brand name.
Some provider–service combinations will disappear from published rate files. Insurers must exclude combinations they determine are unlikely to be reimbursed for a provider's specialty, using internal taxonomy mappings or other rules used in claims adjudication. The rule also calls for a separate taxonomy file explaining those mappings. The purpose is to reduce unrealistic combinations that made earlier files enormous and harder to use.
More context will accompany the numbers. New information includes product type, common network name, and network identifier.
The rule also establishes a utilization file. That file identifies providers with at least one reimbursed claim for a covered service during a specified prior period.
These supporting disclosures are phased in. Under the final rule, utilization-file posting begins July 1, 2028. They should not be assumed to be available today.
Finding and updating files should become simpler. The rule requires a standard website path to the disclosures. It also requires a contact point for questions about the files.
CMS says plans and issuers must add a "Price Transparency" or "Transparency in Coverage" link to their homepage footer beginning October 1, 2027.
In-network and out-of-network files also shift from monthly to quarterly posting under the updated requirements. That change does not mean a practice's contract rate can only change quarterly.
Why a missing rate is not a contract decision
Suppose a rate comparison tool no longer displays a provider–service pairing that appeared in an earlier file. Under the new specialty-based filtering rules, that absence may reflect the way the public file is prepared. It does not, by itself, prove that the practice lost network participation, that a contract was amended, or that the service will be denied.
The appropriate next step is to verify the payer agreement and applicable fee schedule, confirm the relevant network and product, and ask the payer to clarify a material discrepancy. The public file is a data source; it is not the practice's contract record.
Our reading at Healthcode is that a missing rate deserves one question, not a conclusion: why is it missing? Until the agreement and the network say otherwise, the file's silence tells you how the file was built — not what your practice agreed to.
A published rate is not the same as a claim payment
A posted negotiated amount can help a practice ask better questions about reimbursement. It does not show every fact that affected a particular remittance. Billing code, modifiers, date of service, place of service, product, provider participation, and claim-specific adjudication can all matter when reconciling expected and actual payment.
Think of the published rate the way you would the reference value printed on a report, and the adjudicated amount on a specific claim as this patient's actual result: the printed value gives context, but it is not the result in front of you for this case, on this date.
That is why public files are best used as an additional comparison point—not as stand-alone evidence of underpayment. A meaningful variance still needs to be tested against the practice's agreement and the payer's actual claim determination.
Three questions for the next revenue-cycle review
- Are we comparing the right rate? Identify the exact payer, network, product, provider, and service before interpreting a published number or an apparent omission.
- What is our authoritative source for expected payment? Confirm that signed agreements, fee schedules, and contract amendments are current and accessible to the people reviewing remittances.
- Who owns the exception? If the public file, contract terms, and actual adjudication do not align, assign someone to validate the difference, seek clarification when appropriate, and track the outcome.
A small practice does not need to turn this into a full-scale data project. Begin with a limited set of high-volume services and the payer contracts that matter most. Use relevant published rates to flag questions; resolve those questions using contract documentation and claim-level evidence.
What to do now—and what to wait for
The final rule does not make every revised data field immediately available. Its effective date is December 7, 2026, while key file and supporting-disclosure requirements take effect later. Practices can use the interval to make sure contract documents are organized, expected-payment checks are reliable, and payer-file comparisons have an identified owner.
As insurers update their public disclosures, the opportunity is better visibility, not automatic proof that current payments are right or wrong. The strongest control remains the connection between a negotiated term, the claim that was submitted, the payment that posted, and the follow-up that actually closed the discrepancy.
Bottom line
The October 2026 Transparency in Coverage rule aims to make payer pricing files smaller, clearer, and easier to find. That is useful for independent medical practices, but it does not remove the need to know which contract applies or to reconcile actual payments. Before acting on a rate—or on a missing one—verify the network, the agreement, and the claim.
What we tell practices is to keep the order straight: agreement first, claim second, public file third. Used in that order, the new files sharpen a review. Used in reverse, they can send a small team chasing a number that was never its rate.
Healthcode RCM can help independent practices examine how payer terms, expected-payment checks, remittance review, and follow-up connect within their revenue-cycle workflow. The goal is dependable visibility, not an assumption that a public file alone settles a reimbursement question.
Sources
• Federal Register — Transparency in Coverage, final rule CMS-9882-F, 91 FR 63748 (Oct. 6, 2026)
• CMS — Transparency in Coverage Final Rules (CMS 9882-F), fact sheet (Oct. 5, 2026)
• CMS — Use of Pricing Information Published Under the Transparency in Coverage Final Rule
Loading approved comments…