Hospitals / NV

BOULDER CITY HOSPITAL

BOULDER CITY, NV

Ranks 7 of 13 scanned hospitals in NV. Ranks 733 of 998 scanned nationally.

Has blockers

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

48/100
51,548 line items scanned
Blockers
2
Warnings
2
Info
0

Source: https://bchcares.org/880065829_boulder-city-hospital_standard-charges.csv

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

Attestation block is present with a named signing official

Blocker · HPT-L2-030

The file must encode the CMS attestation statement, an explicit confirmation flag, and the name of the CEO, president, or other senior official affirming the data is true, accurate, and complete. A missing or blank attester name means no one is actually attesting to this file.

Missing: attester name.

Citation: CY2026 OPPS final rule, 45 CFR 180.50(b)(1)(vii) — attestation requirement effective Jan 1 2026, enforced Apr 1 2026

Remediation: Add the CMS attestation statement, set confirm_attestation to true, and fill in attester_name with the signing official's full name.

Type 2 organizational NPIs pass checksum validation

Blocker · HPT-L2-040

Every Type 2 NPI encoded in the file must be a structurally valid 10-digit National Provider Identifier (the check digit must match). A malformed NPI can't be verified against NPPES and breaks any downstream taxonomy-based lookup.

1 Type 2 NPI(s) fail checksum validation: TRUE.

Citation: CY2026 OPPS final rule — Type 2 NPI requirement for taxonomy codes beginning '27'/'28'

Remediation: Correct the Type 2 NPI to the organization's real, currently-active NPI as registered with NPPES.

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.

48133 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 48,133 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 "880065829_boulder-city-hospital_standard-charges.csv" 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.

2 blockers 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.