IN PROGRESS Feedback from the EDIs were given in defining the "definition of done" from a data quality perspective. Definition of Done Description Taskforce MVP 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? 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) An agreed timeline for clinical closure schedule has been released. Especially considering the independent clinics that are only on manual entry.Status Stakeholders EDI Submitters, Program, ISG Outcome Determine 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 Background
Proposal
Error rates are <5% or close to prior to EQRS EDIs each have their own error rates (pre-11/9/2020) and will share 4 months worth of data with CMS. Errors/Warnings are triggering as expected and data for warnings is being shown as submitted and visible in backend and UI Data completion and error/warning reporting is available at the same frequency as prior to EQRS Provide Clinical Compliance (feedback file) 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). Will provide reports for EDIs to resubmit data via EDSM to correct discrepancies or update via UI. Need to avoid backend scripting. Will need to be addressed at a later time.