2021.02.01 - Errors & Warnings: Phase 1 Discussion (Ad-Hoc Meeting)

• 5 errors will be turned on (see list).
• Environment that was previously used for testing is still available and will be utilized.
• Data will not be refreshed - if can not use the data from the environment, then LDOs will need to generate own data to test.  Should not expect to be able to submit current prod files as test files.  
• LDOs are in agreement to turning these back on.  No coding effort required on their side.
• Resulting in duplicate "new to ESRD" patients within the system.
• Turning the errors on will stop the duplicates "new to ESRD" issue.
• ADO will perform additional research to see if there are any other causes to this issue.  
• NRAA requested that ADO provide a list of patients created after 11/9/2020 and caused a duplicate "new to ESRD" warning message.
• Opportunity to make error messages more distinct.  What is the previous admission reason vs next admission reason.  Facility data impacts each other downstream.  If error provides the data, then would have more information in correcting the data.  Ahmar has documentation for admission reason logic (i.e. what is valid)- should be able to help in testing.  LDOs already have this document, but would like it resent.
• LDOs would like a structured test in pre-prod and run scenarios against the documentation to confirm this.  Curt reminded that there is not current production data so will need to create patients and perform testing to verify this.
• NRAA wants the focus of testing to be what admit reasons work together and don't work together (sequence).

• Originally set up as an error, but later removed.  No warning message is generated.  (Yvette confirmed this later one via Slack message).  
• There were similar issues between 2019 and 2020.  May have been invalid data due to user error (i.e. admission reason was different than existing admission in system).
• has this documentation, but would like confirmation that this is the logic the system is following (i.e. documentation matches what the system is doing and vice versa).  
• LDOs mentioned that if not able to get prod data in pre-prod, they can perform their testing in prod instead.

• Curt asked if LDOs will be able to correct admit reasons.  NRAA did not understand that was an expectation.
• New ESRD admissions will be extremely hard for facilities to correct because of how error codes will interact with each other.  
• Who, how and how long to correct - LDOs would like a separate targeted discussion that is accompanied report of patience who have a wrong admission reasons since they have not been triggering warnings and they do not know who these are.
• Knowing who is right and who is wrong on two different admission reasons will be difficult to ascertain.  Historical correction will be difficult.  
• If the behavior is the same in EQRS as it was in CROWNWeb, the LDOs will not have and issue with the correction process.  
• Any errors triggered on feedback file, LDOs have processes in place to research the specific record in question.

• LDOs requested Error Trends report.  Critical to see overall how the system is performing and what kind of errors are being triggered.  
• Howard will provide a sample report to Lisa.
• LDOs would like to put metrics on the report - are we generating the errors at the same rate?
• Also contained tips on resolution for errors.  
• Clinical Comply and other reports are highly operationally necessary.
• Lisa confirmed that NCC is 60% complete with Clinical Comply Report.
• Clinical Comply Report - NCC will do some testing to ensure that this is what LDOs is expecting.
• Lisa - NCC is trying to support many initiatives right now. So it will be difficult to work on two reports at the same time for the LDOs.  
• Will work to give LDOs what they need, but will take time to be able to deliver. 
• LDOs wanted to discuss "time".  Clinical Comply is necessary and Error Trends is necessary at this time.
• Lisa will set up a call with NCC to prioritize list.  Howard would like Kathleen, Nathan and Vlad part of this discussion.  
• LDOs clarified that Error Trends is #4 is a list of 12.  January 19 meeting - NCC did not have access to the data, so Clinical Comply was prioritized over Error Trends.  NCC now has access (Lisa to confirm). 
• Priority list:  (1) Clinical Comply Report, (2) UNOs, (3) Flu, (4) Error Trends.

11221

Invalid Admit Reason: An exact match patient was found and the Admit Reason selected is invalid based on the next admission record's Admit Reason  ({0}).

11222

Invalid Admit Reason: An exact match patient was found and the Admit Reason selected is invalid based on the previous admission record's Admit Reason  ({0}).

11223

Invalid Admit Reason for a dialysis facility admission.

11224

Invalid Admit Reason for a transplant facility admission.

11225

Invalid Admit Reason: An exact match patient was found and the Admit Reason selected is invalid based on the previous admission record's Discharge Reason  ({0}).