Date

Attendees

Name
Aaron Thompson
Adrienne Adkins
Adrienne Rayx

Ahmar Wazir


Anitha Chintalapati
Arnie Esparterox
Betina Fletcherx
Branon Barrettx
Cheri Jergerx
Chris Brownx
Curtis Phillips
Deb Wilson
Dianna Christensen
Greg Eccleston
Hari Krishna Pemmasani
Heather Dubendris
Heather Moore
Howard Thomas
Janet Lea Hutchinson
Jason Clem
Jennifer Baileyx
Justyna Sardinx
Karena S
Kathleen Prewittx
Kelly Llewellyn
Kelly Mayo
Lakshmi Eriginenix
Leah Skrienx
Lisa Reesx
Malik Arsalan
Matt McDonoughx
Melissa Fieldhouse
Michael Kennedyx
Nathan Muzosx
Ozlem Taselx
Pandu Muddanax
Rachelle DuBose Caruthersx
Revathy Ramakrishnax
Sarah Fillingx
Seema Sreenivasx
Scott Laughlinx
Shalon Quinn
Steve Goodmanx
Todd Johnson 
Vladimir Ladikx
Yvette Brown
Zach Serlethx




Agenda

ItemsWhoTopics
Meeting RecordingArnie

This session will be recorded for the purpose of documenting the meeting minutes and action items. If there are any objections to the recording of this session, please make it known now. Absence of an objection to the meeting being recorded will count as consent to recording this meeting 

https://zoom.us/rec/share/MpM2L9e3P_fyq5pHHmZk5Zh0lh5Y8--zw632WYJoSWUMfi-vCshu_91pQCP5upqX.b8X-rs2tc1BOJ6jw

Passcode: 6.$^Hpk! 

Gateway Timeout ResolutionScott/Lakshmi/Branon

Note:  The Program team is unable to join today so today's meeting will be repurposed to discuss the API Gateway Issue

Update and Progress

  • Configuration changes were explained and discussed to the group by Branon and  Lakshmi
  • There were a couple of issues identified after reviewing the logs
  • One of the API Gateway layers had an AWS restriction on the AWS API Gateway of 30 seconds
  • We are using multipart upload that should hopefully allow multiple requests to be made during a multipart uploads and succeed on larger files
  • After tracing back down deeper through the stack to the Lambda that takes those files and validates the schema that moves them to S3 and writes a record tot he database table for processing - that lambda was also timing out. So that API Gateway was also timing out at 30 seconds
  • No response was being sent from that Lambda on the multipart upload because just the pre processing step of those files was timing out causing the failure so upstream from that FKC was getting that API Gateway timeout error; downstream from that it was timing out on the Lambda service
  • Quick fix is to provision more resources for that Lambda service - increasing memory and CPU availability for that Lambda
  • Ran about 100 files with the fix in place in prod preview and were successful with no timeout error
  • Continuing to not see any errors at the time of this meeting
  • Branon and team will continue to monitor
  • Request for Revathy to resubmit the files that were failing and let CMS ADO know (Branon and Lakshmi)
  • Nathan request that since today is the day DaVita submits a large submission of their data, Revathy hold off submitting their files until later this afternoon
  • Revathy pointed out that the gateway error files encountered were very few, 4 or 5 patient files
Identify Depressed PatientsScott

The questions, feedback and comments from yesterday's System Demo have been captured and documented

  • Next Steps
    • Share and review with CMS/Program (Lisa) for answers and feedback
    • CMS/Program will get back to this group after they have had a chance to discuss
    • Any Program facing questions today will need to be forwarded to Lisa
  • Question from Nathan regarding Identifying Depresses Patients
    • The new work that is being done, is it being done were it will be part of the current xml or is it becoming its own file?
      • Per Vlad , historically it has been it's own file
      • Will we have two files related to depression or the new questions being integrated into the current depression file 
      • Per Preston it will be its own file
      • Knowing this information will help DaVita in capacity planning
