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
This field is incorrectly named in the plural: billing_code_modifierS
The CMS Validator did not catch this error.
Keyark caught this error because our load process includes enhanced checking, going beyond the baseline checks provided by the CMS Validator. In addition to verifying that only JSON fields names in the spec exist, we generate basic statistics, such as counts of distinct EIN, NPI and billing codes by type, to quickly gauge the completeness of the MRF.
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
-
Just sharing a heads-up that the optional but important field billing_code_modifier is misnamed in the In-Network MRF in the most recent monthly release. In particular this was encountered in https://AllegianceCostTransparency.com/1001/innet/2022-10-01_allegiance_in-network-2.json.gz
This field is incorrectly named in the plural: billing_code_modifierS
The CMS Validator did not catch this error.
Keyark caught this error because our load process includes enhanced checking, going beyond the baseline checks provided by the CMS Validator. In addition to verifying that only JSON fields names in the spec exist, we generate basic statistics, such as counts of distinct EIN, NPI and billing codes by type, to quickly gauge the completeness of the MRF.
Beta Was this translation helpful? Give feedback.
All reactions