Platform · Hospital price transparency files

Hospital Price Transparency Data

Every US hospital publishes what it charges and what payers pay. The files are enormous, inconsistent, and changed again in 2026.

Hospital price transparency data covers the machine-readable files US hospitals must publish under federal rules: standard charges including gross charges, discounted cash prices and payer-specific negotiated charges. From 1 January 2026, estimated allowed amounts gave way to actual allowed amounts — median, 10th and 90th percentiles and a count — with an executive attestation. So every figure keeps its file, field and version, and no "true price" is invented.

The data is public by law. Making it usable without changing what it says is the work.

Get a free sample See sample data

Free pilot on your own Hospital price transparency files list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

hospital_mrf_sample.jsonl LIVE FEED

{"hospital_id":"as published","file_version":"as published","attestation_present":true} {"billing_code":"as published","charge_type":"payer_negotiated","payer_name":"as published","amount":1840.00} {"charge_type":"allowed_median","allowed_count":212,"true_price":null}

illustrative sample rows · USkeeping each figure's provenance · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Hospital price transparency files or its owners. Hospital price transparency files and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Hospital price transparency files at a glance

How we handle Hospital price transparency files specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Source: Hospital machine-readable files (45 CFR 180)
Contents: Gross, cash, payer-specific negotiated, min and max
2026 change: Actual allowed amounts: median, p10, p90, count
Also 2026: Executive attestation; organisational NPIs
Enforcement: From 1 April 2026
So: file, field, version on every figure
Derived prices: None invented
Refresh: Per hospital, as files are updated

Platform specifics

Keeping each figure's provenance

These are the reasons a Hospital price transparency files dataset needs its own handling rather than a shared retail schema.

What the files contain

Hospitals publish one machine-readable file of standard charges, plus shoppable services information. The CY2026 rule changed several things: actual allowed amounts drawn from remittance data replace estimates, a hospital executive must attest to accuracy and completeness, and files must include organisational NPIs.

hospital_id, file_url, file_version, file_last_updated on every figure.
charge_type — gross, discounted_cash, payer_negotiated, min, max, allowed_median, allowed_p10, allowed_p90 — exactly as the file labels it.
payer and plan names kept as published; a normalised payer name is a separate, labelled field.
Codes — billing codes and their types — kept as published.

Normalisation, and what we do not do

What can be normalised

Schemas and formats differ between hospitals and versions. We parse each into one structure, keeping the original field names alongside. Normalised payer names, code descriptions and service groupings are derived fields, labelled.

Attestation and completeness

The attestation is recorded as a field of the file. A file that is missing, stale or fails to parse is recorded as such, dated, and not filled from elsewhere.

What we do not do

Invent a single "true price", fill missing figures, judge a hospital's compliance, or touch any patient or claims data — the files contain none, and nothing is joined to any.

Scope

What we collect on Hospital price transparency files, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

hospital_id, file_url, file_version on every figure
charge_type exactly as the file labels it
2026 allowed-amount fields: median, p10, p90, count
Attestation recorded as a field
Payer and plan names as published
Normalised payer names as labelled derived fields
Billing codes and code types as published
Missing or unparseable files recorded, dated
Refresh per hospital as files update

❌ What we do not, and why

A single "true price" invented
Missing figures filled from elsewhere
Hospital compliance judged
Original field names discarded
Any patient or claims data

Core Hospital price transparency files fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
hospital_id / organisational_npi	As published
file_url / file_version / file_last_updated	Provenance
attestation_present	As in the file
billing_code / code_type	As published
description	As published
setting	Inpatient or outpatient, as published
charge_type	Exactly as labelled
amount	As published
payer_name / plan_name	As published
payer_normalised_derived	Labelled
allowed_count	Data points, 2026 fields

Use cases

What teams do with Hospital price transparency files data

Negotiated rate benchmarking

Payer-specific rates across hospitals, with provenance.

Cash price comparison

Discounted cash prices by service and hospital.

2026 allowed-amount analysis

Medians and percentiles from actual remittance data.

File quality monitoring

Which hospitals publish, update and attest.

The 24-hour sample — run on your sources, not ours

Send us a Hospital price transparency files item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Hospital price transparency files is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Hospital price transparency files data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what healthcare & pharmacy data covers, and a Hospital price transparency files-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Hospital price transparency files data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

From 1 January 2026, actual allowed amounts (median, 10th and 90th percentiles and a count) replaced estimates, files need an executive attestation and organisational NPIs, with enforcement from 1 April 2026.

We give the published figures, each with its type and source. We do not combine them into a single invented price.

We parse each into one structure and keep the original field names beside it.

That is recorded, dated. Nothing is filled in.

No, and we join them to none.

It depends on the number of hospitals and refresh frequency; these files are large.

Talk to us.

See real Hospital price transparency files data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner