Before HSQ processes files
- INN file being referenced needs to be sent to HSQ
- INN file needs to be referenced in control file (if applicable).
- Cina INN file needs to be referenced in leased_network_mapping file awith MRF_type = I or CI
- Plan Collection Key associated with INN file needs to be associated with Plans-Products in the PlanDetails
- Provider reference files associated with with INN file need to be sent to HSQ
- Provider reference files need to be in control file (if applicable).
- NPIs in the Provider reference files need to match NPIs in Provider Search Data
- ProviderKey/LocationKeys that match the NPIs in Provider Search Data need to match ProviderKey/Location Provider_Identifiers file.
- Rates in INN files are applicable for plan-product
- Ex. INN files could contain CSTM-ALL billing_code_type, CSTM-00 billing_code with a rate associated. This means that any bi have that rate associated with the NPIs in the provider group or provider reference file containing the provider group for that limit)
- MRF JSON files need to be compliant and usable (next slide)
MRF JSON files need to be compliant and usable
- Provider reference files associated with with INN file need to be included in dataset
- INN file needs to have no errors when processed through CMS Validator Tool
- https://github.com/CMSgov/price-transparency-guide-validator
- Provider Reference needs to contain valid identifiers
Common Issues
- Provider Groups referenced in INN MRF file does not have a provider reference file associated with it.
- Missing required fields in INN MRF rate objects (ex. Billing Code Type)
- Provider NPI not valid.
