Item | Topics and Notes |
---|
Prod Deployment 1/28/2021 | - Will provide more details around 99999 errors.
- May have additional fixes added to deployment on Thursday 1/28.
- Mike will provide an update in next meeting.
- Updated UI will display error for Primary Cause of Renal Failure.
|
Primary Cause of Renal Failure | - 11/5 - error codes 14030 (expecting numeric value) - should be able to accept alphanumeric values (icd10 codes).
- Mike to take a closer look into this.
- Prior to 10/5, CROWNWeb was able to accept both ICD9 and ICD10 codes. May be related to current issue?
- Clinics are having to remove decimal point in ICD10 code before able to save the form. Is fix related to this?
→ No, but Mike will confirm with internal team. → Issue is in UI. → Suggested to remove decimal code in the batch, but some disagreed with this. I12.9 entered in as I129. Is this the same code? → Mike to escalate this to CMS regarding the batch of UI enhancements that are being reviewed. → Batch of UI enhancement
|
Mapping Corrections for 401 Errors | - Tracey provided a list that required feedback from Networks.
- Some records are too old; not submitting data for those patients anymore. Okay if not respond back for these patients.
- Tracey will resend the list to Networks - duplicate identifiers for multiple mapping.
- Root cause of 401 errors are due to the duplicate identifiers for multiple mapping or there is no mapping that exist.
- Network assumes that when sending in demographic files - mapping is complete if receive a success or warning response. If error response, then mapping will not work. Is there a potential issue if EQRS is sending a warning response but not updating the mapping. Is this the reason why experiencing such a high volume of 401 errors? Michael will also discuss with the team.
|
Multiple Mapping Issue | - Very high volume (hundreds of thousands).
- Networks are not able to clean these up.
- Low priority - does not cause errors or prevent data from being processed or data corruption.
|
Medicare Effective Date | - NRAA reported - date is being overwritten.
- ADO was not able to reproduce, but Mike spoke to the user. Captured information needed to research.
|
Deep Dives | - Next steps: Finish analyzing what was found.
- Meet with CMS on recommendations on how to approach.
- Will want to meet with Networks to ensure the following:
→ confirm issues reported are still active. → issues that need more information - provide status. → identify issues that have most impact and prioritize those. → look at the source of the issue, impact and list of priorities. - Will schedule when ready.
|
Attestation | - Mike will reach out to F5 team to get an update.
- Will provide update early next week.
|
Feedback Files | - Not receiving feedback files.
- Unable to process feedback files once based on the entire batch.
- How should this be reported?
- Open one case and start tracking incidents within the same case in order to be able to review the trends.
|
Extension | - Need confirmation if clinical months close with data hidden, Arbor will be able to use it for QIP measurement and scoring. Or need extension.
- Risk: QIP reductions will have significant impact to Networks and facilities.
|
0 Comments