Batch Interfaces

Batch Interfaces are set to run on a designated schedule, usually overnight. They cannot be manually initiated. These interface calls are initiated by specific criteria or triggers, for example, adding a person to a case, a consumer turning a certain age, or updating or editing data elements in KEES.

There are two types of batch interfaces: outbound and inbound. Outbound means that KEES sends data to the partner system. Inbound means that KEES receives data from the partner system. Batch Interfaces can create records, update records or generate tasks.

Note: Batch Interfaces are called for All Programs.

Batch Name	Inbound/Outbound	Description
Beneficiary & Earnings Data Exchange (BENDEX)	Both	Daily batch data exchange that verifies Retirement, Survivors, and Disability Insurance (RSDI) benefits. The request for information is initiated when the program is approved for benefits. Once a consumer is added to the system they remain on the BENDEX file until their case is closed. This interface indicates changes in SSA amounts. The BENDEX interface can generate tasks related to income records and Medicare Premium information.
Child Support Services	Both	Daily batch that sends child support services referrals or updates to existing referrals on Active programs. Creates or updates Child Support Non-Compliance records or generates a task for the Purple Queue if automation is not successful.
Client Listing	Outbound	Daily batch interface sends a list of KEES consumers to DCF to update EATSS. This list consists of consumers who became active on any program and were not previously known or had coverage discontinued on a program within the last 90 days from the batch run; thus, allowing users to request SSA records via EATSS. Due to the information being sent through several systems, the process could cause a delay in manual TPQY requests for brand new consumers in KEES. DCF and KDHE Staff will continue to use EATSS or SWSS on the mainframe to verify SSN and SSA income as needed.
Death Records	Inbound	Weekly batch from Kansas Department of Health and Environment, Office of Vital Statistics. It provides an electronic file which contains a list of persons that have died in Kansas. This interface creates a task when a match is found. The Date of Death displays on the Individual Demographics page in the Deceased Date field. The interface inserts the date of death with the verification code of Pending. Select a verification code of Verified after confirming the person is actually deceased and take the necessary case action.
Inmate Records	Inbound	Monthly batch from Kansas Department of Corrections. It provides an electronic file which contains a list of persons who have been incarcerated in the State of Kansas. This interface creates a task when a match is found.
State Data Exchange (SDX)	Both	Daily batch data exchange that provides SSI data to states that administer federally funded income and/or health maintenance programs. This batch creates tasks related to Medical Condition records and SSI income records.
State Verification & Exchange System (SVES)	Both	Batch query system that provides states and some federal agencies with a standardized method of SSN verification and Social Security benefit information for program processing. The Daily batch is initiated when a consumer is added to a program since the last daily batch run and has a SSN entered on the Individual Demographics page; a consumer turns 64 years, 9 months since the last daily batch run and is not already entitled to Medicare A or B. The Monthly batch is initiated when a consumer has an open program with a review due in the next month. SVES creates tasks, verifies Social Security Numbers if not already verified, verifies income, creates tasks related to SSA income, Medicare Part A and B premium amounts, and Medical Conditions.
Territory Beneficiary Query (TBQ)	Both	Daily batch data exchange between Centers for Medicare & Medicaid Services (CMS) and states. The TBQ file contains Medicare entitlement information. This interface supplies the information displayed on the Medicare Information page and can update Buy-In information on the Medicare Expense page. The batch interface is initiated when a consumer over 18 years of age is added to KEES since the last batch run; a consumer under 18 years of age with a Medicare Claim number is added to KEES since the last batch run; a consumer is added to a medical program without a TBQ response in the last 60 days; a consumer turned 64 years, 9 months since the last batch run; a consumer has an Active medical condition that is older than 23 months; the third payer start date for Medicare Part A is more than two months in the past; a consumer has a Part A or B entitlement with open medical for over two months; any update is made to the Medicare Expense page.