# CMS Transparency in Coverage Rule: How Machine-Readable Files (MRFs) Impact Health Plans
## Key Facts
- **October 2020:** The U.S. Departments of Labor, Treasury, and Health and Human Services issued the **Transparency in Coverage Rule (CMS-9915-F)** to make healthcare price information accessible to consumers **prior to obtaining services and being billed**. (Section: “Introduction”)
- **Phase I — July 1, 2022:** Health plans must publish **in-network rate Machine Readable Files (MRF)** and **allowed amount rate MRF** files as the rule begins rolling out in **three phases**. (Section: “What does this mean for health plans?”)
- **Phase II — January 1, 2023:** Health plans must implement an **internet-based price comparison tool** covering **500 shop-able items and services**. (Section: “What does this mean for health plans?”)
- **Phase III — January 1, 2024:** The internet-based price comparison tool expands to **all items and services not covered in Phase II**. (Section: “What does this mean for health plans?”)
- **Monthly requirement:** To maintain compliance, plans must **update MRFs monthly**, using **CMS-preferred file formats (JSON, XML, YAML) available through HTTPS**. (Section: “Maintaining Compliance”)
- **Enforcement start date:** If plans are not compliant, **CMS enforcement authorities may take action beginning July 1, 2022**, including **civil penalties and corrective action plans**. (Section: “Consequences of Non-Compliance”)
## Summary
### What the Transparency in Coverage Rule (CMS-9915-F) requires—and when
The Transparency in Coverage Rule (CMS-9915-F) is intended to address the problem that healthcare costs are often unknown until after services are delivered and a bill is issued. The rule, issued in **October 2020** by the U.S. Departments of Labor, Treasury, and Health and Human Services, aims to make rates more readily available so consumers can compare costs before receiving care. (Section: “Introduction”)
The rollout is described in **three phases**. **Phase I (July 1, 2022)** focuses on publishing **in-network rate MRFs** and **allowed amount rate MRFs**. **Phase II (January 1, 2023)** introduces an **internet-based price comparison tool** for **500 shop-able items and services**. **Phase III (January 1, 2024)** expands that tool to **all items and services not covered in Phase II**. (Section: “What does this mean for health plans?”)
### What Machine-Readable Files (MRFs) are and what “compliance” includes
An **MRF (machine-readable file)** is defined as a digital file that can be imported into a computer system for further processing. For Phase I compliance, the content outlines that plans must provide both: (1) an **In-Network MRF** (rates for covered items and services between plans and in-network providers) and (2) an **Allowed Amount MRF** (historical billed charges from, and allowed amounts for, out-of-network providers). The document also lists compliance checkpoints, including showing contracted provider rates, presenting historical payments for out-of-network providers, using CMS-preferred formats (**JSON, XML, YAML** through **HTTPS**), and **updating MRFs monthly**. (Sections: “What is an MRF?” and “Maintaining Compliance”)
### How Payment Accuracy Edge supports MRF generation, file delivery, and rollout
The document describes a solution using **Payment Accuracy Edge (formerly HealthEdge Source™)** to generate MRFs aligned to selected configurations, with scheduling that supports **monthly** updates and **on-demand** generation. It outlines a step-action flow including user role assignment (RBAC), configuring job parameters (such as **state(s)**, **provider types**, **date/time**, **frequency**, and options like **compressing MRF files**), monitoring job progress, receiving email notification upon file availability, and saving files to a customer-preferred **SFTP** location for download. (Sections: “Our Solution,” “Maintaining Compliance,” and “Step-Action Overview of MRF Generation in Payment Accuracy Edge”)
The document also specifies environment and data design details, including producing MRFs for **Professional and Facility** types, outputting files in **JSON format**, and providing data dictionary updates. It provides a naming convention example: `YYYYMMDD-HHMM_Configurationnumber_State_ProviderType.json` (example shown: `20211214-1644_2000_OK_MC05.json`) and notes that files containing multiple provider types may be **1 gigabyte** and numbered sequentially (e.g., `_01`, `_02`, `_03`). It proposes a folder structure of `“/PreProd/MRF/”` and `“/Prod/MRF/”`. (Section: “Data Design”)
Finally, the rollout strategy presented includes phases labeled **Assessment**, **Implementation I**, **Implementation II**, **Implementation III**, and **Production**, culminating in **MRF Go-Live**. (Section: “Our Rollout Strategy”)