Transparency in Coverage files guide
Payer machine-readable files expose negotiated rates. Learn what the files contain, where raw records fail, and how to turn a focused slice into traceable evidence.
Explore TiC dataDirect answer
Transparency in Coverage data is payer-published pricing information for covered healthcare items and services. The machine-readable files can expose negotiated rates, but they are built for publication—not for the analyst trying to answer a provider, payer, code, or market question.
Lumivera's On-Demand TiC Data product lets teams define the slice they need, then extracts, structures, validates, and delivers a usable dataset without requiring them to process the raw files themselves.
File anatomy
The currently enforced disclosures separate in-network negotiated rates from historical out-of-network allowed-amount information. Provider benchmarking primarily starts with the in-network file.
Applicable rates for covered items and services furnished by in-network providers. Records can connect a billing code and provider group to a negotiated amount and reimbursement structure.
Provider use: rate benchmarking, negotiation preparation, network and market analysis, and fee-schedule review.
Allowed amounts and billed charges for out-of-network providers, reported with historical context defined by the rule and technical guidance.
Provider use: out-of-network analysis and related pricing research.
In-network record map
CMS defines the publication schema. Provider analysis still needs enrichment and validation because raw identifiers do not fully describe the organization, market, or clinical relevance of each record.
Review the CMS technical guideReporting entity, plan or network identity, file source, and publication date.
NPI arrays, TIN, organization mapping, location, specialty, and care setting.
Billing code, code type, modifiers, and bundled or covered-service context.
Negotiated amount plus type—negotiated, derived, fee schedule, percentage, or per diem.
Expiration date, reporting month, schema version, and relevant contract or policy period.
Raw-file failure modes
Public and parsable does not automatically mean complete, comparable, or relevant to the provider decision. Every rate needs context and a reason to remain in the analysis.
NPIs and TINs may omit the names, locations, specialties, and organization relationships needed for a fair peer comparison.
Highly granular plan records must be mapped to the relevant network and reimbursement relationship before summarizing a market.
Dollar, percentage, per-diem, fee-schedule, bundled, and derived rates are not interchangeable units.
A provider-service combination may be listed even when the provider would be unlikely to furnish that service. Clinical plausibility must be tested.
A structurally valid record can still be duplicated, implausible, incomplete, or unsuitable for the intended comparison.
Publication periods, expiration dates, schema versions, and payer reporting behavior can change the result over time.
CMS identified unlikely provider-service combinations as a primary cause of oversized in-network files in a December 2025 proposed-rule fact sheet. Proposed changes are not current requirements.
Data quality and traceability
Payer files can be large, inconsistent, and difficult to compare. Lumivera structures the requested data while retaining the source context needed for defensible analysis.
Regulatory context: CMS Transparency in Coverage.
Retain the payer, file, plan, provider, code, and publication context behind the extracted record.
Map inconsistent file structures and identifiers into fields analysts can filter, compare, and export.
Separate duplicate, incomplete, implausible, or non-comparable rates from the evidence your team will analyze.
Preserve enough source context to understand what a rate represents and why it was included in the output.
Decision-grade checklist
A polished export is not enough. The output must preserve the source context behind each rate and document the checks that made the records comparable.
Once the payer, plan, provider, service, rate structure, and time period are resolved, the files can support decisions across the payer lifecycle.
Compare rates with relevant peers by payer, market, service, and billing code.
Identify meaningful gaps and bring evidence-backed targets into payer negotiations.
Test the economic effect of proposed rates, structures, and contract changes before signature.
Assess network participation, payer strategy, service-line priorities, and market expansion.
Prioritize services where comparable rate differences can materially affect reimbursement.
Use market evidence to focus investigation before moving to contract- and claim-level validation.
Lumivera structures the payer, provider, market, plan, and billing-code slice you need; resolves relevant identifiers; separates unusable or non-comparable records; and preserves source traceability. Results can be configured in the UI, exported to Excel, or delivered through an API.
Common questions
Transparency in Coverage is a federal framework requiring most group health plans and health insurance issuers to disclose pricing information, including public machine-readable files and consumer price-comparison capabilities.
The currently enforced machine-readable disclosures include an in-network rate file and an allowed-amount file for out-of-network providers. CMS maintains the current technical implementation guidance.
The file can include plan or issuer context, billing codes, provider NPI/TIN identifiers, negotiated types, negotiated rates, and expiration information for covered items and services.
Ghost or zombie rates are provider-service combinations listed in a file even though the provider would be unlikely to furnish that service. They should be filtered or flagged using provider specialty, service, and claims or utilization context where available.
The raw identifiers do not fully describe the provider organization, location, specialty, or relationship among entities. Mapping and consolidation prevent duplicate counting and support fair peer comparisons.
No. TiC data can support market analysis and investigation, but claim-level expected payment depends on the applicable contract terms, amendments, reimbursement logic, claim details, remittance, and payer-policy context.
Move from file mechanics to the provider decisions that validated rate evidence can support.
Bring the payer, plan, market, provider, and codes you need to understand. We’ll show you how Lumivera returns structured, traceable data for the decisions that follow.
Request a demo