Questions

For the HSC Ticket for Prerequisite Action 2 (confirm data files contain both sets of valid keys):

• Which environment does HealthSparq want these from?
  • HealthSparq is recommending that you provide the production keys - this will allow you to test NCCT, CLNR, etc when BCBSA will only have the production keys available
• Is HealthSparq expecting a sample PROVALTID file with PROD data or Full file?
  • The initial file provided for analysis can be a sample/subset of the PROVALTID data
  • A full file will be needed for processing - HealthSparq would prefer a full file if avaialble
  • When commenting in Planning Action 2 ticket - please indicate if the initial file is a full file v sample file
• Do plans need to send a full provider data set or just the PROVALT_ID file?
  • A full provider data set should be sent for analysis
• Once the analysis is complete, what can clients expect for feedback? i.e. a formal report or comments in the HSC ticket with the findings? If a report, what content should/could clients expect?
  • For the initial analysis, HealthSparq will provide each plan with confirmation that the data meets the format requirements
  • Any adverse findings will be documented and shared
  • This will documented in the Planning Action 1 ticket

For the HSC Ticket for Action 1: Confirm/Approve PDT/BPD Data Analysis Report, are the plans expected to confirm/approve the above mentioned activity?

• • Confirmation will be needed
  • If a subset of PROVALTID was provided, a full file will need to be sent

Next Steps

• Plans - submit PROVALT_ID files for analysis
• HealthSparq
  • Perform a data analysis on the file (format validation)
  • Provide feedback on data
• Plans - Confirm if results are as expected in the report
• HealthSparq
  • Update provider data intake to consume both sets of keys
  • Load PROVALTID file with both sets of valid keys into HealthSparq UAT for each plan
  • Update any carve out rules that use the keys (if applicable)