Hospitals / MT

CLARK FORK VALLEY HOSPITAL

Name: CLARK FORK VALLEY HOSPITAL price transparency scorecard
Creator: MRF Preflight

PLAINS, MT

Ranks 2 of 4 scanned hospitals in MT. Ranks 526 of 993 scanned nationally.

Claim this hospital

Has warnings

This file has one or more warnings, worth a look, but nothing that blocks a good-faith attestation on its own.

88/100

119,473 line items scanned

Blockers: 0
Warnings: 2
Info: 0

Source: https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fcfvh.goredde.com%2fEstimator%2fFiles%2f81-0475376_Clark_Fork_Valley_Hospital_standardcharges.csv&c=E,1,3gdRaAniKsYfRqedNKmhUi3oPbxeRufQ_Rpl3mEuoARmIKL2h5K1azsU_pucM_a5sXbOpXZElb3pHKT-1JGdH4NN4kU0I2OhGy8uE9kZ8C_JaI2dq5yupO9L2Q,,&typo=1

Format: csv-tall · Schema v3.0 · Engine v0.2.3 · 9/19/2026, 7:18:37 PM

Automated analysis of the public file, using the current MRF Preflight ruleset. Not legal advice. Hospitals may re-scan at any time.

Score history

L2: Completeness and plausibility

No placeholder values in price or payer fields

Warning · HPT-L2-014

Values 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.

92002 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 92,002 row(s).

L3: Discoverability compliance

MRF filename follows the CMS naming convention

Warning · HPT-L3-002

CMS 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 "url?a=https%3a%2f%2fcfvh.goredde.com%2fEstimator%2fFiles%2f81-0475376_Clark_Fork_Valley_Hospital_standardcharges.csv&c=E,1,3gdRaAniKsYfRqedNKmhUi3oPbxeRufQ_Rpl3mEuoARmIKL2h5K1azsU_pucM_a5sXbOpXZElb3pHKT-1JGdH4NN4kU0I2OhGy8uE9kZ8C_JaI2dq5yupO9L2Q,,&typo=1" 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.