2022-1-27 CCSQ D&A Townhall

Agenda

• General Announcements
• System Updates
• Data Source & Usage Updates
• MDM Data Updates & Workaround
• Q&A

Slack Channel: Strength in Numbers - Community Driven Collaboration 

• We are introducing the CCSQ Data & Analytics Slack Channel, #ccsq_data_analytics!
• This is a community-driven collaboration channel for creating connections with other members of the CCSQ Data and Analytics community, motivating each other and facilitating learning opportunities.
• In this channel, you can submit your questions, respond to threads to contribute ideas, or share your best practices with others within the user community.
• All users with SAS Viya Slack licenses will/have been added to our channel.
• Please note that all announcements regarding CCSQ Data & Analytics will continue via email as some of our user community do not have access to Slack.
• Please continue to post issues to the #help-service-center-sos Slack channel.
• Please note that the D&A Team will not be monitoring this channel closely, as this channel is designed for users to collaborate with one another.
• If you have questions about Slack access, reach out to your COR and the Contract Engagement Team.

Important! - When collaborating with other users, it is your responsibility to not share any PHI, PII, or sensitive information.

SAS Viya Issues

Lagging Issues

• SAS Viya users have reported intermittent lagging and freezing while utilizing the application.
• Due to the issue's intermittent nature, some users have reported that their issue has gone away by the time that a help desk ticket has been created.
• In order to capture the details for the D&A Team to investigate, please follow these instructions found within the Known Issues Log
• After following these instructions, please provide the information via a helpdesk ticket

Issues Accessing Data

• Issue Description: SAS Viya users have reported issues accessing data within Hive due to issues with two of the environment’s worker nodes.
• What to Expect: The team is currently investigating the issue and is working to triage these worker nodes. More details about the issue will be shared shortly this afternoon.
• Affected Communities: SAS Viya Users
• Call to Action: If you are experiencing this issue, please open a helpdesk ticket 

Maintenance Schedule

• Updating dates for scheduled CAP & CDR Maintenance events: 
  • February 4
  • March 4
  • April 1
  • May 6
  • June 3

• All events will begin at 8:00 pm ET and end approximately at 11:00pm ET. 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.

EQRS Data Availability 

• The D&A Team is currently in the pilot stage of receiving data from the EQRS Team involving one user group
• Once the data is available, the D&A team will communicate to the organizations who have the appropriate DUA entry

Known Issues

• BIC MBI Sequence - 8/25/2021
  • Ongoing – TBD
• QMARS Appeals - 6/18/2021
  • Ongoing – TBD
  • Consider using healthcare_service_qmars_ng if your DUA supports it
• QMARS - 1/12/2021
  • Ongoing - TBD
  • Consider using healthcare_service_qmars_ng if your DUA supports it

Please watch the presentation for a full walkthrough. 

Workarounds: 

SAS Workaround for INT to BIGINT

• BIGINT is known to be incompatible with SAS. MDM Surrogate keys(sk) defined as BIGINT and are generated with 19 digits whereas SAS can hold only 15.
  • Additional information can be found here: http://support.sas.com/kb/39/831.html
• Manual workaround
  • Convert BIGINT column to char to ensure no value is lost. Ex. select cast(sk_col1 as char(19)) from mdm_table1

SAS Workaround for STRING

• Conversion issues can occur when querying data from CDR Hive with SAS Viya.
  • Hive STRING columns default to 32767 when Hadoop data is read into SAS. This can be unnecessarily large for short STRING columns and might lead to performance issues
  • It can also truncate Hadoop STRING columns that are greater than 32767
  • Additional reference can be found here: 48815 - Issues with various data types occur when you convert data from Hive to SAS® with SAS/ACCESS® Interface to Hadoop

• Remediation has been applied in all CDR managed dataset
  • New table attribute added SET TBLPROPERTIES (‘SASFMT: sk_col1'='char(max_length)’) during table publish process.
• Other manual workaround when encounter performance issue by casting the column to appropriate length
  • Ex: SELECT CAST(SUBSTR(sk_col1 , 1, max_length) AS CHAR(max_length)) AS casted_sk_col1 FROM mdm_table1

1. Could you define MDM? What kind of data lives there? 
   A - MDM hosts provider data from PMI/SPP and PECOS as well as beneficiary data. 
2. Which channel in Slack should we report issues?
   A - #help-service-center-sos
   
3. Is this data and its changes live in the CDR as of today? 
   A - Yes, MDM data is already live and available within the CDR. It is available under provider_pmi_data