Page History

1. System Updates
   1. File Lock Issues - Resolved!
   2. Lagging Issues
   3. GitHub Issue
   4. Maintenance Schedule - Updated! 
2. Data Sources and Usage Updates
   1. Known Issues
   2. Claims Part A Update
   3. BIC Updates
3. Monthly Satisfaction Survey
4. Human Centered Design and the CAP/CDR User Experience
5. Q&A

SAS Viya Issues

File Lock Issues - Resolved!

• Issue Description: SAS Viya users have reported file lock errors when reading data from their workbenches during SAS job runs

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

• The Data & Analytics Team will address this issue during tomorrow’s maintenance event.

Github Issue

• 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 continues to work with the SAS Vendor to obtain a patch that will resolve the issue. More updates will be shared once more information about the patch is available.
• Affected Communities: SAS Viya Users
• Call to Action: A new workaround has been published on this issue. Please follow these instructions found within the Known Issues Log

• The Data & Analytics Team will address this issue during tomorrow’s maintenance event.

Scheduled CAP & CDR Maintenance 

Scheduled CAP & CDR Maintenance Schedule

• April 22nd (Added!) 
• May 6th
• June 3rd

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.

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

Claims Part A Updates

• New fields to be added in mid-April 2022
• CR20 new fields being added
• Pricer Version Field (CR12463)
  • added to display the Prospective Payment System (PPS) Pricer Version to Inpatient/SNF, Outpatient, Home Health and Hospice claims at the claim level
• Medicare-Severity Diagnosis Related Group (MS-DRG) Grouper Version field (CR12463)
  • added to display the MS-DRG Grouper Version to Inpatient/SNF claims at the claim level

BIC Updates

• New columns added in mid-April 2022:
• HMO_CONTRACT_NUM field
• HMO_LKIN_PMT_OPTN_CD field

HCD Defined

• • Human-Centered Design is a creative approach to problem-solving that starts with the people you’re designing for and ends with solutions -  products, services, systems and experiences - that are purpose-built to suit their needs. - IDEO (IDEO is a global design consulting company known for its human-centered, interdisciplinary approach.)

HCD Process

1. Discover Phase (User Interviews & Problem Definition)
   1. Empathize (understand the user) and Define (define the problem) 
   2. Goal: Discover User's Needs
   3. Empathize (diverge): Focus on understanding user's needs, seeing things from their perspective (How: user interviews)
   4. Define (converge): Defining the problem based on user feedback (How: synthesize feedback)
2. Design Phase (Identify & Pilot a Solution)
   1. Ideate (diverge): Consider solutions that solve for the user's defined problem (How: Identify possible solutions, systems, or product)
   2. Prototype (converge): Narrow down possible solutions to pilot (How: Pilot the solution)
   3. Goal: Identify a solution to pilot
3. Measure Phase (Usability, UAT & Iterate)
   1. Test (diverge): Conduct testing on the pilot and learn (how: usability testing, user acceptance testing)
   2. Iterate (converge): Make adjustments based on user feedback (how: make changes to the pilot and re-test) 

CCSQ Data & Analytics Team HCD Research

1. CAP / CDR environment Satisfaction Survey:
   • Gain metrics over time to measure user community satisfaction
2. Data Catalog:
   • Learn about Data Consumer’s data catalog workflow, Data Catalog navigation and areas of difficulty, ideas for improvements
   • To reduce difficulty for user community to leverage it and maintain it
3. EMR Pilot:
   • learn about user’s tools, datasets and onboarding experience

CCSQ Data & Analytics Team HCD Research

• Our goals (stabilize and improve the system) + Your feedback (on tools, systems, and process) = Changes Made (directly address your needs)

1. Were the Part A fields added to CSAT or just NCH?
   A - It's been added to NCH and we will need to check with the CSAT team on when it will be available in that data set (internal note: Jayaram mentioned that it won't be until the May refresh for CSAT at the earliest date)

2. Which BIC tables have those fields?

   A - New fields are available in "mapd-contract" table
3. Q Can someone share navigation or url to the bic data catalog (page)
   A - Data Catalog
4. Q The problem for CCSQ seems to be that you have so may user types.  How define and categorize the user groups so that you know where to start?
   A - We are starting with 2 high-level personas Data Contributor and Data Consumer. Data contributors are those that contribute date to the CDR, and Data Consumers are those that access the CDR for analysis.