11.13.26 MRF 3.0: Client readiness questions

  • Created  []
  • Updated  []

MRF 3.0: Client readiness questions

The 2026 federal rule changes the Transparency in Coverage machine-readable files. The first updated in-network and allowed-amount files are due April 1, 2027, with quarterly updates thereafter. CMS has published a draft 3.0 format; its field names and details can change before release.

We assume the information you provide today meets current requirements. These questions focus on what changes for 3.0. Existing input field names are examples; if an adapter, payer, or vendor supplies your data, answer using the equivalent source.

By December 1, 2026, please identify who owns each applicable change, the system or party that supplies the information, whether it is ready, and any blockers or expected readiness dates. A redacted example or sample mapping is helpful; do not send member-level data, identifiable claim data, or Social Security numbers. This is a planning checkpoint, not a CMS deadline.

1. Network identity

For each provider network, what stable ID will you use, and which public names are aliases versus separate networks? Can NTWK_MAPPING.Ntwk_Collection_Key serve as that ID, or do multiple keys merge into one network or one key cover multiple networks? Who negotiated each network's rates, and what arrangement applies (own, rented, host, carve-out, or other)? For an external network, what identifier helps map it to the external owner?

2. Plans and networks

At the CMS plan level, which networks can members use, and which providers and rates belong to each network? If this varies by product, how will those differences be identified and resolved into the draft's plan-level network references? If plans share a network name or ID but have different provider groups, contracts, or rates, how can the correct membership and rates for each plan be identified? What source establishes those relationships, including external networks?

What is the rate order? The CMS draft requires a distinct precedence for every network reference, including 1 for a plan's only network; 1 is consulted first.

3. Plan and reporting entity information

For each plan, where will the CMS product_type (or product_type_description) and market_segment (individual, small group, large group, or self-insured) come from? Who confirms how each existing Reporting_Entity_Type maps to the CMS reporting_entity.type values: group_health_plan, health_insurance_issuer, third_party_administrator, claims_clearinghouse, or other_third_party?

4. Specialty filtering

The rule excludes a provider's rate for a service when internal specialty or claims-adjudication rules indicate that the provider is unlikely to be reimbursed for it. What source supplies those rules and provider specialties, and how are missing or multiple specialties handled?

Can you provide the information in a form that lets the MRF publisher apply the exclusion without removing eligible rates for other providers in a shared rate group? Can it support billing-code and NUCC-specialty pairs for the taxonomy file, first due October 1, 2027? The exclusion applies from March 6, 2027; the taxonomy-file schema is still pending.

5. Changes to existing rates and arrangements

Your current INNETWORK_NEGOTIATED_RATE already supports percentage, fee-schedule, and derived rate types, as well as capitation arrangements. For any percentage rates, are they percentages of billed charges for which no dollar amount can be assigned before billing, as required by the CMS draft?

If capitation applies, can the existing rate be expressed in dollars per member per month, and can the existing covered-code mapping and Negotiation_Arrangement_Description support the draft's capitation object? If any rates use ICD or CSTM-ALL billing-code types, what supported billing-code standard and value identify them? The CMS draft does not list those types.

6. Out-of-network amounts, if applicable

For each market segment represented by your plans, who supplies the allowed-amount file? A file is still required when no item meets the threshold; it may have an empty out_of_network array.

Can the source cover the six-month service-date period beginning nine months before publication and omit an item or service with fewer than 11 different claims across the applicable market? For self-insured plans, which sponsors and plans belong in each file, including any combined file? The threshold is counted across plans in a combined file.

7. Attestation and delivery

Who is the responsible official for each reporting entity? Can one official cover all files, or do officials differ by plan or reporting entity? The rule requires the official's name; the CMS draft also calls for a title, with organization optional.

Can the responsible party confirm which attestation statements apply to each file? If another party attests under a written agreement, which party and official cover which files? If a payer or vendor supplies MRFs, who confirms its readiness and provides test and production files for April 1 and quarterly updates?

8. Later requirements

Who will provide the text and taxonomy files due October 1, 2027, the prescription-drug file expected in December 2027, and the utilization file due July 1, 2028? Who will update the website footer by September 6, 2027, and provide the text-file contact email, the page where the MRFs are published, and direct links to the files?

Optional planning question: payment provisions

Do your in-network facility contracts include outlier, stop-loss, or similar payment terms, and where are they held? These fields are draft-only; the date they become required is not yet defined. If a supplied provision's trigger or payment method uses estimated cost, the draft requires the applicable facility cost-to-charge ratios. The final schema may change.

Sources

<!-- regulation-source: 45 CFR 147.210(a)(2)(xi), 147.212; Departments' FAQs Part 75 --> <!-- schema-draft-source: CMSgov/price-transparency-guide@7d95e08e7c68dd3a1cfac111d2780149bfd19f82 schemas/table-of-contents/README.md, schemas/in-network-rates/README.md, schemas/allowed-amounts/README.md -->

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request