2021.05.28 EQRS EDI Submission Testing - Meeting

Phase 2 Testing Timeline

• 5/4 to 6/1 - EDIs perform Phase 2 (Patient Codes) testing in progress.
• 6/2 - EDI Sign off on testing.
  • Based on results of the testing to date we are anticipating all groups signing off on 6/2.
• 6/7 - Production deployment.
• Timeline

• Davita 
  • No new issues.  
• DCI 
  • No new issues
• FKC 
  • No new issues.
  • Request: Need a list of all errors and warnings classified by warnings and errors. All IDs should have a flag detailing the issue and definition.
    • Scott: Take back and will get back to the group.  
• NRAA
  • Testing engineer is working on analysis. Expect after holiday.  Will target to run regression on the 2nd or the 3rd of June. 
  • Reiterated the need for updated Error Code list.
    • Scott: asked if this happened historically. 
    • Yvette: Yes, it was provided during Crown Web days.  The issue with EQRS is that all the codes are in the database but it doesn't tell you whether its a warning or error.  That information is in the code so it's a manual process. Now for the phase 2 codes she has been making the updates as final decisions are made.  Will continue to do that for clinical and 2728.  A process needs to be implemented that would have that information in the database available to pull. 
    • Scott: We got the code number and description so we are lacking what's an error and a warning at this point, correct Yvette?
    • Yvette: Yes
    • Scott: Bottom-line, we hear you and have a take away.  This aligns with updating messages feedback we've received.  May be able to tie it all in.
    • Kathleen: Echoed the need for the Error Warning List. Brought up the point of not seeing old errors(CROWN web) 11294, namely, in the new runs. 
    • Michael: You should not see 100, 400 or 401 because he's been fixing.  With facility and patient mapping, you shouldn't see any high numbers.
    • Kathleen: Thanked Michael. But for the 5 digit one, so Yvette I heard you the phases are only for those we made changes but if this one didn't take, why is it triggered?
    • Yvette: Yes, will send out the full list of codes again after call, and it is on the full list it says "the patient has a submitted form 2728, admit reason can not be changed from 'new' to 'ESRD.'" Just from reading the description, I can see why you haven't really received this often because it is not a common scenario. But it is on the list.
    • Kathleen: I can go back and validate. This used to be one of our biggest errors in the CROWN web days.
    • Scott: We need more data to investigate the results. Reiterated that what was available in Crown is no longer available. PM3 will Link errors list in confluence. 
    • Revathy: Requested a change log be instituted for error codes to maintain history log.
    • Scott: mention concerned with timeline.  The requested signoff date for phase 2 is on 2nd, and expressed little concerned it doesn't match with your testing strategy and how we would work through it.
    • Kelly: Mentioned resource constraint and its the soonest the test engineer could look at the messages.
    • Scott: Ok

If interested in 1:1 calls please reach out to Scott and Yvette.

• In Progress. Tracking toward 6/21.
  • Nathan: Data Clean up. What is the status of the Bulk identifications of records?
  • Michael: Yes, completed all of the Ghost Patients that had been migrated, Secondary merge IDs impacting individual tickets, 2744 code deployment that was blocking and showing duplicates.  Still working on others. 2744s blockages are priority. Then critical cleanups after that.

Scott: Confirm a signoff prior to making a scheduling change. Can deploy as early as 6/3 if signoff is completed if not 6/7.

Nathan: Schedule has a refresh as well. Scott: that would remain unchanged. Nathan: outside of the refresh between now and July should we expect any changes in Prod Preview? Scott: refer to timeline.