2023-1-26 Communications Call

1. System Updates
2. New Macro Announcement
3. Data Source and Usage Updates
4. Final Action Issue and Update
5. Notebook Alternative Update

Scheduled CAP & CDR Maintenance Schedule

• February 3rd
• March 3rd

All events will begin at 8:00 pm ET and end approximately at 11:00 pm ET. Some events may require longer time, in which case users will be notified separately. A communication will be sent out once maintenance is complete. As a reminder, whenever there is maintenance on the environment, you will need to make sure all of your code and table changes are saved.

SAS Viya Lagging Issue

• Issue Description: SAS Viya users have reported intermittent lagging and freezing while utilizing the application.
• We will be starting a pilot to test a solution (Lustre) to improve stability and performance for SAS jobs when accessing data sets on SAS workbenches

• Provide CCSQ Community with a stable, scalable environment that can support increased user workloads, personal compute, and access to more advanced analytics capabilities
• Goal of improving user experience and developer productivity, while decreasing analysis runtimes
• Pilot conducted between June – October 2022 to explore alternative notebook and compute solutions – Databricks and Sagemaker

• Data Council Meeting Decision: Databricks was selected as the notebook alternative solution
• Development is underway by D&A Team:
  • Phase 1: Databricks Notebooks (Coming Soon!)
  • Phase 2: SAS Integration with Databricks Compute

Known Issues

• QMARS Longer Text Fields - 1/12/2021
  • Workaround: Consider using healthcare_service_qmars_ng if your DUA supports it
• Final Actions Claims Discrepancy – 09/19/2022
  • Final Actions in Claims data may change over time, as data refreshes will update Final Actions value in historical data
  • More information will be shared in today’s Communications Call
• HQR Data Discrepancy - 12/14/2022
  • Issue Description: HQR team identified an issue related to quality_measures_hqr_data_form. The years 2022 and 2023 numerator, denominator, and score fields are supposed to be the values for the whole year (Q1 – Q4), but instead they are the values submitted for Q4.
  • Resolution: HQR team is currently investigating the issue and working on a plan for resolution
• NCH Claims Data Issue - 1/25/23 (Data Duplication) 
  • Issue Description: A data duplication issue regarding Part A and B Claims with the specific NCH weekly processing date of 10/11/2022.
  • There are separate claims (different claim_sk values and beneficiary information and other claim field values) that have the same nch_clm_sgmt_link_num and nch_daily_proc_dt. These two fields are supposed to be used to concatenate the values to create a unique claim identifier.
  • Resolution: The D&A Team is currently working with NCH team to resolve the issue and more updates will be provided later
• QBIC Data Discrepancy Issue - 11-28-22 (Resolved)
  • Issue Description: There was an issue regarding the QBIC hospc_asmt_fed table that prevented history records from being deleted.
  • Resolution: The iQIES Team reloaded the hospc_asmt_fed and hospc_asmt_fed_hstry tables in QBIC with the corrected data. The CCSQ Data & Analytics Team has reloaded these tables in the CDR, and the issue is now resolved (as of 01/04/2023).

New Nursing Home Compare Crosswalk Documentation - Crosswalk Data Dictionary 

• Data & Analytics team has developed a crosswalk dictionary that maps the source data to columns within the CDR. The data dictionary can be found in the Data Catalog under compare_nursing_home
• Crosswalk also identifies any discrepancies in the CDR, particularly in snf and provider_info tables
• Long-term solution: D&A will work with CMS to resolve these discrepancies in the future

Claims Final Action Point in Time Logic

• Currently in the NCH Part A and B claims, there is a data issue with a field called clm_err_sgntr_sk that is preventing the ability to have a point in time logic for identifying final claims
• This does not affect the clm_finl_actn_ind field and pulling final claims, but only trying to pull final claims as of a previous point in time

Examples and Load Process 

• See the recording for a walk through of the examples and load processes

Next Steps

• Correct the claims final action code to not overwrite the clm_err_sgnt_sk values on previously submitted claims within a “claim chain”
• Run the NCH Part A/B weekly refresh with the updated claims final action code in parallel with the production weekly refresh
• Validate that the updated claims and “claim chains” have the correct and expected values for clm_err_sgnt_sk and compare with production claims that no additional changes were made to any other field values
• Identify business need for historical claims backfill