Case Types Specifications
01-025-V1.0
August 13, 2001
THE PURPOSE OF THIS DOCUMENT
The purpose of this document is to provide the specifications for the new case types being added to the CSENet 2000 application in support of changes in the Uniform Interstate Family Support Act (UIFSA) forms. This modification is identified in the FPLS Release 01-01 Manifest Minor (OCSE Reference # 114) and is scheduled for implementation on November 19, 2001. The Release Manifest is available at: http://www.acf.hhs.gov/programs/cse/newhire/library/relmgnt/relmgnt.htm.
This document is organized as follows:
Section 1.0: Introduction provides a background on case types.
Section 2.0: Analysis of Case Type Values includes information on existing and additional case types.
Section 3.0: Implementation Approach provides information on software programming for CSENet 2000, changes necessary on State systems, and information concerning States’ pilot testing.
Table of Contents
1.0 INTRODUCTION
The UIFSA forms modified in December 2000 incorporated changes to the IV-D case types. States raised the issue that the case types in the CSENet 2000 application were inconsistent with those contained in the UIFSA forms. The CSENet team solicited input from States regarding their use of this data and performed an analysis of the case types and associated CSENet values. The analysis concluded that software modifications are needed to standardize the case types and assign CSENet 2000 values to the new UIFSA case types.
1.1 Overview
The case types found in the Case Data Block of the CSENet 2000 Data Block Record Layout no longer match those on the revised UIFSA forms. To provide States with the ability to electronically transmit interstate data using current case types, the CSENet 2000 application will add new case types and assign values.
1.2 Scope
The scope of this document is to provide States with the new case types and their values so they can program to send and receive this information. The goal is to allow the existing case type values to pass the validation process while offering States the opportunity to program in advance for the new case type values.
Table of Contents
2.0 EXCHANGE AGREEMENT PROCESSES
2.1 Current CSENet 2000 Case Type Values
The current Case-Type values in the CSENet Data Block Record Layout are shown in Chart 2-1. These are the current values used in the CSENet validation process.
CHART 2-1: CURRENT CSENET 2000 CASE TYPE VALUES
| Case Type Value |
Description |
| A |
TANF |
| N |
Non TANF |
| F |
Foster Care (IV-E Foster Care) |
| R |
TANF Arrears Only |
| C |
Foster Care Arrears Only |
| V |
Non IV-D |
| M |
Medical Care (Medicaid Only) |
Table of Contents
2.2 Current UIFSA Case Types
The current UIFSA case types specified at http://www.acf.hhs.gov/programs/cse/forms/ are listed below.
- TANF,
- Medicaid Only,
- IV-E Foster Care,
- Former Assistance,
- Never Assistance, and
- Non IV-D.
2.3 New Case Type Values
The case types and their values as identified in Chart 2-2 will be used by CSENet 2000 for the validation of States’ transactions. The case types are a combination of the current CSENet 2000 case types and their values and the current UIFSA case types. New case type values, S and T, have been added. These are bold and underlined in the chart for ease of identification.
CHART 2-2: CSENET 2000 CASE TYPE VALUES
| Case Type Value |
Description |
| A |
TANF |
| C |
Foster Care Arrears Only |
| F |
Foster Care (IV-E Foster Care) |
| M |
Medical Care (Medicaid Only) |
| N |
Non TANF |
| R |
TANF Arrears Only |
| S |
Former Assistance |
| T |
Never Assistance |
| V |
Non IV-D |
To minimize programming impact on the States, Foster Care Arrears Only (C), Non TANF (N), and TANF Arrears Only (R) values will not be deleted at the present time.
Table of Contents
3.0 IMPLEMENTATION APPROACH
3.1 CSENet 2000 Application Software Modifications
The CSENet 2000 application software will be modified to accept and validate all transactions based on the new case type values. The software will be released into the Production environment on November 19, 2001. To pass the server edits, the Case-Type value must equal A, C, F, M, N, R, S, T, or V. Otherwise, the transaction will be rejected by the CSENet server with the Error Code E620, “Invalid Case Type,” and returned to the sending State.
3.2 States’ CSE System Programming Modifications
On November 19, 2001, all States must be able to receive the new case type values of S and T. States will need to add these values to their systems for transaction generation.
3.3 States’ Pilot Testing
Before release of the new software, it is expected that some States will desire to verify their system programming. States may do this by participating in pilot testing. Pilot testing provides States an opportunity to exchange transactions via test data sets with:
- the CSENet FIPS code 9100000 (Test Deck),
- other States participating in pilot testing, or
- their own system through loopback testing.
CSENet technical representatives will be available to provide analysis and feedback concerning test transactions. Pilot testing will available the week of October 29, 2001. Please contact your technical representative if you wish to participate.
