Hospitals / WI

BELOIT HEALTH SYSTEM

BELOIT, WI

Ranks 3 of 24 scanned hospitals in WI. Ranks 15 of 502 scanned nationally.

Claim this hospital
Has blockers

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

54/100
1,582 line items scanned
Blockers
2
Warnings
1
Info
0

Source: https://beloithealthsystem.org/media/520100_beloithealthsystem_standardcharges.csv

Format: csv-tall · Schema v3.0 · Engine v0.2.0 · 8/19/2026, 5:17:17 PM

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

L1: Schema conformance

Required fields present on every line item

Blocker · HPT-L1-001

Every standard charge line item must include a description, at least one billing code and code type, a care setting, and a gross charge. Rows missing any of these can't be matched to a real service.

1582 of 1582 rows are missing a required field.

Citation: 45 CFR 180.50(b); CMS v3.0.0 CSV/JSON data dictionary, required-field list

Remediation: Fill in the description, code, code|type, setting, and standard_charge|gross columns for every row before republishing.

Affects 1,582 row(s).

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: attestation statement, 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.

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 "520100_beloithealthsystem_standardcharges.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.