11.13.26 Compliance Insights Info Session | TiC 3.0 Recap

  • Created  []
  • Updated  []


1. Immediate action items and key dates

These are the dated items shared in the session. CMS dates are as presented by RevSpring and are expected dates unless noted.

  • Now: Review the readiness questions and checklist that RevSpring will share alongside the recording and notes.
    • Note which group you are in (we build your files, we host your files, or cost tool only). See section 5.
    • Confirm whether member emulation is set up for every TiC-regulated line of business, and tell your RevSpring team as soon as possible if you need support.
    • Start thinking about who your attesting official will be.
  • November 20, 2026: RevSpring is targeting this date to share its draft 3.0 spec with you. The spec is a draft and subject to change.
  • December 1, 2026: RevSpring plans to share a client-by-client analysis and report showing what needs to change in your data.
  • December 7, 2026: The rule takes effect, but nothing is due on this date.
  • December 1, 2026 to January 1, 2027: Get your data ready to support the spec. These are not hard cutoffs, but the sooner RevSpring has your data, the more time there is for testing and feedback.
  • January 1, 2027: Phone cost sharing applies. This is the first requirement with a due date.
  • January 1 to March 6, 2027: Testing period.
  • February 1, 2027: CMS is expected to publish the final schema for phase one of 3.0. A draft schema has already been posted.
  • March 6, 2027: Phase one rules apply: network-level files, rate exclusions, and attestation. This is also the date for final sign-off and delivery of your 3.0 files.
  • April 1, 2027: First quarterly posting of 3.0 files.

Later in 2027 (phase two, expected)

  • June 2027: CMS is expected to post the schema for the taxonomy and utilization files.
  • September to October 2027: The text file and website footer link requirement applies.
  • October 1, 2027: The taxonomy file is expected to be posted.
  • December 2027: The prescription file is expected to begin posting.

2. What is changing with your MRF files

These changes were covered in detail in the previous session, and that recording is available. Here is the high-level view.

  • One file per provider network: The original rule asked for reporting per plan. MRF 3.0 moves to one file per provider network, with your plans mapped to that network.
  • Unlikely rates removed: Rates for services that a provider is unlikely to be paid for must be excluded.
  • Rates as dollar amounts: The original rule required every rate to be a dollar amount. CMS later allowed percentage of billed charges when a dollar amount cannot be known in advance, and that allowance is now written into the rule. RevSpring supports this today.
  • Out-of-network files by market: The threshold drops from 20 claims to 11. CMS made this change because most of these files were nearly empty, and the goal is more real data about out-of-network bills.
  • Quarterly posting: In-network and out-of-network files move from monthly to quarterly posting.

3. New requirements in TiC 3.0

  • Phone cost sharing: Personalized cost sharing must be available by phone. This applies from January 1, 2027.
  • Attestation: Every file must name who is legally responsible for the accuracy of the data, and that person must be a senior official.
  • Open format and public access: One open standards format must be available without a login or blocking. RevSpring already supports this today.
  • Text file and footer link: A plain text file in your website's root folder gives the location of your files and a monitored contact email. Your website footer must also include a link reading "price transparency" or "transparency and coverage" that goes to your landing page.
  • Three new context files: The taxonomy file, prescription (RX) file, and utilization file are due later in 2027.

4. Phone cost sharing and member emulation

RevSpring supports the phone cost sharing requirement through a feature called member emulation.

  • How it works: When a member calls in, your customer service representative (CSR) selects that member in your CSR tool and signs in to the cost estimator as that member through single sign-on (SSO). After authentication, the CSR can pick a procedure and walk through the personalized results with the member while they stay on the phone.
  • Two changes are needed: The teams that manage your CSR tool and your SSO work together to make them.
    • Build the CSR step: CSRs need a way to select the active member and a button that signs them in as that member.
    • Extend your SSO: Your SSO needs to pass CSR details along with the sign-in. You can do this with a new SSO connection or by extending your current one. The RevSpring SSO guide has a section on how the SAML payload should be updated, and RevSpring will include that documentation alongside the presentation.
  • Before you start: Make sure your member cost estimator is live, your SSO is working, and your negotiated rates are loaded. If all three are in place, you do not need to change your data or any settings. The work is in the CSR step and the SSO extension.
  • What RevSpring does: If you reuse your existing SSO, there is not much for RevSpring to do. If you need a new SSO connection, RevSpring will work with you to set it up. Reach out to your account team to review your specific tools and configuration.

5. Which group you are in