GeneralScott
  • Updated XML files have been posted on the public confluence page for the nursing home identifier feature; there was a mismatch between the XSD and XML
  • Question from Revathy regarding the clinical data not going through.  Received a response from Mitch (Service Center) indicating there is problem with the HTTP header
  • FKS does not see any issues in any of their files
  • Per Scott a call is being set up for tomorrow (12/2 1 pm) with the Ventech Security team
  • This issue came up early November

Next meeting scheduled for  




Action Items:

  • Per Lisa - she will have to get back to Vlad on when the release date for PPSV23 Lisa Rees 
  • Lisa will check with Yvette when she can go through the screens related to depressed patients and explain things, what is required, optional, etc Lisa Rees 
  • Lisa will discuss with CMS what is the expectation in terms of EDIs reporting the admissions, especially for short admissions in support of transplants Lisa Rees  
  • Per Lisa, she does not think there can be a retrospective look back at what has happened since EQRS was released but will take it back to CMS to find out Lisa Rees  
  • Lisa will need to ask the team where they plan to have the 2744 reports reside Lisa Rees  
  • Lisa will need to ask Michael why the acceptance criteria is limited to only the 6 fields listed in the Acceptance Criteria?  Lisa Rees 
  • Per Lisa, she does not think the effective date is included but will ask Michael for clarification Lisa Rees 
  • Per Lisa, she will need to check with Michael on whether a record can be updated through the UI Lisa Rees 
  • The definition for "Telemedicine" will be further clarified when Lisa takes the feedback to the team Lisa Rees 
    • 9/8/21 - Lisa is still looking into getting a definition for the EDIs
  • Leah Skrien asked if aside from Telemedicine if there is anything tied to treatment? Lisa will have the other PO's put together something explaining if anything is tied to treatment and bring to the next meeting Lisa Rees
    • 9/8/21 - Per Lisa, her understanding is yes, that Telemedicine was the only thing tied to treatment
  • Anitha will update the "new?" column field with the date the Kt/V "standard" option was moved into production Anitha Chintalapati
  • Nathan request since the Kt/V "standard" option is already in production, can they have the updated data dictionary, XSD, XML examples, error codes and any associated documentation.  Anitha will send the documentation Anitha Chintalapati
  • EDIs would like to understand how, if or when the Kt/V "standard" option will be used as part of the QIP adequacy measures and same for five-star. When will the standard Kt/V be included in QIP and five-star calculations? Need to get something out to the community/EDIs Ahmar Wazir Jason Clem
    • 9/8/21
      • Per Jason, there is no discussion to bring that it
      • On CMS.gov they post a muck list every December of new measures that might be implemented
      • At this time no plans to update the Kt/V measure
      • Per Howard they have a Kt/V with two methods, both are eligible and used in QIPs
      • If not going to use Kt/V, they need to tell people b/c Kt/V is being reported using standard methodology
      • Per Jason, an announcement was sent out on the standard method to all EQRS users - They are still just looking at the UKM two methods for QIP
      • Howard suggest to review the announcement again
      • Per Lisa, they will take this back to the QMVIG team for clarification and to get a definite answer





DateMilestone (M) / Task (T)DescriptionPhaseStatus
2/28/2021MCode deployed to pre-prod for testing.1Complete
3/15/2021 - 3/24/2021TEDIs perform integration testing.1Complete

3/24/2021

MEDIs sign-off on integration testing.1Complete

3/24/2021 - 3/25/2021

TADO prepares for coding deployment.1Complete

3/25/2021

MProduction deployment.1Complete
3/31/2021MProd-Preview environment contains refreshed prod data 2Complete
2/24/2021 - 3/10/2021 TReview of phase 2 codes and finalize list of codes.  Complete
3/11/2021 - 4/30/2021TADO perform coding updates and regression testing - Phase 2 (Patient Codes) 2Complete

4/30/2021

