Hospitals / CT

SHARON HOSPITAL

SHARON, CT

Ranks 5 of 10 scanned hospitals in CT. Ranks 565 of 993 scanned nationally.

Claim this hospital
Has blockers

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

74/100
153,365 line items scanned
Blockers
1
Warnings
1
Info
0

Source: https://www.northwell.edu/sites/northwell.edu/files/machine-readable-files/815056290_sharon-hospital_standardcharges.zip

Format: json · Schema v3.0 · Engine v0.2.3 · 10/3/2026, 12:28:44 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

Type 2 organizational NPIs pass checksum validation

Blocker · HPT-L2-040

Every Type 2 NPI encoded in the file must be a structurally valid 10-digit National Provider Identifier (the check digit must match). A malformed NPI can't be verified against NPPES and breaks any downstream taxonomy-based lookup.

1 Type 2 NPI(s) fail checksum validation: 306960596.

Citation: CY2026 OPPS final rule — Type 2 NPI requirement for taxonomy codes beginning '27'/'28'

Remediation: Correct the Type 2 NPI to the organization's real, currently-active NPI as registered with NPPES.

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 "815056290_sharon-hospital_standardcharges.zip" 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.

1 blocker 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.