MRF file name follows the CMS convention

What it checks

The price file's name follows the pattern CMS sets out, which includes the hospital's tax ID and the words "standardcharges".

Checked by Care Carta. Care Carta's own check, for a requirement CMS's validator does not test.

How hospitals did

Results as of Oct 5, 2026. The most common reasons are on the Publication and accessibility page.

How Care Carta decides

A name the file is served under matches the CMS convention: the response's Content-Disposition name, the last segment of the listed address (or of the address inside an email-link wrapper such as Outlook Safe Links or Proofpoint URL Defense, which the detail names), or the last segment of the address the file is finally served from after redirects. For a ZIP or GZIP, the price file inside is judged and the archive's name is reported. Fails when no name conforms or none names a file. Judged even when the file cannot be prepared, accepting either .csv or .json. Reuse requires the same URL and bytes.

Scope: The official validator library exports filename logic, but the CLI validation path does not invoke it.

Depends on: MRF downloads to an automated client

Version

Today's results all use this ruleset. A check never changes without a new ruleset. Full catalog (JSON)