2022-5-19 Communications Call

1. Monthly User Experience Satisfaction Survey

2.Data Catalog Study

3.System Updates

a. Background Submit Issues

b. Lagging Issues

c. False Long Running Jobs Notifications

d. Maintenance Schedule

4. Data Source and Usage Updates

a. Known Issues

5.User Collaboration Wiki Articles – Highlights

6.QuickSight Demo and Vision

7.Q&A  

HCD Process

• User Interviews & Problem Definition
• Identify & Pilot a Solution
• Usability, UAT & Iterate

Discover Phase: Data Catalog Study

Discover Phase Goal: Discover User’s Needs

Empathize:

• Interviewed 15 CCSQ Data & Analytics community members
• Data Consumers & a Data Contributor

How: user interviews

Define:

• Categorized findings and work on how to address, prioritize, plan, implement

How: synthesize feedback

Data Catalog Study Categories

• Documentation
• Data Dictionary
• Missing Data Elements
• Confluence
• Standardization
• Suggestions

Data Catalog Feedback

1.Documentation:

• Need data model that shows relationship between data (joins, keys, etc.) and CDR/IDR mapping
• Some data dictionaries are unavailable or missing
• Need clear variable details: description, when added, meaning, possible values
• FAQs need to stay updated

2.Data Dictionary:

• Need more detailed data, field descriptions (e.g. data type, field length)
• Need consistent level of information across all datasets
• Want instructions on how to use catalog
• Dictionary needs to be searchable
• Examples of data would be helpful
• Want more useful table layouts with more information (e.g. associated coding for variable)

3.Missing Data Elements:

• Data does not match the dates
• Variables, fields missing descriptions
• CDR does not have data prior to 2017 in excel file

4.CMS – Confluence:

• Data Catalog page layout not user-friendly (e.g. have to scroll right)
• It’s overwhelming – so much information
• Difficult to differentiate between what is clickable vs text
• Have to download excel to preview file

5.Standardization

• Improve data structure: how collected, questions asked, mapping
• Provide code for linking the data
• Table layout needs improvement

Data Catalog: Identified Area for Improvements

• Search through VIYA would be helpful2
• Attach original questionnaires to survey data
• Think about new users and details for how to navigate
• More collaboration between ADOs and business-people who use the CDR
• Consolidate data dictionary with table layout into 1 file
• Provide instructions on what to expect
• Create a more direct way for questions to get answered
• Table of content with list of tables and schemas
• Issue log for data catalog vs communications and known issues
• Ability to publish documents through Confluence (so it’s quicker)
• Automate data dictionary
• Allow to write HIVE code to understand database better

Design Phase - Next Steps

Design Phase Goal: Identify a solution to pilot

Ideate:

• Consider solutions that solve for the user’s defined problem

How: identify possible solutions – system, product: Data Dictionary Template Study

Pilot:

• Narrow down possible solutions to pilot

How: pilot the solution

Background Submit Issues - Resolved!

• Issue Description: Some users were reporting issues with background submitting in SAS Viya. Some were reporting spinning while others were reporting that log files were not showing up or populating after the job completed.
• Users are no longer reporting this issue and additional testing has discovered the issue has been resolved. 

Lagging Issues 

• Issue Description: SAS Viya users have reported intermittent lagging and freezing while utilizing the application.
• Resizing efforts took place during the April 22nd maintenance event to help address this issue. Additional resizing efforts will take place in future maintenance events to help ensure system stability. More specifics of when these resizing changes will be applied will be shared shortly.

False Long-Running Job Email Notification Issue 

• Issue Description: Some users may have been receiving long-running SAS job email notifications for SAS jobs that do not exist.
• A user can disregard this email notification if the PS macro in SAS Viya reveals that they do not have any running PIDs.
• The D&A team is planning to review the automated long running job notification script to ensure that it does not send out any false alerts to users.

Scheduled CAP & CDR Maintenance Schedule

• June 3rd
• July 1st
• August 5th

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

Known Issues

• BIC MBI Sequence - 8/25/2021
  • Ongoing – TBD
• QMARS Longer Text Fields - 1/12/2021
  • Ongoing - TBD
  • Consider using healthcare_service_qmars_ng if your DUA supports it

• Geography Data for DBRCM Appeals Data – Noah Johnson
• User Collaboration Wiki link

Overview

• Enterprise Business Intelligence (BI) tool fully managed, serverless, and native on AWS.
• Integrates with data sources on AWS (Redshift, S3) & upload your own data (like flat files in .csv or Excel).
• Create interactive dashboards and reports for Users to make informed data driven decisions.
• No User License needed to create, share, or view dashboards.

Accessing QuickSight

1.Go to https://idm.cms.gov.

2.Use your HARP or EUA ID to log in.

3.Select “CCSQ QuickSight”.

QuickSight Assets

• Dashboards: Published Analysis that is read-only & shared with your end users.
• Analyses: Create charts, tables, analytics, & visualizations using Datasets.
• Datasets: Specific data from a data source that can be prepared/transformed into data that is used in Analysis.
• Data Source: Where data originates (S3, Redshift, flat files like CSV or Excel) and connects to Datasets.

QuickSight Datasets

• As a QuickSight Developer OR Deployer, you can create Datasets

QuickSight Analyses

• As a QuickSight Developer OR Deployer, you can create Analyses from your available Dataset(s)

QuickSight Dashboards

• As a QuickSight Developer OR Deployer, you can publish an Analysis to a Dashboard
• As a QuickSight Developer OR Deployer, you control who can access your dashboard

CCSQ QuickSight Role Permissions

• Shared Folders is a way for your program to manage your QuickSight assets and access

CCSQ QuickSight Fast Tips

• Access to too many dashboards?
  • Star your Favorites

• Does your Program have many dashboards to share?

  • Use Confluence to create a landing page for navigation to QuickSight Dashboards & use the relay URL to automatically authenticate with HARP

CCSQ QuickSight Resources

• Getting Started Instructions
• Quick Start Guide
• Knowledge Base

CCSQ QuickSight Features In the Works

• Establishing User access to SAS Viya Workbenches mounted on S3 buckets to QuickSight
  • This will eliminate the need to download files from your Workbench only to upload them into QuickSight for use.
  • This will enable the QuickSight backup and disaster recovery system to include these S3 files and subsequent QuickSight assets.
• Establish connectivity from QuickSight to data in CDR
  • This will enable your ability to create datasets in QuickSight using data directly from the CDR

1. Q - On QuickSight I get a screen asking me to include my email and that monthly fees would apply - is there an issue?
   A - QuickSight will not charge. You can ignore the message.
2. Q - Do you have any pros and cons of using SAS Visual Analytics vs. QuickSight?     

      A - QuickSight is the preferred visualization tool. There is robust support for QuickSight. Support is also available for SAS Visual                     Analytics.  

   3. Q - Is there a training course on how to use QIES data for analytics or a data coach I could reach out to for questions?
       A - Reach out to the QuickSight help channel on Slack at help-quicksight or submit a Help Desk ticket via Slack channel help-service-center-sos for help with SAS Viya.

   4. Q - As access to new databases become available to external users, is this the appropriate forum to seek feedback/support in           accessing the data within those databases or an alternate space?
      A - We are working on a method to standardize data publishing.