Hospitals / UT

CASTLEVIEW HOSPITAL

PRICE, UT

Ranks 4 of 19 scanned hospitals in UT. Ranks 672 of 998 scanned nationally.

Has blockers

This file has one or more blockers, issues that should be resolved before signing the attestation.

68/100
135,404 line items scanned
Blockers
1
Warnings
2
Info
0

Source: https://www.castleviewhospital.net/docs/ahcastleviewhospitallibraries/hcl/mrf3q26/621762357_castleview-hospital_standardcharges.csv.zip

Format: csv-tall · Schema v3.0 · Engine v0.2.3 · 9/19/2026, 6:52:26 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

Percentile allowed amounts are internally consistent

Blocker · HPT-L2-020

Where median, 10th percentile, and 90th percentile allowed amounts are reported, the 10th percentile must be less than or equal to the median, which must be less than or equal to the 90th percentile, and the count of amounts behind the calculation must be greater than zero.

115 rows have out-of-order percentiles or a non-positive count.

Citation: CY2026 OPPS final rule, 45 CFR 180.50(b)(4) — median/10th/90th percentile allowed amounts + count

Remediation: Recompute the percentile fields from the underlying remittance data so 10th <= median <= 90th, and ensure count reflects the number of amounts behind the calculation.

Affects 115 row(s).

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.

135404 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 135,404 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 "621762357_castleview-hospital_standardcharges.csv.zip" 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.