MProd-Preview environment data refresh.2Complete

5/3/2021

MRemaining Phase 2 (Patient Codes) deployed to pre-prod for testing.2Complete

5/4/2021 - 6/1/2021

T

EDIs performs integration testing - Phase 2 (Patient Codes) 
Starting 5/4 - EDIs submit prod file in prod environment and PP2-3.  This should be the SAME file for both environments.  Review discrepancies between the feedback files and validate codes.

2Complete

6/2/2021

MEDIs sign off-on integration testing - Phase 2 (Patient Codes) 2Complete

6/2/2021 - 6/4/2021

TADO prepares for coding deployment - Phase 2 (Patient Codes) 2Complete

6/3/2021

MProduction deployment - Phase 2 (Patient Codes) 2Complete
6/4/2021MPhase 2 (Patient Codes) live in production.2Complete
3/10/2021 - 3/17/2021TReview of phase 3 codes and finalize list of codes.  3Complete
5/12/2021 - 06/08/2021TADO perform coding updates and regression testing - Phase 3 Clinical Codes/27283Complete

6/4/2021

MProd-Preview environment data refresh.
Complete
6/4/2021 - 6/6/2021T

EDIs SHOULD NOT submit any PATIENT files during this time period in production (to ensure same patients are in PP2-3).

3Complete
6/7/2021T

EDIs to drop file into PP2-3 to establish a baseline.

3Complete

6/8/2021

MCode deployed to pre-prod for testing - Phase 3 (Clinical Codes/2728).
Reopening September 2020 to March 2021 Clinical months for submission.
3Complete

6/9/2021 - 7/6/2021

TEDIs performs integration testing.

Starting 6/9 - Re-drop same file from 6/7/2021 into PP2-3.  Review feedback files from PP2-3 and validate codes.

3Complete

7/6/2021

MEDIs sign-off on integration testing - Phase 3 (Clinical Codes/2728).3

Complete

7/7/2021 - 7/11/2021

TADO prepares for coding deployment - Phase 3 (Clinical Codes/2728).3Complete
7/12/2021MPhase 3 (Clinical Codes/2728) live in production.3Complete

7/12/2021

MEDSM Implementation Complete (Phase 1 - 3).n/aComplete

7/12/2021 - 9/15/2021




T

Resubmission of Clinical Data Files (September to December). 

Open July 12, 2021 at 5 a.m. Pacific (8 a.m. Eastern) and close September 15, 2021 at 11:59 p.m. Pacific Daylight Time

9/15/2021 is the official closure date for the clinical months of September, October, November, and December 2020.

CMS highly recommends completing large data submissions prior to the official clinical closure date.


n/a

Complete


9/15/2021


M

Data fully submitted and ready for measure and scoring calculations.



n/aComplete
09/20/2021 - 02/28/2022T

Submit January-September 2021 EQRS Clinical Data, ICH CAHPS Attestations, and Clinical Depression Screening and Follow-Up Plan reporting in EQRS. Additionally, all subsequent months in 2021 will open for data submission on the first day of each month (i.e., October opens October 1; November opens November 1; and December opens December 1). 

n/a
02/28/2022MThe clinical closure date for all months in 2021 is February 28, 2022 at 11:59 PM PT.n/a

Data Submission (Errors & Warnings) Milestone Dates - By Phase


Phase No.

File Type

Code Bucket Name

Codes

ADO Completion Date

LDO Testing Start Date

Testing Completion Date

Production Date

1

Patient

Admit Reasons

11221, 11222, 11223, 11224, 11225

2/24/2021

3/1/2021

3/24/2021

3/25/2021

2

Patient

Patient Codes


5/3/2021

5/4/2021

6/1/2021

6/7/2021

3

Clinical

Clinical Codes


6/8/2021

6/9/2021

7/6/2021

7/12/2021

3

2728

2728 Codes


6/8/2021

6/9/2021

7/6/2021

7/12/2021

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.