Name the hospital MRF using the CMS-required format: the file name must include the hospital's license number or EIN (or another approved identifier), an indication of the file type, and a date component; consult the CMS MRF File Naming Wizard on the CMS Resources page for your specific situation.
Create a root-level TXT or JSON file hosted at the hospital's primary web domain that lists the MRF location URL, the contact information for the hospital's price transparency point of contact, and any required metadata fields as specified in the CMS technical instructions.
Link to the price transparency webpage from the hospital homepage footer using link text that meets the CMS discoverability standard so automated crawlers can locate the MRF.
Verify the root-level TXT file resolves at the expected location using an HTTP GET from outside the hospital network (test from a public IP) since CMS monitoring tools make external requests.
When the MRF is updated monthly, update the URL in the TXT file if the file path changes, and update the last_updated metadata in both the TXT file and the MRF itself.
Test discoverability using the CMS MRF Validator tool which also checks whether the TXT file and MRF link structure conform to the required disclosure format.
Known gotchas
The TXT disclosure file must be hosted at the root domain, not a subdomain; a TXT file at prices.hospital.org does not satisfy the requirement if the hospital's primary domain is hospital.org.
CMS automated monitoring crawlers request the TXT file without authentication; placing it behind a login page, VPN requirement, or CAPTCHA causes the hospital to appear non-compliant in CMS monitoring even if human visitors can access it.
Hospitals that operate multiple campuses under a single CCN may need only one MRF, but hospitals with multiple CCNs are generally required to publish separate compliant disclosures for each CCN.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp