CMS, working with the Departments of Labor and the Treasury, finalized changes to the Transparency in Coverage regulations on October 5, 2026. The rules change how health plans organize public pricing information and provide members with personalized cost-sharing information.
The agencies say the changes will make pricing disclosures more useful for consumers, employers and researchers while reducing duplicative reporting. Those are the intended benefits; actual results will depend on implementation.
For health plan leaders, the immediate task is to coordinate several projects: redesigning data files, reviewing vendor responsibilities, preparing member-service teams and establishing a reliable approval process.
Which health plans are affected?
The public-disclosure requirements generally cover non-grandfathered group health plans and issuers offering non-grandfathered group or individual coverage, subject to applicable exceptions. Employer-sponsored coverage, including self-insured arrangements, therefore needs attention alongside individual-market products.
Grandfathered plans also have obligations under the No Surprises Act’s price-comparison provisions, even when the broader public-file requirements do not apply. Plans should assess public reporting and member-service obligations separately.
A useful starting point is a coverage inventory showing each product, its funding arrangement, its provider network and the organization responsible for its disclosures.
What changes in the public pricing files?
The final rules introduce five particularly relevant changes:
- Network-based reporting: In-network files will be organized by provider network instead of separately for every plan or policy.
- Specialty-based exclusions: Plans must remove provider-rate combinations unlikely to be reimbursed given the provider’s specialty, using internal taxonomy or claims-adjudication rules.
- Broader out-of-network reporting: Files will aggregate information by insurance market type, and the reporting threshold falls from 20 claims to 11.
- Additional context: New taxonomy files explain the specialty rules used in preparing disclosures. Utilization files identify reimbursed provider-service activity for the relevant reporting period.
- Easier discovery: A root-directory text file must identify file locations and a monitored contact address. Website footer links must direct users to the disclosure page.
These changes are detailed in the CMS final-rule fact sheet.
The operational challenge is maintaining consistency across the files. A plan should be able to explain how a published rate relates to a network, why a provider-service combination was excluded and which source records support the result.
That work depends on clear relationships between contracts, providers, products and claims—the same foundation discussed in our guide to healthcare data models.
Accuracy becomes an explicit accountability requirement
The rules require attestations concerning the accuracy and completeness of specified disclosures, along with identification of a CEO, president or designated senior official responsible for overseeing data accuracy. They also require member cost-sharing information to be available by phone upon request.
Health plans should determine what evidence supports that assurance. A successful file upload alone does not tell leadership whether the underlying contract rates, provider mappings or coverage associations were checked.
An internal review package could include validation results, unresolved exceptions, reconciliations to source systems and a record of who approved publication. These are practical control recommendations, rather than a prescribed federal checklist.
The implementation dates health plans should track
The rule was published on October 6, 2026. Its applicability dates and first required posting dates are distinct:
| Milestone | Timing |
|---|---|
| Revised member cost-sharing disclosure provisions | Plan years—or individual-market policy years—beginning on or after January 1, 2027 |
| Revised in-network and out-of-network file provisions apply | March 6, 2027 |
| First revised quarterly in-network and out-of-network postings | April 1, 2027 |
| Contextual-file and website-footer provisions apply | September 6, 2027 |
| First taxonomy and text-file postings | October 1, 2027 |
| First utilization-file posting | July 1, 2028, then annually |
In-network and out-of-network files move to quarterly posting. Taxonomy files are also posted quarterly. Text-file location and contact changes require updates within seven calendar days. Existing obligations continue until the relevant transition dates. These distinctions follow the final regulatory text, including its timing provisions.
For project planning, record both the date a requirement becomes applicable and the date its first deliverable must be published. Treating September 2027 as the first deadline for every contextual file would overlook the separate utilization-file schedule.
Keep prescription-drug reporting on a separate schedule
The agencies announced plans to begin developing the prescription-drug file schema in November 2026, finalize it around May 2027 and expect publication using that schema beginning in December 2027, followed by monthly updates.
That is the agencies’ announced implementation roadmap and should be monitored as technical guidance develops. The quarterly schedule for other pricing files should not be applied across all disclosures.
Health plans should involve pharmacy benefit managers early enough to identify data-access, contract and delivery dependencies.
What health plans should prepare now
1. Assign responsibility for every deliverable.
Create a responsibility matrix covering data extraction, network mapping, file generation, hosting, member inquiries and publication approval. Where a third-party administrator or other vendor performs the work, identify the plan employee responsible for reviewing its output.
Vendor discussions should produce specific deliverables, testing dates and escalation procedures. A general assurance that a platform will “support the rule” gives the plan little evidence of readiness.
2. Test the network mapping before consolidating files.
Consider a hypothetical administrator serving several employer plans through one network. Consolidation may reduce repeated data, but the administrator still needs to preserve the correct relationships between coverage options and applicable rates.
Test shared-network arrangements, product variations and contract exceptions before scaling the process. Measure unexplained differences as well as reductions in file size.
3. Make exclusion decisions traceable.
Document which source system supplies provider specialties and which rules determine whether a provider-service combination remains in the published data.
Review a sample of removed combinations with claims and provider-data specialists. Investigate conflicting specialty records and record how exceptions are resolved. This helps prevent a file-reduction project from becoming an uncontrolled deletion exercise.
4. Rehearse the member’s phone experience.
For calendar-year plans, the January 2027 member-service milestone deserves immediate attention.
Test whether representatives can retrieve the relevant information, explain the estimate and handle uncertainty about the requested service. Compare phone responses with online results for the same scenario, and investigate discrepancies before launch.
A useful rehearsal includes common services, multiple providers and situations requiring clarification—not simply a scripted demonstration of the easiest request.
5. Build a repeatable publication and correction process.
Run a complete rehearsal from source data through public download. Include link testing, review of the contact mailbox, approval records and handling of a reported error.
Agree in advance who assesses an issue, who approves a correction and how the resolution is documented. These operational decisions are part of broader digital transformation in healthcare: the technology needs an accountable process around it.
At the next implementation review, leadership should ask for three concrete outputs: a dated delivery plan, a tested sample disclosure and a list of unresolved dependencies with named owners.
