The address CMS has on file renders as a WordPress page, not the machine-readable file it's supposed to serve.
Measured against JTDMH.org (Joint Township District Memorial Hospital, doing business as Grand Lake Health System) and CMS's own enforcement record, retrieved Sep 18, 2026.
| Facility | Host domain | cms-hpt.txt | Filename | Schema | Last updated | HTTP last-mod | Type 2 NPI | Attester | Payers | Rows | Rows w/ rate |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Grand Lake Health System | JTDMH.org | YES | n/a — no mrf-url returned | n/a | n/a | n/a | NO | n/a | 0 | 0 | 0 |
SHARE OF EACH FILE CARRYING A PAYER-SPECIFIC RATE
The address CMS has on file for JTDMH.org's price transparency filing returns a rendered WordPress page — a design template with layout and font declarations — rather than the plain-text cms-hpt.txt CMS's spec calls for. No mrf-url line is present anywhere in the response, so there is no machine-readable file to parse from this address.
cms-hpt.txt renders as a page template, not a file
Fetching JTDMH.org/cms-hpt.txt returns CSS declarations and layout markup (grid templates, border radii, color variables) consistent with a WordPress theme rendering a missing or misconfigured page, rather than the plain-text file format the address is supposed to serve.
Was a real file ever live at this address, or has it been misconfigured since before the 2024 case closed?
The prior case resolved in about three months. Knowing whether the underlying file infrastructure changed since then, versus something that broke afterward, changes where to start.
Is there a different, correct URL for the file that cms-hpt.txt should be pointing to instead of resolving to the site's own homepage template?
A misrouted address is usually a faster fix than a missing file.
FLAGGED, NOT ASSERTED — COULD NOT BE VERIFIED FROM OUTSIDE THE ORGANIZATION