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.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

Attendees


Name

Ahmar Wazir


Lisa Reesx
Curt Phillipsx
Betina Fletcher
Adrienne Ray
Kelly Llewellynx
Heather Moore

x

Kathleen Prewittx
Chris Brownx
Vladimir Ladik
Nathan Muzosx
Leah Skienx
Jason Bullock
Hari Krishnax
Karen Wheelerx
Cheri Jergerx
Jennifer Baileyx
Aaron Thompsonx
Karena S
Pandu Muddax
Revathy Ramakrishnax
Justyna Sardin
Scott Laughlin
Adrienne Adkinsx
Michael Kennedyx
Patrick McConnell
Yvette Brownx
Justyna Sardin
Andy Tarpley
Lonnie Hanekamp
Tom Lantzx
Greg Eccleston
Branon Barrett
Lakshimi Erigineni
Shamim Almamun
Andrew Yochum
Deb Wilsonx
sfillingx
Howard Thomasx






Agenda

ItemsWhoTopics
Phase 3 Clinical Codes Lisa
  • Moving forward with warnings and errors from community feedback.  https://qnetconfluence.cms.gov/x/cbVhC
    →  Current ranges will be kept as is today for warnings.

  • Enabler for future:  Variances on measures/thresholds.  Anything outside of variances will be an error.
    →  EDI collective feedback for variances based on lab providers input.
    →  Warning if results are within lab values.
    →  Error if outside the lab values.

  • Will EQRS show the out of range values that are submitted and trigger warnings? 
    Example:  Normal range is 10-20.  If EDI submits 20.2, it should be visible within the UI since it is only a warning.

    →  Will not be visible within Phase 3, but will be slotted for future work.
    →  Communication to be sent to facilities to make them aware that values will be accepted outside of normal ranges, but may not be visible within the UI.  
    →  Will the data will be available for QIP and 5 Star Rating?  CMS to confirm.  
    →  Clinical Months closing and data is not visible - what will happen if clinics manually enter the data?  This needs to be taken into consideration as possible issue/concerns.
    →  Discrepancies between backend data reporting and whether or not the data is available or not (i.e. NCC reporting).  EDI requesting a detailed report for all patient data that are somehow not being view in EQRS.  Can this be added as an additional column on NCC report?  Lisa will take back to NCC.
  • Error 13647 - Patient has UF records with the same session date triggers when the EDI is submitting the same UF data and date for the patient.  Final decision - Error or Warning?  Need additional information on what is being rejected before final decision.
    →  Warning is triggered when a duplicate session record is sent. 
    →  Does not create a true duplicate; no insert on table that creates another session that is identical to the existing one.
    →  EDIs believe that the data should simply update since all data points are the same and no warning or error should be triggered.
Open Floor

Duplicate Data Being Sent



2744 - Death and Discontinue Issue

  • EDIs send records until they are accepted.  Does not resend record again until there is a change on the record. 
  • Clinicals are sent every month since they change every month.
  • Disconnect occurs when clinics can manually enter data at anytime via UI.  But EDI is not aware and may batch in a duplicated record that is identical.  Instead of rejecting the record for sending same data as what is in the system, an overwrite should occur rather than triggering an error or warning.

  • Workaround - Change the discontinue of death, fix 2744, submit it, then put discontinue back in.
  • Lisa is okay with this workaround.  
  • NRAA requesting a memo from CMS to authorize workaround before this is implemented.  They are concerned that this is falsification of data.  Lisa stated that she is not going to issue a memo for this.  If EDI is uncomfortable with doing this, then they should not perform the workaround.
  • Some NW are accepting 2744 with errors on them - this was NOT a directive from CMS.
  • Patients who die within the 30 days of the discontinue are supposed to be counted as a death on the 2744.  This ensures death count is accurate and once submitted the event is goes back as a discontinue within the system.  Lisa's concern was not changing it back to a discontinue afterwards.


Next meeting on  

Phase 2 Testing Schedule

WhoPoint of ContactTesting Date
FC TeamTom Lantz

 

Pre-Prod Environment refreshed with prod data.
HEISTSaritha

 

Perform regression testing to ensure system is ready for EDI testing to start.



 -  

Round 1 of testing.
NRAAKelly

 

Drop test file #1.
DavitaHari

 

Drop test file #1.
DCIVlad

 

Drop test file #1.
FMCPandu

 

Drop test file #1.


  • For data that is submitted that triggers a warning, but not visible via the UI (i.e. Phase 3 codes) - will the data will be available for QIP and 5 Star Rating?  CMS to confirm.
  • EDI requesting a detailed report for all patient data that are somehow not being view in EQRS.  Can this be added as an additional column on NCC report?  Lisa Rees 
  • Error 13647 - Patient has UF records with the same session date triggers when the EDI is submitting the same UF data and date for the patient.  Need confirmation from ADO on whether only the specific session errors out or all data errors out.  Yvette Brown 
  • Error 13647 - Michael Kennedy  to review older error trends report to determine if this was a top 10 error.  What was the frequency of this error?


Recording

  • No labels