Hospitals / SD

BROOKINGS HEALTH SYSTEM

BROOKINGS, SD

Ranks 1 of 14 scanned hospitals in SD. Ranks 13 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
34,347 line items scanned
Blockers
2
Warnings
1
Info
0

Source: https://www.brookingshealth.org/sites/default/files/2020-12/466000069_Brookings-Hospital_standardcharges.csv

Format: csv-tall · Schema v3.0 · Engine v0.2.0 · 8/19/2026, 5:17:24 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.

34347 of 34347 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 34,347 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.

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.

File was updated within the last 12 months

Warning · HPT-L2-050

last_updated_on should reflect a recent refresh of the underlying charge data. A file that hasn't been updated in over a year is likely showing stale prices, even if it otherwise validates.

last_updated_on ("1000018") is not a parseable date.

Citation: 45 CFR 180.50(c) — MRF must be updated at least annually

Remediation: Regenerate and republish the file with a current last_updated_on date reflecting the actual data refresh.