Key Takeaways

Well done! Let's review some key takeaways from this course:

Implementation Paths:

  • There are three implementation paths depending on the type of customer you are, this course focuses on scenario 3 where you generate and host your MRF files and send them to Kyruus Health to populate the Kyruus Connect for Payers Cost tool

Connecting Data Files to One Another:

  • As a scenario 3 customer, you are responsible for providing the following files:
    • Plan details, out of network allowed amount, region xWalk, POS mapping
  • Kyruus Health takes your INN MRF files and reverse engineers the data into the specification set to create the remaining files 
  • Your cost index is a combination of these files 

Considerations for Implementation:

  • Scenario 3 clients send their MRF JSON files and some files from the Price Transparency Data Specification to create the cost index within the cost estimator tool
  • Implementation path: create your MRF files, prepare supplemental Price Transparency Data files, send your MRF and Price Transparency data files to Kyruus Health; Kyruus Health uses the MRF JSON and Price Transparency file to power the cost estimator tool
  • Files required to submit: plan details, external MRF mapping, out of network allowed amounts, POS mapping, region xWalk

TiC Data Specification File Overview:

  • This file includes all of the information you need to fill out as well as detailed instructions and workflows to show you how the data is extracted and mapped into Kyruus Connect for Payers
  • Allows you to understand what data is required, what the proper format should be, how it connects to other files, etc.

TiC Companion Guide Overview:

  • This guide shows the implementation requirements you need to submit, including the data that will populate the Kyruus Connect for Payers Cost tool, and  how the files connect to the mandate requirements
  • In conjunction with the data set, this file will answer many of your questions in the implementations process 

Connecting the Dots Between the Data and the UI:

  • The path for scenario 3 customers: 
  1. Understand your implementation path
  2. Know which files are required for your implementation path
  3. Review how the files connect to come together and deliver against your implementation needs