Interstate Communications and Case Processing
Federal Office of Child Support Enforcement
July 2004
The Interstate Communications and Case Processing training is an overview of the CSENet 2000 Application. It is designed to provide users with information on using CSENet and describes the electronic components needed to conduct interstate child support business.
The presentation consists of the following slides:
- Slide 1:
- Interstate Communications and Case Processing
- Slide 2:
- The OCSE Network
- Slide 3:
- Goal
- Slide 4:
- CSENet 2000
- Slide 5:
- Interstate Communications
- Slide 6:
- Business Activity CSENet Function Relationship
- Slide 7:
- UIFSA and CSENet Transactions
- Slide 8 - 9:
- Interstate Case Activities - Governed by UIFSA & CFR
- Slide 10:
- Interstate Business Electronic Components
- Slide 11:
- Action and Reason Codes
- Slide 12:
- Function, Action, Reason Codes
- Slide 13:
- Building a Transaction
- Slide 14:
- Transaction Components
- Slide 15:
- Component 1: Header
- Slide 16:
- Component 2: Data Blocks
- Slide 17 - 18:
- Data Block Descriptions
- Slide 19:
- Headers and Data Blocks
- Slide 20:
- Sample Transaction Structures
- Slide 21:
- Required Data Blocks
- Slide 22:
- Component 3: Data Elements
- Slide 23:
- Transaction Characteristics
- Slide 24:
- A Sample Case-Closure Transaction
- Slide 25:
- A Sample Transaction Notifying a State That a Non-TANF Case Is Closed
- Slide 26:
- Transaction Functional and Business Usage
- Slide 27:
- Quick Locate (LO1)
- Slide 28:
- Steps for Building an LO1 Request
- Slide 29:
- Steps for Building an LO1 Response
- Slide 30:
- Case Status Information (CSI)
- Slide 31:
- Steps for Building a CSI Request
- Slide 32:
- Steps for Building a CSI Response
- Slide 33:
- Enforcement (ENF)
- Slide 34:
- Steps for Building an ENF Request
- Slide 35:
- Steps for Building an ENF Response
- Slide 36:
- Managing State Cases (MSC)
- Slide 37:
- Steps for Building an MSC Request
- Slide 38:
- Steps for Building an MSC Response
- Slide 39:
- Paternity (PAT)
- Slide 40:
- Steps for Building a PAT Request
- Slide 41:
- Building a PAT Response
- Slide 42:
- Establishment (EST)
- Slide 43:
- Steps for Building an EST Request
- Slide 44:
- Steps for Building an EST Response
- Slide 45:
- Collections (COL)
- Slide 46:
- Steps for Building the COL Transaction
- Slide 47:
- Development Resources
Slide 1: Interstate Communications and Case Processing
Top of Page
Slide 2: The OCSE Network
The OCSE Network Links 54 Diverse Child Support Enforcement Agencies Together for the Effective Processing of Interstate Cases
A total of 54 jurisdictions:
- 50 states
- District of Columbia
- 3 territories
- Guam
- Puerto Rico
- Virgin Islands
Top of Page
Slide 3: Goal
Expedite interstate case processing and the collection of child support payments by electronically exchanging UIFSA information via the OCSE Network
CSENet 2000 Automates UIFSA Forms
Top of Page
Slide 4: CSENet 2000
- CSENet 2000 simplifies interstate communications
- States/territories send their CSENet files (transactions) electronically to the OCSE server directly from their Child Support Enforcement system
- States/territories receive transactions, including error files, directly from the OCSE 2000 server
Top of Page
Slide 5: Interstate Communications
CSENet 2000 Server Performs All Validation and Routing of Transactions
Communication via the OCSE Network
Top of Page
Slide 6: Business Activity CSENet Function Relationship
| Business Activity |
CSENet 2000 Function |
| Locating noncustodial parents (NCPs) |
LO1 - Quick Locate |
| Gathering information (FCR) |
CSI - Case Status Information |
| Enforcing support order |
ENF - Enforcement |
| Ongoing case activity, administrative services |
MSC - Managing State Cases |
| Establishing paternity |
PAT - Paternity Establishment |
| Establishing support order |
EST - Order Establishment |
| Income tax offset notification |
COL - Collection |
Top of Page
Slide 7: UIFSA and CSENet Transactions
- The next two slides provide examples of the various interstate business activities
- CSENet functions that support these activities are identified
Top of Page
Slide 8 - 9: Interstate Case Activities - Governed by UIFSA & CFR
Top of Page
Slide 10: Interstate Business Electronic Components
Defines the Electronic Business
Top of Page
Slide 11: Action and Reason Codes
- Action code describes the action of the transaction
- R – Request (an initiating transaction)
- A – Acknowledgment of receipt of a Request
- P – Provision of information/Response
- M – Reminder (used when a Response is overdue)
- U – Update of a previously transmitted Request
- C – Cancel a previous Request
- Reason code clarifies the activity
- Activities such as "paternity hearing scheduled" or "additional information needed to proceed" have unique Reason codes
- Not contained in all transactions, e.g., PAT R (Blank) is a Paternity Request
Top of Page
Slide 12: Function, Action, Reason Codes
- Examples of Function, Action, Reason codes
- CSI R FRINF
- Request all available IV-D case information due to notification from the FCR of participant existing in another IV-D case in another state
- PAT A AADIN
- Acknowledgment – additional information needed to proceed
- PAT P PICHS
- Response – Paternity hearing scheduled
- 185* valid transactions
*MSC P REJCT added as part of OCSE Release 04-01 Minor, August 20, 2004
Top of Page
Slide 13: Building a Transaction
Top of Page
Slide 14: Transaction Components
- Header
- Data Blocks
- Data Elements
Top of Page
Slide 15: Component 1 - Header
- A Header begins every transaction
- Provides identifying information on the case, source, destination, and content of the transaction
- Contains "Indicators," used to show which data blocks (if any) and the number of data blocks the transaction contains
- Includes a combination of codes that specify the Function, Action, and Reason of the business activity communicated
Top of Page
Slide 16: Component 2 - Data Blocks
The Header may be followed by one or more data blocks:
- Header
- Case Data Block
- NCP ID Data Block
- NCP Locate Data Block
- Participant Data Block
- Order Data Block
- Collection Data Block
- Information Data Block
Top of Page
Slide 17 - 18: Data Block Descriptions
- Case Data Block
- General case information, status, contact, and payment address
- NCP ID Data Block
- Physical description of NCP or putative father
- NCP Locate Data Block
- Location and employer information regarding the NCP or putative father
- Participant Data Block
- Information about other people involved in the case. Relationship field indicates the relationship of each person in the case, e.g., custodial party, dependent.
- Order Data Block
- Support or paternity order information
- Collection Data Block
- Information about a tax offset
- Information Data Block
Top of Page
Slide 19: Headers and Data Blocks
- A Header is required for all transactions
- Some transactions (CSI and MSC Requests and Updates) require only a Header, although other data blocks may be added
- All other transactions require one or more data blocks
- Some transactions require specific data blocks under certain conditions
- For example, an LO1 Response requires the NCP Locate data block, if the state has been successful in finding NCP or employer information
- Data blocks must be added to a transaction in a specified order
- Case, NCP ID, NCP Locate, Participant, Order, Collection, Information
Top of Page
Slide 20: Sample Transaction Structures
Top of Page
Slide 21: Required Data Blocks
Top of Page
Slide 22: Component 3 - Data Elements
- Each data block contains data elements, for example the local FIPS state code
- Use of a data block requires that certain data elements and/or specific values be present
- Rules govern the use of data elements
Top of Page
Slide 23: Transaction Characteristics
- Each transaction is a string of data terminated with a new-line character that signifies the end of the transaction
- Formatting rules apply to all data, for example, dates must be formatted as CCYYMMDD
- Transactions can be of variable length (maximum 8481)
- Refer to the CSENet Data Block Record Layout for additional information about data block characteristics and data elements
Top of Page
Slide 24: A Sample Case-Closure Transaction
- The next slide contains a simplified sample transaction that contains only the required data block (Case) and data elements for the transaction
- CSENet Data Block Layout contains additional data elements for the Case data block that states may use
- Transaction Functional Matrix (TFM) recommends additional data blocks as essential to conducting business and automating transaction processing
- Below the transaction is a detailed description of the
- data elements in the Header
- the two required data elements from the Case data block
Top of Page
Slide 25: A Sample Transaction Notifying a State That a Non-TANF Case Is Closed
Top of Page
Slide 26: Transaction Functional and Business Usage
Steps for Building Requests and Responses
Top of Page
Slide 27: Quick Locate (LO1)
- The Quick Locate process is a highly successful way of locating noncustodial parents (NCPs) in an efficient manner
- Often the initiating state believes the NCP may be in one of several states and may send an LO1 Request to each
Top of Page
Slide 28: Steps for Building an LO1 Request
- The LO1 Request is typically used to obtain an address or employer when a state/territory has reason to believe that the NCP works or resides in another jurisdiction
Top of Page
Slide 29: Steps for Building an LO1 Response
- Upon receiving a Quick Locate request, the responding state/territory should use its resources to attempt to locate the NCP
- The responding state
- need not initiate a case of its own
- should report any findings to the initiating state, whether successful or unsuccessful
Top of Page
Slide 30: Case Status Information (CSI)
- Provides states/territories an automated method to obtain comprehensive case and order information from another state
- Supplements the information from the Federal Case Registry (FCR)
Top of Page
Slide 31: Steps for Building a CSI Request
- A state receives an FCR Query/Proactive Match Response Record indicating that the NCP and/or CP are involved in a case in another state
- The state evaluates the case to determine if a CSI Request for additional information is warranted
- For example, there is no order or the NCP has stopped paying on an existing order
Top of Page
Slide 32: Steps for Building a CSI Response
- Upon receiving a CSI request, the responding state should automatically build a CSI Response
- States and territories are encouraged to send all available information in the CSI Response
- Once a Response is received, the initiating state can then determine the next case-processing action
Top of Page
Slide 33: Enforcement (ENF)
- The enforcement process is used by states to request and receive assistance with the enforcement of a support order
- Reasons for initiating an Enforcement Request are numerous, for example:
- Modify a support order
- Request collection of an existing order or of arrears
- Request administrative review of a tax offset
Top of Page
Slide 34: Steps for Building an ENF Request
- Once interstate enforcement action is determined to be necessary, the state generates and sends an ENF Request to the state with jurisdiction for enforcement
Top of Page
Slide 35: Steps for Building an ENF Response
- After processing the case, the responding state builds an ENF Response to provide status information or outcome
- Once a Response is received, the initiating state can then determine the next case-processing action
Top of Page
Slide 36: Managing State Cases (MSC)
- The MSC transaction is used to communicate a variety of ongoing business activities in interstate cases and administrative services under UIFSA
- For example, case status updates:
- Case-type change
- NCP left the state
- Field-office change
- Hearing date notification
- Case closure
Top of Page
Slide 37: Steps for Building an MSC Request
- An MSC Request can either be automatically generated by the CSE system or manually initiated by the caseworker
Top of Page
Slide 38: Steps for Building an MSC Response
- Typically, an MSC Response is used to return information specified in a Request from another state
- However, it can also be used to provide information or relay an activity that has occurred in an ongoing case
- Once a Response is received, the initiating state can then determine the next case-processing action
Top of Page
Slide 39: Paternity (PAT)
- The Paternity function is used when long-arm processing is inappropriate or has been unsuccessful
Top of Page
Slide 40: Steps for Building a PAT Request
- Once it has been determined that a PAT Request is necessary, the state builds a Request to send to the state that has jurisdiction for paternity establishment
Top of Page
Slide 41: Building a PAT Response
- The responding state:
- Builds a new case or updates an existing case
- Process the case and use PAT Responses to communicate status and outcome
- Once a Response is received, the initiating state can then determine the next case-processing action
Top of Page
Slide 42: Establishment (EST)
- The Establishment function supports the establishment of support orders in interstate cases
Top of Page
Slide 43: Steps for Building an EST Request
- After identifying a case for which another state needs to establish support, the initiating state builds an EST Request
Top of Page
Slide 44: Steps for Building an EST Response
- The responding state:
- Builds a new case or updates an existing case
- Processes the case and uses EST transactions to provide status and outcome to the initiating state
- Once a Response is received, the initiating state can then determine the next case-processing action
Top of Page
Slide 45: Collections (COL)
- The Collection function is used to notify another state that a tax offset has been received and disbursed
- There is a single valid COL transaction, COL P CITAX
Top of Page
Slide 46: Steps for Building the COL Transaction
- COL P CITAX identifies monies received from a Federal or state tax offset or adjustments of the original offset
Top of Page
Slide 47: Development Resources
- CSENet 2000 Interface Guidance Document (IGD)
- Valid Transactions Table
- Data Block Record Layout
- Transaction Functional Matrix (TFM)
- End User Support and Technical (Software and Network) Groups
- OCSE Website contains the following:
- States' CSENet information, including state contacts
http://www.acf.hhs.gov/programs/cse/newhire/csenet/contacts/csenet.htm
- Exchange Agreement information
http://ocse3.acf.hhs.gov/ext/irg/sps/selectastate.cfm
http://151.196.108.20/irg/overview.asp
- CSENet 2000 IGD and Appendices
http://www.acf.hhs.gov/programs/cse/newhire/csenet/library/csenet2000/csenet2000.htm
|
Print
