FORMAT COMPARISON
CMS Hospital MRF JSON vs. CSV: Choosing a Validation Path
CMS permits JSON and CSV templates for hospital price-transparency files. The right validation approach depends on the chosen representation, file size, data pipeline, and review workflow.
JSON
JSON expresses nested relationships directly and can be validated against a published schema, but very large files require streaming rather than loading the entire document into memory.
- Strong machine-readable structure
- Natural schema-validation path
- Nested errors can be harder for nontechnical reviewers to locate
Wide and tall CSV
CSV is familiar to spreadsheet and data-operations teams, while template selection and repeated headers or relationships require format-specific validation.
- Easier ad hoc inspection
- Potentially simpler exports from tabular systems
- Requires careful handling of headers, delimiters, quoting, and conditional columns
Choose for operations, not aesthetics
Use the format your production pipeline can generate consistently, test at realistic scale, and support with reproducible quality controls. Switching formats does not resolve inaccurate source data.