Hospitals / AR

ARKANSAS CHILDREN'S HOSPITAL

LITTLE ROCK, AR

Ranks 5 of 11 scanned hospitals in AR. Ranks 655 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.

68/100
718,831 line items scanned
Blockers
1
Warnings
2
Info
0

Source: https://apim.services.craneware.com/api-pricing-transparency/api/public/d3b6b861569568a87f28dfbc66463efd/charges/mrf

Format: csv-wide · Schema v3.0 · Engine v0.2.3 · 9/19/2026, 7:08:22 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-014

Values 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.

523100 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 523,100 row(s).

L3: Discoverability compliance

MRF is publicly reachable without authentication or a JS wall

Blocker · HPT-L3-003

The file must be fetchable by an anonymous, unauthenticated HTTP request. A login-gated page, a JavaScript-rendered viewer with no direct file link, or a 403/404 response means automated tools (including this one, CMS, and any payer trying to reconcile rates) can't actually read the file.

https://apim.services.craneware.com/api-pricing-transparency/api/public/d3b6b861569568a87f28dfbc66463efd/charges/mrf returned status 404.

Citation: 45 CFR 180.50(b) — MRF must be accessible to the public without barriers

Remediation: Serve the MRF from a plain, unauthenticated URL that returns the raw CSV or JSON file directly, with no login or JavaScript required.

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