CMS transparency, made clear +1 315 953 2456
All services

01 / Start here

Risk Check
Know your exposure before the next automated review.

A fast, focused read on what your published machine-readable file exposes to CMS crawlers today.

Run the free check Within 24 hoursFree

Sample readout

hospital_mrf.json

Illustrative

Risk signal

74/100

Review
Last 30 days+12 signal points
Payer coverageHigh
Gross chargesOK
Crawler accessMedium
Audit trailReady
6 audit lensesOpen report

ILLUSTRATIVE EXAMPLE — a sample report layout, not a real hospital's data.

What is included

A deliverable you can use on Monday.

No mystery metrics. No black-box recommendations. Each service is built to move from signal to decision without adding another layer of translation.

01

Full MRF validation against the CMS specification

Grounded in what your published file is actually doing right now.

02

High / medium / low risk summary

Prioritized so your team knows what to handle first.

03

Plain-English explanation of what a reviewer could cite

Written for the people who own the next step.

04

No-obligation next-step recommendation

Written for the people who own the next step.

In detail

What this work actually involves.

The mechanics, written out so you can judge whether they match the problem you have.

What the check actually reads

It reads your file the way an automated reviewer does — not the way it looks in a browser. That means starting at the URL, following it without a login or a click-through, and confirming that what arrives is the file rather than a page that builds the file in JavaScript after it loads.

Then it checks the substance. A machine-readable file has to carry gross charges, discounted cash prices, and negotiated rates that name the payer and the plan, with a de-identified minimum and maximum alongside the payer-specific figures. Each item needs a description and a billing code. The shoppable-services set has to be present as well: the services CMS designates, plus the additional ones each hospital selects, in a consumer-facing display.

The output separates what is missing from what is present but unusable. Those are different problems with different owners inside a hospital.

The failures that are invisible from the inside

Most hospitals we look at believe their file is fine, and most of them are partly right — the file usually exists and usually opens. The recurring problems are quieter than that.

A file served behind a redirect chain a crawler will not follow. A download that starts from a button rather than a URL, so a bot gets the button's page instead of the data. A CSV whose column headers do not match the published schema, which makes a technically complete file unparseable. A file that is valid but republished under a new filename each quarter, so the URL that was discovered stops answering. A payer that is contracted but simply absent from the file.

None of these look like a problem from inside the hospital, because a person opening the file in a spreadsheet sees correct data. The gap is between how a person retrieves it and how a machine does.

What this is not

This is operational analysis, not legal advice, and the report does not determine anyone's liability. It tells you what is exposed, what a reviewer would see, and the order in which we would fix it — and you are free to take that to your own team and stop there.

Your first signal

Start with the URL you already have.

We’ll check structure, payer coverage, pricing, shoppable services, accessibility, and the CMS rules that tie them together.

Results delivered within 24 hours
Human-reviewed before we send
No obligation to buy anything else

Free, no obligation

Get your risk score before the next review.

01

Paste the URL where your hospital publishes its machine-readable file. If you’re not sure, send your hospital website instead.

Your email is used to deliver the report. Never shared. Never added to a list.

Keep exploring