You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Priority Health HMO In-Network Rate MRF has what looks to be “synthetic” price data for MS-DRG, but the professional service (CPT) data looks real. Can MRF production fail in this fashion, such that data for certain billing code types can be valid, while other types are invalid?
For the curious, here are screenshots of the analysis by keyark.com
The first hint of a problem was from a quick visual inspection of the data. Notice how the negotiated_rate “percentage” is decimal and out-of-range (I was expecting an integer in the range of 100 to 125):
And Counts on negotiated_rate show repetition of the same (unreal) values:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The Priority Health HMO In-Network Rate MRF has what looks to be “synthetic” price data for MS-DRG, but the professional service (CPT) data looks real. Can MRF production fail in this fashion, such that data for certain billing code types can be valid, while other types are invalid?
For the curious, here are screenshots of the analysis by keyark.com
The first hint of a problem was from a quick visual inspection of the data. Notice how the negotiated_rate “percentage” is decimal and out-of-range (I was expecting an integer in the range of 100 to 125):
And Counts on negotiated_rate show repetition of the same (unreal) values:
MRF is a 468MB GZ compressed file:
http://priorityhealthtransparencymrfs.s3-website-us-east-1.amazonaws.com/2022_09_01_priority_health_HMO_in-network-rates.zip
Beta Was this translation helpful? Give feedback.
All reactions