JsonReader VS price-transparency-guide

The library I used (https://github.com/pcrov/JsonReader) does it in memory with no part files. That was beneficial in my use case as each node was then directly stored in a database.

The problem is that its all released in files in JSON code. The file from the above link has links to 2374 other JSON files that are compressed into multipart JSON.GZ files and some of these are 25 gigabytes and larger. Literally terabytes of data.

Neither of these are implemented via HL7 or FHIR. CMS has defined a new "machine readable format" to implement the regulation: https://github.com/CMSgov/price-transparency-guide

CMS was very particular in the format they required payers to use. You can even check out the spec yourself on GitHub. Unfortunately their requirements don’t make a lot of sense from a data engineering standpoint.

You can review the provided example schemas here: https://github.com/CMSgov/price-transparency-guide/tree/master/schemas

The health insurance companies are now required to publish this and in fact the rule went into effect July 1 2022.

Look up price transparency by CMS (the data will be published in this format: https://github.com/CMSgov/price-transparency-guide)

Note: the data being published by payors in machine readable format (MRF) is MASSIVE - terrabytes of data. Example: https://transparency-in-coverage.uhc.com/

This may be useful in figuring out how to parse the contents.

FYI, there is a similar effort going on that requires all health plans to host machine readable files containing negotiated rates by provider and procedure code by 2022-01-01: https://github.com/CMSgov/price-transparency-guide