Statistical Report
General Information
|
|
Release 07-01 - Manifest Minor
June 1, 2007
TABLE OF CONTENTS
EXECUTIVE SUMMARY
The Office of Child Support Enforcement (OCSE) is planning a Minor State Impact Release for the Federal Parent Locator Service (FPLS), to take effect on or about June 1, 2007. This Release Manifest describes the schedule for, and content of, this release, which is numbered 07-01. Note that some of the changes will be implemented at a time different from the June 1 Release date.
The release schedule focuses on three main events:
- posting of this Manifest on the OCSE Website,
- posting of the detailed specifications on the Website, and
- implementation of the software changes.
The schedule also includes the State conference calls that will be held at key points during the release planning period to assist States in preparation for the changes.
The major part of this Manifest is composed of individual sections that describe each of the changes.
There is one Child Support Enforcement Network (CSENet) change, which will be implemented on June 1, 2007.
There are six Federal Case Registry (FCR) changes, which will be implemented on July 13, 2007. Note, however, that the response data for the “Return Insurance Match Output” change will be implemented later, on a date that will be announced when the interfaces have been more firmly established. OCSE is providing specifications for the response file at this time to give States ample time to program for this very important source of income.
There are three Federal Offset changes, all of which will be implemented on June 1, 2007.
There are two changes to the Query Interstate Cases for Kids (QUICK) system, both of which will be implemented on June 1, 2007.
As a result, Release 07-01 will be implemented in two phases:
- June 1, 2007 – CSENet (CCI 278), Federal Offset (CCIs 2149, 2240 and 2241), and QUICK (CCIs 2083 and 2161)
- July 13, 2007 – FCR (CCIs 2180, 2182, 2191, 2227, 2228 and 2235)
This document also includes two appendices. Appendix A, "Planned Future Enhancements", provides information about a future change that is being planned for after Release 07-01. OCSE welcomes States' comment on this planned future enhancement. Appendix B, "Clarifications of Recent Changes", gives clarifications on a recent change to draw States' attention to this additional functionality that States may want to incorporate into their processing. As part of this Release Manifest, both of these sections include information on QUICK.
Table of Contents
RELEASE SCHEDULE
| Dates |
Activities |
| February 1, 2007 (Thursday) |
Post the Manifest to the OCSE Website. |
CSENet, FCR and QUICK Release Manifest Teleconferences:
- February 13, 2007 10:00 AM (Tuesday)
- February 15, 2007 3:00 PM (Thursday)
Federal Offset Release Manifest Teleconferences:
- February 20, 2007 2:00 PM (Tuesday)
- February 21, 2007 10:00 AM (Wednesday)
- February 22, 2007 10:00 AM (Thursday)
|
Multistate conference call with States' technical support regarding the Release Manifest. Please plan to attend one of the sessions.
The objective of the call is to address the following:
- What are your questions, comments and/or concerns?
- Will you need to make changes to your system?
- Do you have any issues concerning the Release implementation date?
|
| March 1, 2007 (Thursday) |
Post the Release Specifications to the OCSE Website. |
CSENet, FCR and QUICK State Specifications Teleconferences:
- March 20, 2007 10:00 AM (Tuesday)
- March 22, 2007 3:00 PM (Thursday)
Federal Offset State Specifications Teleconferences:
- March 27, 2007 2:00 PM (Tuesday)
- March 28, 2007 10:00 AM (Wednesday)
- March 29, 2007 10:00 AM (Thursday)
|
Multistate conference call with states' technical support regarding the Release Specifications. Please plan to attend one of the sessions.
The objective of the call is to review the specifications and Q&A.
|
| TBD (to be established during conference calls) |
Test with States as necessary. |
| June 1 (Friday) |
OCSE implementation of FPLS Release 07-01 (except for items noted for later release) |
Table of Contents
| System |
CHILD SUPPORT ENFORCEMENT NETWORK |
| Title |
Discontinue FIRG Update File (OCSE Ref #278) |
| Proposed Changes |
The CSENet application is being modified so that States only receive active address information in the Intergovernmental Referral Guide (IRG) Master File. |
| Impact |
With the implementation of the 07-01 release, States will no longer receive the IRG Update file from the CSENet application. |
| Business Requirements or Benefit |
The CSENet application will download only the IRG Master file from the IRG server twice per month and send it to the States. |
| Reason |
The IRG Update file contains invalid data. Periodically replacing the address data using the IRG Master file will provide more accurate address information. |
| Point of Contact |
|
| Targeted Implementation Date |
June 1, 2007 |
Table of Contents
| System |
FEDERAL CASE REGISTRY |
| Title |
Implement Proactive Matching with SVES (OCSE Ref #2180) |
| Proposed Changes |
The FCR is being modified so that States that elect to receive SVES information will have an option to receive proactive SVES matches on their new and changed Persons who are in a IV-D case. An additional option is being provided to enable States to specify which Participant Types to use in this Proactive Match. This is the first portion of a phased approach to implement SVES Proactive Matching. Subsequent phase(s) will implement matching to identify “pending” Title II claims cases. |
| Impact |
States that currently receive SVES Locate information can choose to receive SVES information on a proactive basis, and can designate the Participant Types to include in this Proactive Match. The existing FCR SVES Title II, Title XVI and Prisoner Locate Response record layouts (Record Identifier of ‘FK’) will be returned for this proactive match, and the SVES Locate Response records will be modified to contain a new field, SVES Match Type, with a ‘P’ to indicate the response is the result of proactive matching. |
| Business Requirements or Benefit |
This change will expedite the States' ability to identify obligors who are receiving SSA benefits, which should increase collections, obligations, paternities and Locates. |
| Reason |
To provide States the option to receive through proactive matching, Title II, Title XVI and Prisoner data from SVES for persons in IV-D cases with no family violence indicated. |
| Point of Contact |
|
| Targeted Implementation Date |
July 13, 2007 |
Table of Contents
| System |
FEDERAL CASE REGISTRY |
| Title |
Filter Negative Locate Responses (OCSE Ref #2182) |
| Proposed Changes |
The FCR is being modified to provide States with the option to suppress Negative (no record found) Locate Responses, and provide an additional option to override this filter if a negative response is the last response of a group so a Locate Closed Indicator can be returned. |
| Impact |
States who choose this option will receive fewer Negative Locate Responses. This option only applies to Locate Request type 'CS' (request is for IV-D purposes). All other Locate Request types will not be filtered.
If a State opts to suppress Negative Locate Responses, the following Locate Responses with Locate Response Code of '10' or '22' will not be returned:
- FCR-NDNH Locate/Proactive Match Response Record (Record Identifier 'FN') with NDNH Match Type of 'L' and Locate Source Response Code of 'H01'.
- FCR-SVES Not Found Response Record (Record Identifier 'FK') with Locate Source Response Agency Code of 'E10'.
- FCR Locate Response Record (Record Identifier 'FF') and for Locate Source Response Agency Codes 'A01' (DoD), 'A02' (FBI), 'A03' (NSA), 'C01' (IRS non-1099), 'E01' (SSA) and 'F01' (DVA).
Locate Response Codes of '06' (FCR case type change from IV-D to non-IV-D, person deleted from case, or case closed) and '39' (disclosure prohibited, person is associated with family violence) will continue to be returned to the submitter for all Locate Sources.
States that want to continue to receive the last negative response, with the Locate Closed Indicator, may continue to receive it by selecting a second Filter Option, which will be provided. This first level filtering is part of a longer-term effort to improve the quality of data being returned by the FPLS. |
| Business Requirements or Benefit |
This change should reduce the number of duplicate Locate Responses being returned to States, reduce State CPU processing time, reduce worker alerts, reduce negative responses as new Federal and private sources are added, and save workers' time in reviewing old data. |
| Reason |
States have often indicated that a significant amount of redundant data is returned, requiring that States either filter the duplicates or send repetitive notices to caseworkers. |
| Point of Contact |
|
| Targeted Implementation Date |
July 13, 2007 |
Table of Contents
| System |
FEDERAL CASE REGISTRY |
| Title |
Provide DMDC Sponsor Information (OCSE Ref #2191) |
| Proposed Changes |
The FCR-DMDC Match process is being modified to return information relating to the sponsor of the child if the sponsor is coded as "Other" (that is, not CP, NCP or PF). |
| Impact |
The FCR will return additional data on sponsors, including a code to specify the child’s relationship to the ‘Other’ sponsor as: Child, Foster Child, Pre-adoptive Child, Ward, Stepchild, Self, Spouse and Other/Unknown. In specific instances, the FCR will also return the ‘Other’ sponsor’s name and SSN. |
| Business Requirements or Benefit |
To provide additional identifying information that is related to the child's medical coverage sponsor, when the sponsor has been identified as "Other". |
| Reason |
States expressed a desire to obtain a Relationship code for "Other" sponsors for such reasons as Review and Adjustment. Without more meaningful information, the responses with a sponsor code of "Other" were of limited value. |
| Point of Contact |
|
| Targeted Implementation Date |
July 2007 |
Table of Contents
| System |
FEDERAL CASE REGISTRY |
| Title |
Return Error/Warning Codes for AD, PK and CV Locate Types that include NSA (OCSE Ref #2227) |
| Proposed Changes |
The FCR is being modified so that AD, PK, and CV Locates that include a request for NSA will be returned with an appropriate error or warning message. |
| Impact |
States that submit a Locate Request Type 'AD', 'PK' or 'CV' with only one Locate Source of 'A03' (NSA) will receive error code 'TE027' (Invalid Locate Source Code), and the Locate transaction will be rejected.
States that request Locate source "NSA", along with one or more other sources (such as "SSA", FBI" etc.), or Locate source is "ALL" will receive a warning code of LW002 (Locate Source not available for Locate Request Type) on acknowledgement if the Locate Request type is 'AD', 'PK' or 'CV'.
|
| Business Requirements or Benefit |
To generate error/warning codes when applicable. |
| Reason |
NSA information is not allowed for Locate Request Types AD, PK or CV. |
| Point of Contact |
|
| Targeted Implementation Date |
July 13, 2007 |
Table of Contents
| System |
FEDERAL CASE REGISTRY |
| Title |
Return Alternate NDNH SSN/Name Validation Codes (OCSE Ref #2228) |
| Proposed Changes |
The FCR-NDNH Locate and Proactive Match process is being modified to return records that contain a code that indicates that the SSN/Name combination was not verified at SSA, but successfully passed a name matching routine used by NDNH in conjunction and in combination with the SSN. |
| Impact |
The FCR-NDNH Locate/Proactive Match process will now include response records with a new Locate Response Code of ‘48’. This code will identify W-4, QW or UI responses that contain an unverified SSN/Name combination with a probable name match. |
| Business Requirements or Benefit |
Use of the name matching logic will provide States with additional NDNH information that was not previously available. |
| Reason |
These matches will allow States to pursue enforcement or establishment actions on cases for which they have had little information in the past. Additional codes will assist States to correctly identify and process person data that may need follow up. |
| Point of Contact |
|
| Targeted Implementation Date |
July 13, 2007 |
Table of Contents
| System |
FEDERAL CASE REGISTRY |
| Title |
Return Insurance Match Output to State Child Support Enforcement Agencies (OCSE Ref #2235) |
| Proposed Changes |
The FCR is being modified to return a new FCR Response record that contains the results of matches of persons on the Federal Tax Refund Offset File with insurance data bases. |
| Impact |
This new Insurance Match record format will be included with the Release 07-01 Specifications. However, States will not receive these new records until Insurance Matches are negotiated and developed with insurers or their agents. At that time, States will need to implement programming changes to receive the Insurance Match information from OCSE via the FCR. This response record format will enable States to plan for a successful early implementation of the Insurance Match as subsequent interfaces with insurers are developed. |
| Business Requirements or Benefit |
This match will provide States with an additional enforcement mechanism to collect past-due child support. |
| Reason |
Section 7306 of the Deficit Reduction Act of 2005 amended Section 452 of the Social Security Act to authorize OCSE, through the FPLS, to compare information concerning individuals that owe past-due child support with information that is maintained by insurers (or their agents) concerning insurance claims, settlements, awards, and payments and return the matches to the State agencies that are responsible for collecting the past-due child support. |
| Point of Contact |
|
| Targeted Implementation Date |
July 13, 2007 |
Table of Contents
| System |
FEDERAL OFFSET |
| Title |
Create New Exclusion Indicator for Insurance Match (OCSE Ref #2149) |
| Proposed Changes |
The Federal Offset System is being modified to provide an Exclusion Indicator to allow individual cases to be excluded from Insurance Match (this information was provided in Release 06-01, and the implementation will be in Release 07-01). |
| Impact |
States will be able to modify the Federal Offset process to exclude an individual case from Insurance Match, if a State is participating in the match. An Exclusion Indicator of ‘INS’ will enable States to exclude an individual case from an Insurance Match. It will be included with the existing Exclusion Indicator codes in positions 188 to 227. |
| Business Requirements or Benefit |
To provide States discretion to control which cases they include in or exclude from future Insurance Match. |
| Reason |
To support legislative changes made in S.1932, Deficit Reduction Act of 2005, Social Security Act 452(l) that allows OCSE to match with insurers and/or their agents. |
| Point of Contact |
|
| Targeted Implementation Date |
June 1, 2007 |
Table of Contents
| System |
FEDERAL OFFSET |
| Title |
Improve SSN/Name Verification Process in Federal Offset (OCSE Ref #2240) |
| Proposed Changes |
The Federal Offset System is being modified to provide SSN/Name verification status and obligor identity information to States relating to eligibility for Department of State passport certification. Please note that as a result of a recent related change, SSN/Name combinations not verified at SSA that successfully pass a name matching routine resulting in a probable name match are eligible for passport denial certification. |
| Impact |
When States submit an Add or Name Change transaction, three additional warning codes may be returned in the Rejected Case Submission and Update Record file for cases if:
- the current SSN/Name does not verify or pass a name match, but a previous SSN/Name for this obligor does verify or pass a name match, or
- the current SSN/Name does not verify or pass a name match, and no previous SSN/Name for this obligor verifies or passes a name match, or
- the Date of Birth and/or Place of Birth for this obligor is invalid.
These warning codes do not mean the transaction was rejected by the Federal Offset System. Warning Codes ‘2’ and ‘3’, above, indicate that the obligor’s SSN/Name or identity information does not meet the requirements for passport denial certification, and the obligor is not eligible. Warning Code ‘1’ indicates that the current SSN/Name would not meet the DoS requirements, but a previous name for this obligor did meet the requirements, and the obligor is eligible.
Additionally, a new field will be added to the Case Reconciliation File to provide the name verification status of an obligor. The code will advise whether:
- the current SSN/Name combination is verified, passed a name match, is not verified, or
- the current SSN/Name combination is not verified but a previous name for this obligor was verified or passed a name match.
|
| Business Requirements or Benefit |
To provide a warning to States that affected cases do not meet the DoS requirements for passport denial certification, to provide additional information so States can determine if a Name Change transaction is necessary to improve the probability of an SSN/Name verification or name match, and to improve customer service at both the State and Federal level. |
| Reason |
To support requirement changes made by DoS for obligors to be considered eligible for passport denial certification, and to improve probability that obligors will meet the DoS requirements for passport denial certification. |
| Point of Contact |
|
| Targeted Implementation Date |
June 1, 2007 |
Table of Contents
| System |
FEDERAL OFFSET |
| Title |
Return Additional Fields in Case Reconciliation File (OCSE Ref #2241) |
| Proposed Changes |
The Federal Offset System is being modified to provide obligor's priority address information that is stored at OCSE to States through the Case Reconciliation File. |
| Impact |
Additional fields will be created in the Case Reconciliation File to provide States with the following obligor priority address information that is stored at OCSE:
- Address Source
- Address Line 1
- Address Line 2
- City
- State
- 9-Digit Zip Code
- Foreign Indicator (for future use)
- Country Name (for future use)
These additional fields will be contained in what is currently used as filler of the record layout. |
| Business Requirements or Benefit |
Additional information can be used by States to determine if the address information that is currently stored at OCSE needs to be updated.
Provide improved customer service.
Improve caseload synchronization between OCSE, FMS and States. |
| Reason |
OCSE uses the priority address for those States that request that OCSE issue their Pre-Offset Notices.
The priority address is also forwarded to FMS.
When a State attempts to obtain an address, or search for a better address, the priority address information that is stored by OCSE may facilitate their enforcement and collection on that obligor. |
| Point of Contact |
|
| Targeted Implementation Date |
June 1, 2007 |
Table of Contents
| System |
QUERY INTERSTATE CASES FOR KIDS (QUICK) |
| Title |
Add Informational Message for Case Not Found (OCSE Ref #2083) |
| Proposed Changes |
The Query Interstate Cases for Kids (QUICK) application is being modified to provide States with a data access response code on the JIT Response XML document when the State does not have a case for the requestor's other State case identifier. |
| Impact |
States will have to program a new data response code if they want to let the requesting State know that the requested Case ID could not be found on their system. |
| Business Requirements or Benefit |
To allow States to return the ‘406’ data access response code and a data message, “Case ID from the other state not found”, on the JIT Response XML document. |
| Reason |
When workers receive the error message “Providing State Error”, they could not determine whether the providing State did not have a case for the Case ID, or if another error occurred (for example, invalid data element or system error). Workers suggested that a specific error message be generated to address this condition; therefore, a new information code and a message is being added to inform workers there is no case in the providing State. |
| Point of Contact |
|
| Targeted Implementation Date |
June 1, 2007 |
Table of Contents
| System |
QUERY INTERSTATE CASES FOR KIDS (QUICK) |
| Title |
Remove Processing Page (OCSE Ref #2161) |
| Proposed Changes |
The Query Interstate Cases for Kids (QUICK) application is being modified to remove the QUICK Processing Page and consolidate its functionality with the Case Request Page. |
| Impact |
The client browser will not have to make a "round-trip" request to the OCSE QUICK server for the processing page. The result will be reduced network traffic and improved response time of requested data. |
| Business Requirements or Benefit |
Consolidate Processing Page with Case Request Page, thus removing one unnecessary page. |
| Reason |
Removing the processing page will speed up communications with State browsers. |
| Point of Contact |
|
| Targeted Implementation Date |
June 1, 2007 |
Table of Contents
APPENDIX A: PLANNED FUTURE ENHANCMENTS
| System |
QUERY INTERSTATE CASES FOR KIDS (QUICK) |
| Title |
QUICK Case Activities |
| Proposed Changes |
The purpose of the Query Interstate Cases for Kids (QUICK) Case Activities Module is to provide States with a standard and secure user interface to access and view case activities information in other States. |
| Impact |
States need resources with expertise to accomplish development. |
| Business Requirements or Benefit |
The QUICK system will expedite communication between States, reduce errors, and reduce the need for using other means to request case activities data from States (e.g., phone calls, faxes, e-mails, interstate transmittals). |
| Reason |
The QUICK Case Activities Module will improve interstate communications through the sharing of case activities and worker contact information between States. |
| Point of Contact |
|
| Implementation Date |
Varies by State |
Table of Contents
APPENDIX B: CLARIFICATIONS OF RECENT CHANGES
| System |
QUERY INTERSTATE CASES FOR KIDS (QUICK) |
| Title |
QUICK Implementation |
| Proposed Changes |
The scope of the QUICK Pilot System is to facilitate the exchange of financial interstate CSE case information between States. The system is hosted by OCSE on the OCSENet with data provided by the States. Using the QUICK Pilot System, a State can either access a website that is hosted on an OCSE server to request and view case information, or use their own user interface to request and view case information. Case information is provided by a State via the QUICK Server using a web service-oriented process. |
| Impact |
The following States are participating in the pilot for this system: North Carolina, Pennsylvania, Virginia, Colorado, Arizona and North Dakota. |
| Business Requirements or Benefit |
This system automates a manual process, thereby:
- improving worker efficiency;
- reducing errors;
- improving customer service; and
- improving time on collections.
|
| Reason |
QUICK improves the response time of interstate case queries. |
| Point of Contact |
|
| Implementation Date |
Summer 2006 |
|
