Clone or download the CMSgov/price-transparency-guide-validator repository and follow its README to install dependencies.
Point the validator at your MRF JSON file using the command-line interface, specifying the target schema version that matches your file's schema_version field.
Review the validator output for errors distinguishing required-field violations (hard failures) from optional-field warnings.
Fix any reported errors — common issues include missing attestation fields, incorrect data types for numeric amount fields, and NPI format mismatches.
Re-run the validator until the output reports zero errors, then retain the passing run log as compliance evidence.
As an alternative, use the CMS web-based validation tool at the CMS Resources page to upload the file and receive immediate feedback without a local install.
Known gotchas
The validator enforces the schema version declared inside the file itself, so mismatches between the file's stated schema_version and the actual structure produce cryptic errors rather than a clear version mismatch message.
Large MRF files (multi-gigabyte) may time out or exhaust memory in the web-based tool; use the CLI validator with sufficient heap allocation for files over a few hundred megabytes.
The validator does not verify the accuracy of calculated amounts — it only checks structure and type conformance, so a plausible but incorrect median allowed amount will pass validation.
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