What is needed from you depends on how RevSpring supports you with TiC 3.0. Please note which group you fall into.

  • We build your MRF files: You send RevSpring your data. RevSpring builds, hosts, and publishes your files and powers your cost tool.
  • We host your files: You or your vendor create your own MRFs. RevSpring publishes them for you and powers your cost tool.
  • Cost tool only: Your payer publishes your MRF files. RevSpring reads those files and uses them to power your cost tool.

Across all three groups, plan details and mapping are key. This is the data that describes your plans and how they connect to your networks and files. Network-level files and unlikely-rate filtering are the key items for the group where RevSpring builds your files. Even where the work falls mostly on RevSpring, input from you is still needed.

6. What it means for you, by group

If RevSpring builds your files

  • Stable network IDs: Review your current provider networks and identify a stable ID for each one. RevSpring is moving away from the plan collection key and toward the stable network ID, so providers and rates will be grouped by network, which is what a 3.0 in-network MRF looks like.
  • New network and plan fields: CMS is requesting new fields for networks and plans. RevSpring will share a list soon.
  • Unlikely rates: RevSpring expects clients to apply the exclusion of unlikely rates themselves. If you need help, contact your account manager.
  • Validation rules: CMS has added more restrictions on billing codes and other fields. RevSpring will update its validation rules and highlight the changes in future documentation.
  • Allowed amount files: These move to the market segment level, so expect some changes to the claims input data. More information will come in future documentation.
  • Attesting official: Every MRF needs an attesting official, so start thinking about who that person is.
  • Draft schema: RevSpring will share its draft schema in the coming weeks. It is a draft and subject to change, and RevSpring cannot finalize its schema with confidence until CMS finalizes theirs.

If RevSpring hosts your files

  • Talk to your MRF creator: Start engaging with whoever creates your MRFs, and understand the 3.0 timeline so RevSpring can process your data correctly.
  • Mapping and plan details files: Because allowed amount files move to market segment and in-network files move to the network level, expect changes to your external MRF mapping and plan details files. The linking keys between these files will need to be updated, and RevSpring's spec is changing to account for this.
  • More file types: RevSpring expects to host additional file types, including prescription, utilization, taxonomy, and the plain text file. More details will come when CMS publishes the draft spec for those files.
  • Attesting official: RevSpring will need your attesting official's information, so start thinking about who that person is.

If you are cost tool only

  • Vendor timeline: Confirm your vendor's 3.0 MRF timeline and relay it to RevSpring.
  • Linking keys: Confirm the linking keys in your plan details and external MRF mapping files.
  • Product code mapping: Make sure the product code to network ID mapping is correct.

7. RevSpring project milestones

  • Spec work so far: Over the last several weeks, the RevSpring team has reviewed the draft schema CMS shared and has been building a draft 3.0 spec. The spec is in review now.
  • By November 20: RevSpring expects to share the draft spec with you.
  • Between now and December 1: RevSpring is doing client-by-client analyses of what is needed from you and what needs to change in your data. The analysis and report will be shared by December 1.
  • December 1 to January 1: You make changes so your data supports the spec.
  • January 1 to March 6: Testing, with back-and-forth feedback. These dates are not hard cutoffs. If you cannot send data by January 1, that is okay.
  • March 6: Final sign-off and delivery of the 3.0 files.
  • Pilot partner: RevSpring would like a client who can move quickly to pilot the spec. Piloting helps confirm that the spec supports TiC 3.0. If you are interested, let your client team know.
  • Timeline concerns: If the March 6 date is a concern for your team, you are encouraged to share that feedback with CMS. RevSpring is also partnering with CMS and has seen comments about the timeline in public forums. The more CMS hears about timing concerns, the more information it has when considering the readiness timeline for phase one.

What's next

  • Draft spec: RevSpring is targeting November 20 to share it with you.
  • Your analysis: RevSpring will share a client-by-client report on where you stand by December 1. You then make changes, ideally ahead of January 1, before testing begins.
  • Documentation: RevSpring will post help articles, readiness questions, checklists, and other documentation in Zendesk. Links will follow shortly after the session.
  • Later phases: Much of this session focused on phase one, which is due by March 6. RevSpring does not yet have all the answers on the utilization and text file requirements because CMS has not posted those schemas. RevSpring will keep sharing information as it learns more from CMS and from you.
  • Monthly sessions: These webinars continue monthly. The next session is Friday, December 11.
     

Additional Resources

Questions or help

Your client team is your first contact for questions or anything specific to you. For data or spec questions, submit a request through Help Desk.

 

Disclaimer: This summary is informational only and is not legal or compliance advice. CMS dates and timelines are as presented during the session and are subject to change.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request