QualityNet Jira and QualityNet Confluence will be briefly unavailable on Wednesday, July 24, 2024, between 8:00 PM ET and 9:00 PM ET while the team performs an AMI update.  If you have questions or concerns, please reach out to us in Slack at #help-atlassian.

EQRS Communications Hub

Versions Compared

Old Version 13

changes.mady.by.user Karen Wheeler

Saved on

compared with

New Version 14

changes.mady.by.user Karen Wheeler

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt


Page properties


Status

Status
colourYellow
titleIn Progress

StakeholdersEDI Submitters, Program, ISG
OutcomeDetermine what is an acceptable level to move forward of EQRS clinical closures from a data quality perspective and define the MVP that the EDI Submitter Outreach Taskforce will deliver in order to be considered "done".
Due date

 

Owner

Adrienne Ray



Background

Feedback from the EDIs were given in defining the "definition of done" from a data quality perspective.

Target to finish this on and share with EDIs  

Proposal

Definition of Done

Description

Taskforce MVP

Error rates are <5% or close to prior to EQRSEDIs each have their own error rates (pre-11/9/2020) and will share 4 months worth of data with CMS.
  • Average percentage across 4 months prior to 11/9/2020 per EDI.
  • Will continue to work with each EDI if the error rate is not <5% (post implementation of reinstatement of validation rules).
  • Within 5% range (up or down) of error trends data prior to EQRS Go-Live for each code within each phase of implementation - for the top 10 error codes.
  • Michael Kennedy  - January 2020 back to October 2019 - broken down by each phase for each code in the top 10 codes. - Done
  • 5/3/2021 - Will not be part of definition of done. Error Trends report prioritized for future PI so not ready to share yet. Do plan to provide in future PI. 
Errors/Warnings are triggering as expected and data for warnings is being shown as submitted and visible in backend and UI

For errors that currently do not meet validation rules, the data does not show up in the UI.  If the code remains a warning as determined thru the Errors & Warnings Implementation, we will need to allow the data to be seen thru the UI.  Is this possible?  What is the level of effort around getting this accomplished?  

For each phase - for errors that are reverted to warnings, the developers need to take a deeper dive into the code to assess the LOE to have the warning visible via the UI.  Need to have this work built in to each phase to correct this issue.

  • 5/3/2021 -
    • Confirmed with ADO could not split backend from UI.
    • Need warning visible via the UI.
    • Future Scope: Work related to matching behavior where appropriate.
    • For errors can we have can make the statement in Column #1 and matching behavior for PI 14? Scott Laughlin will go back to team during 5/3 standup and confirm what is being done for PI 14.




Data completion and error/warning reporting is available at the same frequency as prior to EQRS

Provide Error Trends report similar to what CDDS provided in the past.  (PI14)?

System generated report available to the user (long term).

What reports should be included in this DOD?  Specify this in our DOD.

This will be done in PI 15.

  • 5/3/2021 - Will not be part of definition of done. Error Trends report prioritized for future PI so not ready to share yet. Do plan to provide in future PI. 

  

Major Bug List has been completed and successfully tested or any backlogged bugs are not impactful to QIP/Five Star results (this assumes a Major Bug List exists and becomes part of routine status updates)

CMS prioritized list of EDSM work within PI 14 is shared with EDIs and completed.


  • EDI Issues Dashboard will be shared and tracked towards our DOD.\
  • Share roadmap.
  • Share objectives (committed only).  Program themes?
  • 5/3/2021 - Program Level themes are correct level to share. 

CMS has analyzed Admit/Discharges/Treatment and Clinical (from Aug. - Current month) EQRS data to assess data discrepancies that were introduced to EQRS.  EDIs have been given guidance and support to resolve the data discrepancies identified.  (Clean up effort).


Established and executed the data cleanup timeline.
Analyzed the data discrepancies.

Will provide reports for EDIs to resubmit data via EDSM to correct discrepancies or update via UI.  Need to avoid backend scripting.
  • What type of reports will be provided?
  • What is the current state of data discrepancies in the system today.  ETL report to identify the volume of data discrepancies?  How will this be cleaned up - resubmitting files?
  • 2744 will provide visibility into this.  
  • Clean up effort will be planned for future work (not committed).  Many different avenues for data clean up

Michael will share a timeline of the clean up effort.

  • 5/3/2021 - Timeline is planned and actively being worked. Good with this as is. 

An agreed timeline for clinical closure schedule has been released.  Especially considering the independent clinics that are only on manual entry.


Will need to be addressed at a later time.  
Revisit 
  • 5/3/2021 -
    • Ok on this for 2020 - at EDI meeting on Wednesday will reshare what is in the EDI schedule table already:
      • Resubmission month is 7/12-8/22 (Resubmission of Clinical data)
      • 8/23-8/30 (Data Cleanup)
      • 2021 we do not know yet
    • After we are done with Phase 3 plan to open up Sep/Oct/Nov/Dec (four months of 2020), then pause. Jan / Feb 2021 were also requested to be open by EDIs. ADO wanted to focus on just the final four months of 2020. Phuong Dam will ask about the technical concerns restricting this to those four months at EDSM strategy meeting on . 
    • Goal is to get 2020 closed out.
    • Dates entered impact both EDI and smaller organizations therefore will do phased in approach - last four months of 2020, pause, then first two of 2021.
    • No clinical closure date provided by the program yet for 2021 for production. After date is provided by program can enter that date into the system. 
    • Should we reach out to Delia and see if eOCT can talk to some smaller users and get some feedback (ultimately QIPs decision about clinical closure dates)? There is a Wednesday already scheduled with Delia where Justyna Sardinmay be able to confirm if ok to reach out to them. (Will help with understanding if the 7/12-8/22 timeframe is enough for the smaller users). - Now Phuong Dam reaching out to Cheri per 11:30 meeting.