- Created by Phuong Dam, last modified on Apr 22, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 3 Next »
Date
Attendees
CMS
Ahmar Wazir
Lisa Rees
Curt Phillips
LDOs
Howard Thomas
Nathan Muzos
Vladimir Ladik
Adrienne Adkins-Provost
Chris Brown
Deb Wilson
Hari Krishna Pemmasani
Heather Moore
Jason Bullock
Jennifer Bailey
Karena S
Kelly Llewellyn
Leah
Teresa Edmunds
Kathleen Prewitt
Others
June Tran
Phuong Dam
Discussion Items
Items | Topics |
---|---|
Clinical Data Submission |
|
Review of Validation Codes |
|
Discharge Reason Codes |
|
Resetting System |
|
Wishlist |
|
Vaccinations |
|
Reporting |
|
EDIs Top 5 Pain Points |
|
System instability (processing timeouts, micro service reliability, security key failures)
| |
High data submission errors (e.g. 10x increase of 401s, receiving errors CMS thinks are turned off).
| |
No access to bulk data/operational reports.
| |
Next meeting on |
Discharge Reason Codes
Code | Description |
---|---|
11231 | Invalid Discharge Reason for a dialysis facility admission. |
11232 | Invalid Discharge Reason for a transplant facility admission. |
11233 | Invalid Discharge Reason: The Discharge Reason selected is invalid based on the next admission record's Admit Reason ({0}). |
11234 | Invalid Discharge Reason: The Discharge Reason selected is invalid based on the admission record's Admit Reason ({0}). |
Action Items:
- Provide a report for EDIs on a count of how many patients are receiving each error code. Lisa Rees
- CMS will need to take a closer look to determine why 11232 is on the validation list of codes since EDI submitters do not submit data electronically for transplant facilities. Lisa Rees
- Need to review the current list of codes to confirm if they are currently generating an error in prod today. Examples: 11222 (Admit), 11233 (Discharge), 11234 (Discharge). Lisa Rees
- Review list of error codes to determine the impact to single interface users since the same edits will apply to both UI and EDIs. @NRAA
- Discuss with ADO on timeline to get ALL error codes (prior to 11/1) turned back on and any validations that they recommend NOT to turn back on.
- Request for LDOs to review the tabs and provide the following information: value on error provides to the system & level of effort - high, medium, low (with testing incorporated). @EDIs
- No labels