JACKSON-MADISON COUNTY GENERAL HOSPITAL
JACKSON, TN
Ranks 6 of 8 scanned hospitals in TN. Ranks 636 of 993 scanned nationally.
This file has one or more blockers, issues that should be resolved before signing the attestation.
- Blockers
- 1
- Warnings
- 2
- Info
- 0
Source: https://www.wth.org/wp-content/uploads/standard-charges/62-6010402_JH_standard_Charges.csv
Format: csv-tall · Schema v3.0 · Engine v0.2.3 · 10/3/2026, 12:23:11 PM
Automated analysis of the public file, using the current MRF Preflight ruleset. Not legal advice. Hospitals may re-scan at any time.
L1: Schema conformance
Required fields present on every line item
Blocker · HPT-L1-001Every standard charge line item must include a description, at least one billing code and code type, a care setting, and at least one standard charge (gross charge, discounted cash price, or a payer-specific negotiated dollar amount, percentage, or algorithm). Rows missing any of these can't be matched to a real service or priced.
40 of 84820 rows are missing a required field.
Citation: 45 CFR 180.50(b); CMS v3.0.0 CSV/JSON data dictionary, required-field list
Remediation: Fill in the description, code, code|type, and setting for every row, and make sure every row carries at least one standard charge, before republishing.
Affects 40 row(s).
L2: Completeness and plausibility
No placeholder values in price or payer fields
Warning · HPT-L2-014Values like 999999999, 'N/A', or an empty payer name are common placeholders hospitals leave in when a real number wasn't ready. They pass schema validation but carry no real pricing information.
13890 rows contain a placeholder value instead of real data.
Citation: CMS Hospital Price Transparency FAQ, data completeness guidance
Remediation: Replace placeholder values with the real negotiated rate, or omit the row if the rate genuinely doesn't exist for that payer/plan.
Affects 13,890 row(s).
L3: Discoverability compliance
MRF filename follows the CMS naming convention
Warning · HPT-L3-002CMS expects the MRF filename to follow <ein>_<hospital-name>_standardcharges.<ext>. A non-conforming filename makes the file harder for automated tools (including CMS's own review process) to identify.
Filename "62-6010402_JH_standard_Charges.csv" doesn't match <ein>_<hospital-name>_standardcharges.<ext>.
Citation: 45 CFR 180.50(b)(1)(i) — file naming convention
Remediation: Rename the file to <ein>_<hospital-name>_standardcharges.csv (or .json), using the hospital's EIN with no dashes.
1 blocker found in this file
The Attestation Evidence Packet documents every finding above with the exact file location, what was checked, and when — as a dated PDF with a SHA-256 hash, so what was true at generation time stays provable after the file changes. One hospital, one-time.