ROSELAND COMMUNITY HOSPITAL
CHICAGO, IL
Ranks 44 of 47 scanned hospitals in IL. Ranks 709 of 998 scanned nationally.
This file has one or more blockers, issues that should be resolved before signing the attestation.
- Blockers
- 2
- Warnings
- 1
- Info
- 0
Source: https://apps.para-hcfs.com/PTT/FinalLinks/Reports.aspx?dbName=dbRCHCHICAGOIL&type=CDMWithoutLabel&fileType=CSV
Format: csv-tall · Schema v3.0 · Engine v0.2.3 · 9/19/2026, 7:13:49 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-020Where 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.
15566 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 15,566 row(s).
L3: Discoverability compliance
cms-hpt.txt is present at the domain root and points at a live MRF
Blocker · HPT-L3-001Every hospital must publish a cms-hpt.txt file at the root of its public domain listing the location(s) of its machine-readable file(s). Without it, the MRF is effectively undiscoverable to anyone who doesn't already have the direct URL.
cms-hpt.txt at https://roselandhospital.org/cms-hpt.txt exists but doesn't contain a recognizable MRF URL.
Citation: CMS Hospital Price Transparency txt-file FAQ; 45 CFR 180.50(e)
Remediation: Publish a cms-hpt.txt file at https://<your-domain>/cms-hpt.txt listing the full URL(s) of your MRF(s), one per line.
MRF filename follows the CMS naming convention
Warning · HPT-L3-002CMS 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 "Reports.aspx?dbName=dbRCHCHICAGOIL&type=CDMWithoutLabel&fileType=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.