GEISINGER JERSEY SHORE HOSPITAL
JERSEY SHORE, PA
Ranks 32 of 41 scanned hospitals in PA. Ranks 524 of 993 scanned nationally.
This file has one or more warnings, worth a look, but nothing that blocks a good-faith attestation on its own.
- Blockers
- 0
- Warnings
- 2
- Info
- 0
Source: https://www.geisinger.org/-/media/OneGeisinger/pdfs/ghs/patient-care/patients-and-visitors/billing-and-insurance/hosp-charges-csv/24-0792115_Geisinger-Jersey-Shore-Hospital_standardcharges
Format: csv-tall · Schema v3.0 · Engine v0.2.3 · 9/19/2026, 7:23:20 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
No placeholder values in price or payer fields
Warning · HPT-L2-014Values 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.
3282 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 3,282 row(s).
L3: Discoverability compliance
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 "24-0792115_Geisinger-Jersey-Shore-Hospital_standardcharges" 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.