Hospitals / MN

LAKEWOOD HEALTH SYSTEM

Name: LAKEWOOD HEALTH SYSTEM price transparency scorecard
Creator: MRF Preflight

STAPLES, MN

Ranks 29 of 47 scanned hospitals in MN. Ranks 1058 of 2446 scanned nationally.

Claim this hospital

Insurer rates vs. nearby hospitals

We compared the commercial rates in LAKEWOOD HEALTH SYSTEM's published price file with the same insurers' commercial rates at hospitals within 120 miles, across 13 common services (imaging, lab tests and emergency visits). No insurer pays LAKEWOOD HEALTH SYSTEM below the nearby median on most of the services compared.

Insurer	Below the nearby median
Blue Cross Blue Shield of Minnesota	7 of 13 services

The full benchmark lists every service for every insurer: this hospital's rate, the nearby 25th percentile, median and 75th percentile, and each nearby hospital's published rate with a link to its source file, so your team can check every number before a contract negotiation.

Get the full benchmark ($990)One-time PDF. Prefer an invoice or PO? Email sam@mrfpreflight.com.

Source: each hospital's own machine-readable file published under 45 CFR 180 (this hospital's file last updated 2026-09-11). Commercial plans only; Medicare Advantage and Medicaid plans are excluded. Where a file lists several plans for one insurer, we use the median of those plans. Hospitals sharing this hospital's tax ID are not counted as peers. Not legal or contracting advice.

Has warnings

This file has one or more warnings, worth a look, but nothing that blocks a good-faith attestation on its own.

94/100

111,162 line items scanned

Blockers: 0
Warnings: 1
Info: 0

Source: https://apps.para-hcfs.com/PTT/FinalLinks/Reports.aspx?dbName=dbLHCBAUDETTEMN&type=CDMWithoutLabel&fileType=CSV

Format: csv-tall · Schema v3.0 · Engine v0.2.7 · 10/31/2026, 7:28:56 PM

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

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 "Reports.aspx?dbName=dbLHCBAUDETTEMN&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.