search

CMSgov / price-transparency-guide

The technical implementation guide for the tri-departmental price transparency rule.
354 stars 107 forks source link

Reporting as files is poor design #676

Closed cigzigwon closed 1 year ago

cigzigwon commented 1 year ago

We are consuming large files but the influx of them with their flaws just sucks away time and resources.

Since this data is being sourced from databases it doesn't make sense to publish these files because nobody has technology to consume them nor audit them.

This would be much simpler for all parties if the data was provisioned as "Hypermedia based JSON". Easier to find and read data in this fashion and can still be provisioned statically on the web.

If I'm a consumer of a machine readable file and don't have the technology to consume it and once I get it find out that the data is un-readable... Who pays for that?

cigzigwon commented 1 year ago

eg. https://example.com/cms_medicare/in-network-rates/provider_references/1

Much simpler for me a consumer to leverage "hypermedia" w/linking to consume these references or any other context. It's much easier to build an API against a database then try to constantly get some performance gain out of streaming data.

And smaller businesses are never going to be able to consume these in a timely fashion. By time they get the data it will be outdated. This is not helping our economy as a whole.