pikevillehospital.org's own certificate points to a different domain. The file itself is dated five and a half months ago.
Measured from Pikeville Medical Center's own published price transparency file under 45 CFR Part 180.50 and 180.60, 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Pikeville Medical Center | pikevillehospital.org (redirects to pmcky.org; file served via HospitalPriceDisclosure.com) | YES | standardcharges (JSON) | 3.0.0 | 2026-04-01 | YES | — | — | 17,224 | 10,041 |
SHARE OF EACH FILE CARRYING A PAYER-SPECIFIC RATE
The file's own date is five and a half months old
The published file's last_updated_on field reads 2026-04-01. Of its 17,224 priced entries, 58% carry an actual payer-specific dollar amount, and 3.9% carry the median/10th/90th percentile figures CMS has required since April, a requirement that postdates this file's own last refresh.
The domain CMS has on file for you doesn't resolve securely
The TLS certificate served on pikevillehospital.org is issued to pmcky.org, not to the domain itself. A browser or automated system checking the address CMS has on file gets a security warning before it ever reaches the file. The correct file is reachable at pmcky.org/cms-hpt.txt, which loads cleanly and names the same contact.
Type 2 NPI is present and the file structure itself is complete
The JSON file correctly encodes two Type 2 NPIs and a full standard-charge structure per service line. The gap here is currency, not format.
Is a refreshed file already sitting somewhere internally, just not yet republished at the address CMS has on file?
The first case here closed in 13 days in August 2025, which suggests updating this file is not usually a slow process once it's someone's task.
Is pmcky.org the correct long-term address for this filing, or is pikevillehospital.org meant to be the primary domain going forward?
Whichever domain CMS's record should point to, fixing the certificate mismatch resolves the immediate access problem regardless of which one wins.
FLAGGED, NOT ASSERTED — COULD NOT BE VERIFIED FROM OUTSIDE THE ORGANIZATION