HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
CMSgov
price-transparency-guide
Ruby2021–2025
CMSgov / price-transparency-guide

price-transparency-guide

The technical implementation guide for the tri-departmental price transparency rule.

8Distinct people
11Mentions
1Explicit recommenders
462GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The technical implementation guide for the tri-departmental price transparency rule.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

The author has replied to me, and shared these great examples of transparent prices: https://github.com/CMSgov/price-transparency-guide/tree/mast... Along with this fantastic…

logicallee used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year11 dated mentions

Observed mentions: 2021-04-14 14:42:50 UTC to 2025-10-10 03:32:24 UTC.

0123452021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC312
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC505
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

11 sources
But that's entirely dependent on the data - if you read the article, you'll see that the author is pointing out how different datasets are reporting different values for the same healthcare service. A correct, properly labeled example is just that - a document where values are accurate rather than misreported. If you want to get a sense of what a correct, properly labeled example might look like, you should visit the CMS's guidance [1]. Health insurers should be providing documents that follow the format described there, and most importantly, reporting values that are accurate. [1] https://github.com/CMSgov/price-transparency-guide
In New health insurance “transparency data” looks suspiciously wrong
I'm the author. When I write articles I have to make a choice: make them readable by the public, or detailed enough to satisfy the experts. I try to strike a balance, but I can't have both. Please take a look at the CMS Price Transparency Guide https://github.com/CMSgov/price-transparency-guide and familiarize yourself with the schema. You can also take a look at the federal ruling: https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-... The metadata you're talking about is specified in the files themselves. I've limited my search to fee-for-service (non-capitated, non-derived, non-bundled) institutional claims. You can write to me if you have more questions. alec@dolthub.com
In New health insurance “transparency data” looks suspiciously wrong
I'm the author. Take an example like this https://github.com/CMSgov/price-transparency-guide/discussio... I don't know how closely you've worked with this data -- you clearly have some kind of expertise -- but how do you explain this? The insurance companies had 18 months to talk to the CMS and ask for a better data model. If they're not able to explain how much things cost with 5 different negotiated types -- negotiated, percentage, derived, fee schedule, and capitation -- then they should have asked for another one. The hospital and insurance rates are both fee-for-service base rates for items billed individually. If there's some nuance in interpreting how "fee for service" "dollar amount negotiated" goes, definitely write to me and let me know. I talked with experts in healthcare pricing before I published this. You can write to me at
Read the rest
alec@dolthub.com if you wanna hit me with more questions.
In New health insurance “transparency data” looks suspiciously wrong
They are doing that as well. They are posting general requirements, as well as providing details on specific situations. From the main project @ https://github.com/CMSgov/price-transparency-guide Section: Overview > All machine-readable files must [...] made available to the public without restrictions that would impede the re-use of that information. Section: Public Discoverability > These machine-readable files post made available to the public without restrictions that would impede the re-use of that information.
In Instructions around the usage of meta robot tags and robots.txt files

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.