Hospitals / HI

SAMUEL MAHELONA MEMORIAL HOSPITAL

KAPAA, HI

Ranks 4 of 9 scanned hospitals in HI. Ranks 17 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.

53/100
0 line items scanned
Blockers
2
Warnings
1
Info
1

Source: https://hhsc.pt.panaceainc.com/MRFDownload/hhsc/mahelona

Format: json · Schema v3.0 · Engine v0.2.0 · 8/19/2026, 5:13:10 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

JSON file has all required top-level metadata fields

Blocker · HPT-L1-006

A v3.0.0 JSON MRF must include hospital_name, last_updated_on, version, and an attestation object at the top level. Missing any of these means the file doesn't conform to the CMS JSON schema.

Missing top-level field(s): hospital_name, last_updated_on, version, attestation.

Citation: CMS v3.0.0 JSON schema, top-level required properties

Remediation: Add the missing top-level field(s) (hospital_name, last_updated_on, version, attestation) to the JSON file.

Affects 4 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, attester name.

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 has a plausible amount of charge and payer coverage

Info · HPT-L2-060

A hospital MRF with only a handful of line items or a single payer is very unlikely to represent the hospital's full standard charge list, even if the file otherwise validates cleanly.

File looks thin: only 0 line item(s).

Citation: CMS Hospital Price Transparency FAQ, completeness guidance

Remediation: Confirm the file actually contains the hospital's complete chargemaster and all contracted payers, not a partial export.

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 "mahelona" 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.