Services / 01—03
Compliance work that starts with evidence.
Choose the level of help that fits the moment: a fast risk signal, a defensible audit, or a partner who keeps the loop closed.
Risk Check
A fast, focused read on what your published machine-readable file exposes to CMS crawlers today.
Compliance Audit
A detailed, payer-by-payer audit that turns a machine-readable file into an executable remediation plan.
Remediation + Monitoring
We repair the file, verify its hosting, and keep watch so compliance does not disappear with the next data refresh.
The audit methodology
A clear readout beats a vague feeling.
Every service uses the same six-sided check. The difference is how far we take the signal after we find it.
Format integrity
JSON / CSV structure, required fields, usable values
Payer coverage
Negotiated rates across the payers you actually contract with
Cash prices
Discounted cash price and gross charge completeness
Shoppable services
Required service set, consumer-facing visibility, consistency
Crawler access
Public hosting, no login wall, no bot-blocking surprises
CMS rules
The edge cases automated checks and reviewers tend to surface
Where it goes wrong
Compliance rarely fails all at once.
Most hospitals that get cited have a file. The problem is that the file stopped describing the hospital some time ago, and nothing noticed.
The file drifts away from the truth
A machine-readable file is generated from a charge master, contracted rates, and revenue-cycle data. Every time one of those changes and the published artifact does not, the gap widens. Nobody is negligent — the file simply sits outside the process that produces the numbers it claims to report.
Three teams own one artifact
Pricing owns the charge master, contracting owns the negotiated rates, and the web team owns whatever URL the file is served from. Each can be individually correct while the published result is wrong, which is why remediation has to name an owner per finding rather than issue a general instruction to improve.
The URL you test is not always the URL that is read
A website migration, a CDN change, a redirect added for an unrelated reason, or a robots rule can quietly stop automated access to a file that still validates perfectly on disk. Nothing inside the hospital looks broken, because the file opens in a browser exactly as it always did.
What enforcement looks like
CMS reviews, may require a corrective action plan with a deadline, and can assess civil monetary penalties that accrue for each day of noncompliance. The daily maximum is reset by annual rulemaking and is lower for hospitals with 30 or fewer beds — which is why we describe the mechanism rather than quoting a figure that will be out of date by the time you read it. Confirm the current number against the rule.
Not legal advice
We provide operational compliance analysis: what your published file exposes, in what order to fix it, and verification that the fix is live. We are not a law firm and do not interpret the rule for you. Your compliance and legal teams own those decisions.
Not sure where to start?