Dispatch 3192018

Medical Programs

Zero Income Records Not Found Reasonably Compatible

Persons with zero income reported and zero income found (on a successful interface call) are being marked as not reasonably compatible. We are recommending that staff manually mark these people as Verified on the Income Amount Detail so that case processing can continue.

An unsuccessful interface call can be determined by looking at the Real Time Interface History Detail. If KDOL and TALX show Request Failed, this means that the call was not made. If this is the case, the RC result does not meet the requirements for this process.

Also, staff should journal the following when following this process:

“Per instruction received from KDHE, the income record for <Insert Name> will be considered Reasonably Compatible since they reported zero income and zero income was found on successful interface call(s). This will not be reflected on the Reasonable Compatibility Test Detail due to a current system issue, however the income record will manually be set to Verified.”

These cases no longer need to be reported to the KEES Help Desk. Please note that this only applies to the zero income records that are not found reasonably compatible due to the issue described above. Any other RC issues found must be reported.

Buy In Reminder

The Buy In Deletion Report will be available to eligibility staff on the 14th of each month unless notified. The Buy In file will be sent to CMS early on the morning of the 21st. This means the Buy In Deletion Report will need to be completed by 5:00 PM on the 20th. Any cases newly authorized between the 14th and the 20th that qualify for immediate buy in, or cases that need the deletion to be removed from the CMS file, will need to have an email sent to the DXC Buy In team no later than 2:00 PM on the 20th so they can be manually processed.   LOC-KSXIX-BuyIn@groups.ext.hpe.com

Non-Medical Programs

Error Message Received When Running eDRS

Workers are receiving an error when attempting to run eDRS, Error! This web service call to eDRS was not successful. Try Again.  A fix for this issue is planned for this evening.