2021.03.10 EQRS Working Group - Meeting

• Feedback file issue - is it still continuing?  Has anyone recently submitted a test file and received feedback file successfully?
  • NRAA was able to submit a test file early last week and sent test results to the Helpdesk email.
  • NRAA receive feedback files differently than other EDIs which are posted to an API and as the system are creating them.  Receive a feedback file for each XML file that is submitted.  

EDI Homework Responses

• Definition of Done for Data Quality - Still in review.
• Test Environment Refresh Strategy
  • EDIs only have access to 5-6 clinics in order to be able to test with.  EDIs would like access to ALL clinics and ALL data to be able to fully test.
  • This is the same behavior that has always been available for testing, but EDIs feel that this a small sample is not enough to test properly.
  • CMS needs to discuss further internally; may not be feasible.  

• Each EDI to provide a status on where they are with testing.

• Ahmar spoke to the feedback provided by EDIs for Phase 3.  
• Additional column added to indicate if the data is used in QIP calculation for EDIs to understand that if they are kept as warnings than it may impact scores.  
• Keeping them as errors could ensure the data is accurate (in cases of data entry mistake).  May be in EDI's benefit to keep as errors. 
• Curt reminded the group that warnings should be reviewed.
  • Kathleen mentioned that for a user who is managing data in the UI, the system does not alert the user that the value does not meet the parameters set (warning message is not triggered).  CROWNWeb used to have functionality where the user had to check a box "to ignore this warning" before submitting.   Users are not able to validate that the submitted data was successfully loaded to the system since the data is not displayed in the UI after it has been entered.  
  • Curt clarified that UI will not display data that does not meet the established parameters set (business value) even if the data was successfully loaded into the system due to changing validation check from error to warning after 11/9 go-live.
  • Future state after validation code implementation is to have true warnings to be displayed in the UI.  Specifically, errors changed to warning, then as part of implementation project, CMS decides to keep as a warning, the system will accept the data AND display the data in the UI.
  • Ahmar's spoke about desire for future system behavior - Goal is to have system should display clinical data even if it does not meet the prescribed range.  Internal discussions for CMS.