Allowed amounts
4 fields
- Median, 10th and 90th percentile in dollars, plus count
- From 835 data, 12 to 15 month lookback; next highest observed value when between two amounts [4]
The contract mechanism question has operational weight: an outlier provision or a stop-loss threshold is not a single dollar charge, so today it is described in words. CMS is asking whether it should be data [2].
| Area | What CMS asked | If it became a rule |
|---|---|---|
| MRF standardization | Approaches to improve comparability and standardization of the information reported in machine-readable files | Tighter templates and fewer free-text escape hatches |
| Contract mechanisms | How to report outlier payments, stop-loss provisions, rate tiering and carve-outs | Structured fields for the parts of a contract that today sit in notes, or nowhere |
| Free-text accuracy | Improving the accuracy and completeness of free-text field reporting | Validation rules or controlled vocabularies for the notes fields |
| Consumer display | Enhancing the consumer-friendly display; whether to modify or eliminate deemed compliance for internet-based price estimator tools | Hospitals relying on an estimator might need a 300-service display |
| Shoppable services and displayed prices | Updating the required shoppable services list; clarifying which ancillary and bundled items a displayed price includes | A revised 70-service list and explicit bundling rules |
The attestation's third part already requires the fee schedule or components behind a formula contract. The RFI asks whether those components should be structured fields.
4 fields
3 parts
Named official
Type 2 NPIs
Preparation that pays off whether or not the RFI becomes a rule.
Read the RFI as a list of fields CMS wishes it had. The hospitals that can already produce them will have the easiest 2028.
No. It contains a request for information on strengthening the standardization and comparability of price transparency data. Any change to the requirements would come through a future proposed rule.
Standardizing machine-readable file data, reporting contract mechanisms such as outlier payments, stop-loss provisions, rate tiering and carve-outs, improving free-text field accuracy, whether to modify or eliminate deemed compliance for internet-based price estimator tools, updating the shoppable services list, and clarifying which ancillary and bundled items displayed prices include.
August 31, 2026 at 11:59 PM EDT, on docket CMS-2026-2344.
Inventory contract mechanisms by payer, review every free-text field in the current file against the contract, know whether you could post a 300-service display if estimator deemed compliance ended, and keep the 2026 allowed-amount and attestation audit current.
Preparation that pays off whether or not the RFI becomes a rule.
We read your payer contracts for outliers, stop-loss, tiering and carve-outs, compare them to the free-text fields in your current file, and hand revenue integrity a worksheet that answers the RFI and the attestation at once.