A. FCR

CCI 2180 – Implement Proactive Matching with SVES

Question 1: What does SVES stand for?
Answer 1: SVES is the State Verification and Exchange System.

Question 2: Will only positive SVES proactive matches be returned to States when Release 07-01 is implemented?
Answer 2: Yes.

Question 3: If the person is found to be deceased, would that be considered a positive or negative SVES response?
Answer 3: When the new information shows that a person is deceased, it is considered a positive match.

Question 4: Where can States get the SVES proactive matching option form?
Answer 4: The form is available with Release 07-01 Specifications, which have been posted to the OCSE website at
http://www.acf.hhs.gov/programs/cse/newhire/library/fcr/fcrspec07-01.pdf

Question 5: Where should States send their completed SVES Proactive matching election form?
Answer 5: The completed form should be mailed to:

Joan O'Connor
Department of Health and Human Services
Administration for Children and Families
Office of Child Support Enforcement
Federal Parent Locator Service, 4th floor
370 L'Enfant Promenade, S.W.
Washington, DC 20447

Forms may also be faxed to Joan O'Connor at 202-401-5553 or 202-401-5647.

Question 6: How frequently will the proactive matching with SVES be performed?
Answer 6: Proactive SVES matching will be done when the State submits an 'Add' or 'Change' person transaction to the FCR.

CCI 2191 – Provide DMDC Sponsor Information

Question 1: For the DMDC matching, will a code be returned to specify the child's relationship to the "other" sponsor for step-children?
Answer 1: Yes, a code will be returned for the step-children; however, no other identifying information is provided for the sponsor. We are only providing information for those relationships where the sponsor has a legal responsibility for the child.

Question 2: Why would DMDC show a relationship code of '1' to a child?
Answer 2: You may see a relationship code of '1' to a child because of the timeframe difference between updating the information in DEERS and providing the information to the States.

CCI 2228 – Return Alternate NDNH SSN/Name Validation

Question 1: QW records often contain truncated names. Are there any statistics on what data has been improved by the NameSearch routine? What is the success rate?
Answer 1: We've been keeping count since October 2006. We were able to match 9% of 4.4 million unverified records, including 3.5 million unverified quarterly wage records.

Question 2: For the alternate NDNH SSN/Name Validation codes, will this name validation routine help with fraudulent use of SSNs?
Answer 2: This process helps compare names that are close, but are not exactly the same. It will not identify individuals who are fraudulently using SSNs.

Question 3: Can States send in all of their unverified SSNs after this process is implemented to see if it would help to verify some name/SSN combinations?
Answer 3: At this time, these routines are used in the NDNH only. In a future release, these routines will be used in the FCR. Once they are implemented in the FCR, States can send in "Add Person" transactions for individuals that were not registered because SSA was unable to verify the SSN/name combinations.

Question 4: Will States be required to make a change to their State system when the new name validation process is implemented?
Answer 4: This will depend on whether the State edits on the Locate Response Code. If so, the State will need to make a change to allow for the new code of '48'.

CCI 2235 – Return Insurance Match Output

Question 1: Will those States that are not ready to receive the insurance match information need to program for the exclusion indicator?
Answer 1: No. States that are not ready to receive and process the insurance match data will not have to program for the insurance exclusion indicator. When a State is ready to receive insurance match data through the FCR, the State should notify OCSE of their decision to participate in the insurance match. If a State that is participating in the insurance match would like the ability to exclude individual cases from the insurance match, that State will need to program the insurance match exclusion indicator to prevent those cases from being included in the match.

Question 2: Can OCSE send an indicator back to the State letting them know that the employer address was the headquarters or location where the individual is working?
Answer 2: No, OCSE cannot provide an indicator because that information is not provided by the insurer.

B. CSENet

CCI 278 – Discontinue FIRG Update File

Question 1: What is the impact to States that download directly from the IRG website?
Answer 1: Data in the IRG Master File is the same as data downloaded from the IRG website. Accurate address information is available from both sources.

Question 2: Why will States no longer receive the IRG Update File?
Answer 2: States will no longer receive the IRG Update File because it contained all change activity throughout the month. It was determined that the IRG Master File, which contains addresses that are complete and up-to-date at the time of transmission, is most useful.

Question 3: What is the impact if a State does not currently receive the IRG Update File?
Answer 3: There is no impact. The State does not have to make any changes

Question 4: Would the IRG Master File contain the following transaction types?

Adds = A
Changes = C
Deletes = D

Answer 4: The Master File contains only up-to-date address information, including 'Adds' and 'Changes'. States will be able to distinguish between an 'Add' and a 'Change'.

Question 5: Has the record layout for the IRG Master File changed?
Answer 5: There are no changes to the record layout for the IRG Master File.

C. QUICK

CCI 2083 - Add Informational Message for Case Not Found

Question 1: What happens if States in production with QUICK cannot program for the new response code '406' and the error message "Case ID from other State not found" by the scheduled release date of June 2007?
Answer 1: As a providing State, States in production will continue to provide the existing response code '405', which will produce the error message "Providing State Error".

Question 2: Does this change affect the HTML or XML States?
Answer 2: Both HTML and XML States will need to program the '406' response code in their response to the requesting State when the Case ID requested is not in the providing State system.

CCI 2161 - Remove Processing Page

Question 1: If a State is currently a QUICK HTML State, would the State need to make changes to the web application to make this change?
Answer 1: No, HTML States do not need to make any changes as a result of this change. The change will be implemented by OCSE.

The background and analysis on 07-01 minor release items can be found at the following URL: http://www.acf.hhs.gov/programs/cse/newhire/library/relmgnt/relmgnt.htm