2021.12.01 EQRS Program Working Group Meeting

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! 

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

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

• 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