PRICE TRANSPARENCY REVIEW 2026-09-18
PRICE TRANSPARENCY REVIEW · Hendricks Community Hospital

Hendricks Community Hospital

CMS's own record sends a patient looking for a price straight to a spreadsheet, not a price.

Measured from Hendricks Community Hospital's own published files under 45 CFR Part 180.50 and 180.60, retrieved Sep 18, 2026. What closes that gap is a working consumer price estimator built off the same file already published, so a patient sees what they'd actually owe on their plan instead of a raw CSV.

Facilities1
Files retrieved2026-09-18T21:40:00Z UTC
Measured againsteCFR current to 2026-09-01
Prepared bySuperscript
1 file
doubles as both the machine-readable spreadsheet and the listed consumer price page
0 of 1,030
rows carrying the CY2026 median/percentile dollar fields the rule now requires
17 months
since the posted file was last touched (Mar 2025)
01The portfolio§180.20, §180.30
FacilityLegal entityLocationCCNType BedsOwnershipMedicare since
Hendricks Community HospitalHendricks Community Hospital Assn & Retirement HomeHendricks, MN241339CAH Critical Access Hospital24Nonprofit2002-07-01

As a Critical Access Hospital, Medicare Part B outpatient coinsurance here is calculated as a share of the hospital's charges rather than a negotiated allowed amount — a real, long-standing CMS rule specific to CAHs, not a pricing error.

02What’s published today§180.50(d), schema v3.0
FacilityHost domaincms-hpt.txtFilenameSchema Last updatedHTTP last-modType 2 NPIAttester PayersRowsRows w/ rate
Hendricks Community Hospitalhendrickshosp.orgYESPrice Transparency File2.0.03/26/2025Fri, 11 Apr 2025 18:26:28 GMTNOHendricks Community Hospital51,0301,030

SHARE OF EACH FILE CARRYING A PAYER-SPECIFIC RATE

03The charge file§180.50
GAP (2)

The consumer price page and the machine-readable file are the same spreadsheet

CMS's own record lists Hendricks Community Hospital's consumer source page as 410307617_hendricks-community-hospital-association_standardcharges.csv — the identical file filed as the machine-readable standard charges data, not a separate consumer-friendly display or estimator. A patient who follows CMS's own link looking for a price lands on a raw spreadsheet instead.

The file in force is still on the pre-2026 schema

The posted file self-reports version 2.0.0 and a last_updated_on of March 26, 2025. CMS's CY2026 rule, in force since April 1, 2026, requires the file to carry median, 10th percentile and 90th percentile allowed amounts in actual dollars, sourced from remittance data, plus Type 2 (organizational) NPIs. None of that is present here — not one of the 1,030 priced rows carries a percentile field, and no Type 2 NPI appears anywhere in the file. The file hasn't moved since before the rule that now governs it took effect.

WATCH (1)

The attestation names the hospital, not a person

The CY2026 rule also requires the attestation to name the CEO, president, or the senior official responsible for encoding the data. The posted attestation currently reads Hendricks Community Hospital in that field rather than a named individual.

CLEAR (1)

Every priced row carries a real payer-specific rate

Across all 1,030 data rows and 5 payers (Avera Health, BCBS of Minnesota, HealthPartners, Medica, UnitedHealthcare), every single row carries an actual negotiated dollar amount — there's no gap here between what the file claims to price and what it actually prices.

04Enforcement record§180.70, .80, .90
2024-09-19
Hendricks Community Hospital — Warning Notice issued (case 2667)
2024-12-30
Hendricks Community Hospital — CAP Request issued (case 2667)
2025-04-10
Hendricks Community Hospital — CAP Request issued (case 2667)
2025-04-14
Hendricks Community Hospital — Closure Notice issued (case 2667)
2026-07-01
Hendricks Community Hospital — Warning Notice issued (case 8130)
05Open questions
01

Was the July 2026 warning notice (case 8130) opened specifically against the CY2026 percentile/NPI fields, or something else in the file?

CMS's enforcement data doesn't name which deficiency was cited. If it's the percentile fields, that's a data problem, not a display problem, and the fix path is different.

02

Is the March 2025 file update still considered current internally, or is a refresh already in progress?

The prior case (2667) closed four days after that file was touched. If a refresh is already underway, some of this may already be moot.

Reproducibility
06Method & sources

FLAGGED, NOT ASSERTED — COULD NOT BE VERIFIED FROM OUTSIDE THE ORGANIZATION