2026 Transparency in Coverage Rule: OON Negotiation Data Guide

The Departments of Labor, Health and Human Services, and the Treasury published the final rule on October 6, 2026. It becomes effective December 7, 2026, but its data provisions have later applicability dates. Until those dates, plans and issuers continue under the prior machine-readable-file requirements. A negotiation package should therefore label both the file date and the rule version rather than blending old and new datasets.

This guide explains public data and an operational evidence method as of October 10, 2026. It does not claim access to proprietary repricing formulas, determine what a plan owes, establish a reasonable value, or replace contract review, a plan appeal, state law, or Federal IDR analysis.

What changes and when

1. Understand what the files actually contain

Transparency in Coverage requires many group health plans and issuers to publish machine-readable files with in-network rates and historical out-of-network allowed amounts. The in-network file describes negotiated rates for covered items and services. The allowed-amount file describes historical amounts paid and billed for out-of-network services that meet the reporting rules. Neither file is a claim adjudication record, a contract offered to the provider, or a legal conclusion about the correct reimbursement for another service.

2. Account for the 2026 OON data changes

The final rule addresses a practical weakness in the older allowed-amount files: many contained limited or no out-of-network data. The Departments finalized aggregation by insurance market type, reduced the reporting threshold from 20 claims to 11, and extended the reporting period in a way intended to increase disclosed OON information. The final rule also requires product-type context and accuracy attestations.

• Distinguish large-group, small-group, individual, and self-insured market data when the final structure applies.
• Do not treat the lower 11-claim threshold as proof that a sample is representative of the claim being negotiated.
• Record whether the value is a rate, an allowed amount, a billed charge, or a derived statistic.
• Use the file's date, quarter, attestation, plan or issuer identity, product type, and network identifiers in the evidence log.
• Retain the original file or a reproducible extraction reference so another reviewer can audit the result.

3. Use a claim-first matching method

Start with the disputed claim, not the dataset. Build a claim profile from the clean claim, itemized bill, remit, plan information, service date, and clinical record. Only then select public observations that match the actual service and payment question.

1. Identify the exact plan or policy, funding type, TPA, insurer, product, network, and repricing entity; do not infer them from a logo alone.
2. Match billing code system, code, modifier, units, place of service, professional or facility class, and bundled or case-rate method.
3. Match provider NPI, tax ID, organizational level, specialty or taxonomy, and service location where the file supports those fields.
4. Use a defensible geographic frame and explain whether it is local, regional, state, or national.
5. Align the observation period with the service date and note material market or rule changes.
6. Exclude duplicates, impossible values, unrelated arrangements, unmatched provider groups, and records with unresolved identity conflicts.
7. Summarize the remaining distribution and sensitivity instead of presenting one unexplained number.

4. Convert the analysis into negotiation evidence

Public rate evidence works best as one part of a claim-specific package. The provider should first correct coding or processing errors and identify the governing plan or contract. If the claim was processed as designed but the amount remains disputed, the analysis can show why a proposed resolution is reasonable relative to carefully matched observations.

Avoid saying that a public median, percentile, or observed rate is legally owed unless the governing document or law actually makes it the payment rule. Use language such as 'market evidence supporting the proposed resolution' and identify every limitation. A transparent analysis is more credible than false precision.

5. Keep TiC, ERISA, and Federal IDR separate

Transparency in Coverage is a disclosure framework. ERISA claims procedure governs many group-health benefit appeals. Federal IDR applies only to qualifying No Surprises Act items and services after the required open-negotiation process. The same claim may touch more than one framework, but a TiC comparison neither creates Federal IDR eligibility nor substitutes for a plan appeal.

• Track commercial negotiation, plan appeal, state remedy, contract notice, and Federal IDR dates independently.
• Do not describe every OON reduction as a surprise-billing claim.
• Use the plan's denial or reduction rationale to decide whether the immediate request is correction, document access, benefit appeal, or price negotiation.
• If a payer identifies a contract or network discount, request the agreement and access chain before presenting market evidence.
• If Federal IDR may apply, preserve open-negotiation and initiation requirements even while other discussions continue.

6. Prepare for the 2027 transition

Provider teams can prepare before the new file requirements apply. Update data dictionaries to capture market type, product type, network identifier, quarter, provider taxonomy, utilization context, and attestation. Store the rule version with each extraction. Build a reproducible audit trail from original file to filtered observations and final exhibit. When new structures arrive, test old and new pipelines in parallel before relying on trend comparisons.

Related Millennova Legal resources

Explore TPA and out-of-network commercial negotiation support, the broader TPA negotiation methodology guide, and the Data iSight review and counteroffer guide. For protected out-of-network claims, use the Federal IDR process guide.

Primary sources