2026 Transparency in Coverage Rule: What It Means for QPA Compliance

New federal rules are changing how health plans report pricing information, and TPAs and plan administrators are the ones who have to put those changes into practice.

On October 5, 2026, federal agencies finalized updates to the Transparency in Coverage (TiC) rule. The timing matters. These changes land just weeks after a federal court decision on Qualifying Payment Amounts (QPAs), and together they put a spotlight on the data behind healthcare pricing and compliance.

The goal of CMS-9882-F is straightforward: make published pricing information more accurate and more useful. The updated in-network and out-of-network reporting requirements take effect March 6, 2027, with the first updated files due April 1, 2027.

What Changed Under the 2026 Transparency in Coverage Rule?

Under the new requirements, health plans and issuers must:

• Exclude unlikely provider-service combinations

In-network files must remove rates for services a provider would be unlikely to furnish based on their specialty.

• Change reporting frequency

In-network and out-of-network files will move from monthly to quarterly publication, with in-network rates reported by provider network.

• Expand out-of-network disclosures

The reporting threshold decreases from 20 claims to 11, increasing the amount of information available.

Separately, telephone cost-sharing disclosure requirements also apply for plan years beginning on or after January 1, 2027, requiring plans to provide applicable cost-sharing information over the phone upon request.

New Documentation Requirements

The rule also adds new documentation requirements for plans and issuers.

New Taxonomy and Utilization Files will explain provider classification rules and identify providers receiving reimbursement. These requirements take effect September 6, 2027, with the first Taxonomy Files due October 1, 2027, and Utilization Files due July 1, 2028.

Every file must now include an attestation confirming the published information is accurate and complete, along with the name of a senior official. That puts real accountability behind the data.

Plans and issuers must also publish a plain-text file identifying where their machine-readable files are hosted, along with a monitored email address for inquiries. Websites must include a footer link labeled “Price Transparency” or “Transparency in Coverage” that directs users to the files, and these requirements apply beginning September 6, 2027.

How Do Ghost Rates Affect QPA Calculations?

The ghost rate debate comes down to one question: which contracted rates belong in a QPA calculation? Under the No Surprises Act, a QPA is generally the median contracted rate for a covered service.

That number carries weight. QPAs help determine patient cost-sharing amounts for certain out-of-network services and factor into the federal independent dispute resolution (IDR) process, so getting them right matters for both patients and payment disputes.

Which rates count was the central question in an August 2026 Fifth Circuit ruling. The court ruled against including certain ghost rates, which are contract entries for services a provider does not perform or negotiate.

Those entries pull QPAs artificially low. The court also ruled that qualifying bonus and incentive payments can’t be left out.

To be clear, the TiC rule governs public pricing disclosures. It doesn’t change QPA methodology. Both developments raise the same question for administrators: how do you know the data in your system is right?

Where Could Existing Platforms Fall Short?

Platforms built around the original requirements will likely need updates to flag inappropriate provider-service combinations and generate the new files.

The bigger question is where your QPA data comes from. If your system relies on machine-readable file data in one way, shape, or form, it’s worth a closer look to make sure ghost rates aren’t skewing your calculations.

For administrators managing multiple health plans, this gets more complicated. Many reporting systems weren’t built to consolidate pricing data across shared provider networks or organize out-of-network disclosures by market type.

One practical step: pull sample reporting files and compare them against your source data now. Gaps in provider classification or network-level rate reporting are much easier to fix before the new requirements take effect than after.

How IPS Is Addressing QPA Data Requirements

When the ghost rate question came up, we didn’t have to scramble. IPS already integrates with FAIR Health to support QPA workflows.

That matters because FAIR Health data is independent and claims-based, drawn from commercial in-network allowed amounts rather than published machine-readable fee schedules. Its reference data can be used for QPA calculations in circumstances permitted under the No Surprises Act, including when plans have insufficient contracted-rate information.

On the reporting side, we built Transparency+ to automate data validation and machine-readable file generation. It works with your existing claims system or alongside our Encompass+ administration platform.

Regulations will keep changing. We build our platforms to adapt with them, so teams aren’t left rebuilding their reporting by hand every time a new rule or compliance change comes out.

Key Takeaways for Plan Administrators

Start by getting clear on who owns what. The new requirements are a good reason to revisit how reporting responsibilities are split between health plans, administrators, and technology vendors. Assign an owner to each change, and test your systems well before the first updated files are due.

Remember, don’t assume your transparency updates will take care of QPA. They’re separate issues. Review your calculation methods on their own and confirm they comply with applicable requirements.

Is your current platform prepared for the new reporting requirements? Contact IPS and let’s talk through where your current process stands and how we can help.