FPLS RELEASE 02-01 FCR FOCUS GROUP

**DECEMBER 13, 2001, MEETING and**

**DECEMBER 20, 2001, MEETING**

**TELECONFERENCE SUMMARY**

A.  **GENERAL**

# The FCR Focus Group held two teleconferences, on December 13, 2001, and on December 20, 2001, to review manifest items that are scheduled for release in May 2002.

Nancy Sheain, one of Lockheed Martin's Development Managers, reminded
the group that the items under consideration did not include all of the
scheduled changes, but were the ones that needed additional State input.
She also reminded the group that the documents reviewed were drafts and
not the final specifications. They were disseminated for discussion
purposes only.

The following meeting summary highlights the points covered, the
material discussed, and the decisions that were made at the meeting.
Materials for the meetings were provided beforehand. The discussion
points included in this summary do not repeat the understanding obtained
from the materials.

## PARTICIPANTS

Representatives from OCSE Management, LM Development Staff, TRW
Technical Support, SSA, and representatives from New Hampshire,
Virginia, Arizona, Iowa, Minnesota, Pennsylvania, North Carolina,
Washington and Illinois.

## C. PROPOSED SYSTEM CHANGES

1.  **CCN 1338 -- Provide a Complete Employer Data Indicator**

```{=html}
<!-- -->
```
a.  **Discussion**

-   Withholding can be more automated by identifying the records with
    all of the needed employer data.

-   The employer field sometimes contains a service provider rather than
    an employer.

-   FEIN might not be correct, but it will contain all valid numerics.

-   The indicator would not undo the suppression of Proactive Match
    Records that fail the edits. (Suppression of Proactive Match Records
    that fail the address edits will continue, but this issue will be
    reviewed further.)

-   Many State systems are programmed to deal only with complete
    addresses, so perhaps we should suppress. Some States do load
    incomplete addresses now.

-   Many States already have features in their State systems that
    address this need.

-   Even if employer addresses are incomplete or missing, it would be
    helpful to include the employer name with the FEIN in order to give
    the States something they can use to find an address.

b.  **Decisions**

-   This change request was identified as a low priority.

-   This change request was classified as a no State impact item because
    it will utilize filler to accommodate this new field.

-   Due to the fact that this change request is a No State Impact item
    and is a low priority, it will not be included in the May 2002
    release.

-   If this change is to be implemented, a Flash Bulletin will be issued
    describing the change. In addition, to help the States document and
    monitor this change, it will be described in the next formal Release
    documentation after it is implemented.

```{=html}
<!-- -->
```
-   The indicator will have three possible codes:

> C -- Complete and scrubbed address.
>
> I -- One or more of the five elements missing.
>
> X -- All elements are present, but the address could not be scrubbed.
> (Although 'S' was initially suggested for this value, after the
> meeting, the development team chose to utilize the value of 'X'
> instead.)

2.  **CCN 1282 - Return Participant Type in the FCR-to-NDNH Response
    Record**

```{=html}
<!-- -->
```
a.  **Discussion**

> There were no comments on this item.

b.  **Decisions**

This is a no State impact item that is planned for a mid-March
implementation. At that time a Flash Bulletin will be issued describing
the change. In addition, to help States document and monitor this
change, it will also be described in the May Release documentation.

3.  **CCN 1255 -- Consistency Edit Between Date of Birth and Participant
    Type**

```{=html}
<!-- -->
```
a.  **Discussion**

It was agreed that no additional warning code would be necessary if the
FCR can send the file mentioned in CCN 1357, which fulfills this need
and more.

b.  **Decisions**

This CCN will be rescinded since CCN 1357 (see below) will take care of
this need

4.  **CCN 1357 -- Create a Data Inconsistency File**

```{=html}
<!-- -->
```
a.  **Discussion**

> See decisions below.

b.  **Decisions**

-   The threshold for an adult is over ten years old.

```{=html}
<!-- -->
```
-   The file will consist of records that have one or more of the five
    relational inconsistencies.

-   The sixth item (DOB unknown on IV-D case) will be dropped.

-   The file should be handled like the Reconciliation File.

-   A quarterly file is indicated.

-   No warning codes will be associated with the records.

-   The file will require a new CONNECT:Direct process.

-   This is classified as a Minor Release item and will be included in
    the May 2002 Release.

c.  **Action Items**

Pat Snodgrass will provide a list of alert/warning messages that relate
to the conditions that might be included in such a file.

5.  **CCN 1180 -- Store Default Values in the NDNH**

```{=html}
<!-- -->
```
a.  **Discussion**

> There are times when data elements on the NDNH are stored in a format
> that is inconsistent with a State's field type. If States receive such
> data, the State's production environment may be subject to abnormal
> terminations. The discussion revolved around the trade-off of storing
> exactly what was submitted versus storing and returning an adjusted
> value. The suggestion was made that under conditions mentioned above,
> the NDNH should default the values in these fields to either spaces or
> zeros as appropriate. The States pointed out that, rather than
> rejecting an NDNH record that contains invalid data, they would still
> prefer the record to be stored because partial and erroneous data is
> better than no data.

b.  **Decisions**

-   This proposed change would not require the States to make any
    programming changes; therefore, it will not be part of a formal
    State Release but will be implemented as part of OCSE's routine
    system maintenance.

-   Defaults of zeros in numeric fields and spaces in alphanumeric
    fields are preferred.

-   The default for date fields will be spaces.

-   Foreign addresses should continue to remain untouched.

6.  **CCN 1356 -- Reject Duplicate Locate Requests**

```{=html}
<!-- -->
```
a.  **Discussion**

> Pat Snodgrass clarified the fact that requests from different counties
> in the same State and from different users in the same county would
> not be considered duplicates, so it was agreed that a new reject code
> and a warning code should be set up for duplicates. The FCR will
> accept and send on for regular processing those requests for sources
> other than the duplicate sources. Under some circumstances, the FPLS
> rejects locates currently, so the States are familiar with it.

b.  **Decisions**

-   States are agreeable to this change as described in the proposed May
    Release Manifest.

-   This is classified as a Minor Release item and will be included in
    the May 2002 Release.

7.  **CCN 1331 -- Provide a Closed Account Indicator for MSFIDM
    Matches**

```{=html}
<!-- -->
```
a.  **Discussion**

There is outreach to the Financial Institution to populate the field.
There were no comments on this.

b.  **Decisions**

This is classified as a Minor Release item and will be included in the
May 2002 Release.

8.  **CCN 370 -- Make SVES Available As a Locate Source**

```{=html}
<!-- -->
```
a.  **Discussion**

The development team explained SVES responses would not be bundled with
other Locate Responses. The response records will be sorted and merged
with the other response records. AWR responses will continue to be
bundled as they currently are. New Hampshire and Virginia now receive
SVES through their IV-A agency.

b.  **Decisions**

To see the Questions and Answers for some specific fields on the SVES
Record Layouts, refer to Attachment - A, "SVES Data Elements Questions
and Answers from 12/20/01 Meeting" contained in these notes.

c.  **Action Items**

-   Lockheed Martin will check to see how SVES will react to aliases and
    multiple SSNs and whether the FCR can handle the responses.

-   Those States that did not review the record layouts will send
    comments to the T/S team.

-   Lockheed Martin will research whether the DOD on the Title II Locate
    Response Record is the same as SSA's DOD. John Bauer will confirm.

-   Lockheed Martin will get the Data Dictionary from SSA.

-   Lockheed Martin will find out about the Railroad Retirement and
    disability claim and the Title II monthly benefits -- last eight
    months.

-   Lockheed Martin will research the order received.

-   Lockheed Martin will research the SSA district office code that
    appears on the record.

-   Iowa will check to see whether States want additional fields from
    SVES (e.g., Other Name).

-   Other questions for SSA (See also Attachment -- A, "SVES Data
    Elements Questions and Answers from 12/20/01 Meeting" below:

```{=html}
<!-- -->
```
-   Will self-employment income be on the Locate Record?

-   What if the Date of Death conflicts with the Death Master File?

-   What is Essential Person?

-   INP & RPD -- is check being held?

```{=html}
<!-- -->
```
-   The States will send follow-up questions for discussion at a future
    meeting by close of business, December 14, 2001.

## NEXT STEPS

1.  There will be a follow-up meeting next Thursday, 12/20/01.

2.  Action Items must be completed by those assigned.

3.  The States will email follow-up questions on the SVES Locate
    Response Records.

## Follow-up Meeting of 12/20/01 

1.  A follow-up meeting was held to respond to specific questions that
    pertained to some of the SVES data elements.

2.  Attachment A, "SVES Data Elements Questions and Answers from
    12/20/01 Meeting", is a chart of the specific questions and answers
    that were discussed during the follow-up meeting.

3.  The far left column, "Record Layout Chart ID", of the Attachment A
    chart refers to Appendix-A, "Response Record Layouts", Chart A-1
    through Chart A-4 of the FCR Release 02-01 Minor Specifications
    posted on the OCSE Website.

4.  Please note that the words in italics were added after the meeting
    by SSA to clarify some of the answers.

+-----+-----------+----+---------------------------+-----------------+
| S   |           |    |                           |                 |
| VES |           |    |                           |                 |
| D   |           |    |                           |                 |
| ata |           |    |                           |                 |
| El  |           |    |                           |                 |
| eme |           |    |                           |                 |
| nts |           |    |                           |                 |
| Que |           |    |                           |                 |
| sti |           |    |                           |                 |
| ons |           |    |                           |                 |
| and |           |    |                           |                 |
| A   |           |    |                           |                 |
| nsw |           |    |                           |                 |
| ers |           |    |                           |                 |
| f   |           |    |                           |                 |
| rom |           |    |                           |                 |
| 12  |           |    |                           |                 |
| /20 |           |    |                           |                 |
| /01 |           |    |                           |                 |
| M   |           |    |                           |                 |
| eet |           |    |                           |                 |
| ing |           |    |                           |                 |
+=====+===========+====+===========================+=================+
| Rec | Data      | Po | Question                  | Answer          |
| ord | Element   | si |                           |                 |
| Lay |           | ti |                           |                 |
| out |           | on |                           |                 |
| Ch  |           |    |                           |                 |
| art |           |    |                           |                 |
| Id  |           |    |                           |                 |
+-----+-----------+----+---------------------------+-----------------+
| All | N/A       | N  | It was mentioned during   | A data          |
|     |           | /A | the conference call that  | dictionary for  |
|     |           |    | an updated copy of the    | SVES elements   |
|     |           |    | Data Dictionary is        | will be         |
|     |           |    | needed.  There are        | provided.       |
|     |           |    | several references        |                 |
|     |           |    | throughout the SVES       | SVES States can |
|     |           |    | documentation to the Data | also specify    |
|     |           |    | Dictionary. In these      | the continued   |
|     |           |    | situations, no other      | receipt of AWR  |
|     |           |    | field information is      | information.    |
|     |           |    | provided so States are    |                 |
|     |           |    | unable to determine what, |                 |
|     |           |    | if any, use they will be  |                 |
|     |           |    | able to make of these     |                 |
|     |           |    | fields until there is     |                 |
|     |           |    | more information about    |                 |
|     |           |    | them.                     |                 |
|     |           |    |                           |                 |
|     |           |    | In a previous discussion  |                 |
|     |           |    | States were led to        |                 |
|     |           |    | believe that they would   |                 |
|     |           |    | continue getting the SSA  |                 |
|     |           |    | E01 data in addition to   |                 |
|     |           |    | the new records. States   |                 |
|     |           |    | want to receive the new   |                 |
|     |           |    | data and the old E01      |                 |
|     |           |    | data. Will they?          |                 |
+-----+-----------+----+---------------------------+-----------------+
| All | N/A       | N  | Are all of these records  | SVES is         |
|     |           | /A | both Locate Request       | available only  |
|     |           |    | Responses and Proactive   | as a Locate     |
|     |           |    | Match Response Records?   | Request and is  |
|     |           |    | If so, will States        | not searched    |
|     |           |    | receive the CHART A-4,    | for proactive   |
|     |           |    | "SVES Not Found Response  | matches.        |
|     |           |    | Record", on anyone who    |                 |
|     |           |    | was not found in a        |                 |
|     |           |    | proactive match?          |                 |
+-----+-----------+----+---------------------------+-----------------+
| All | N/A       | N  | Need self-employment or   | This will be    |
|     |           | /A | any income or asset       | reviewed to     |
|     |           |    | information to be         | determine       |
|     |           |    | available from the SSA    | whether it can  |
|     |           |    | Database.                 | be added in the |
|     |           |    |                           | future.         |
+-----+-----------+----+---------------------------+-----------------+
| All | N/A       | N  | Need to be able to submit | The FCR submits |
|     |           | /A | multiple aliases and SSNs | verified        |
|     |           |    | to the FCR for matching   | multiple SSNs   |
|     |           |    | purposes.                 | on the FCR      |
|     |           |    |                           | Database that   |
|     |           |    |                           | are associated  |
|     |           |    |                           | with the SSN on |
|     |           |    |                           | a Locate        |
|     |           |    |                           | Request. States |
|     |           |    |                           | can submit      |
|     |           |    |                           | individual      |
|     |           |    |                           | requests using  |
|     |           |    |                           | their set of    |
|     |           |    |                           | multiple        |
|     |           |    |                           | aliases and     |
|     |           |    |                           | SSNs, all of    |
|     |           |    |                           | which are       |
|     |           |    |                           | subject to      |
|     |           |    |                           | verification.   |
+-----+-----------+----+---------------------------+-----------------+
| All | N/A       | N  | Does Title II include     | Title II        |
|     |           | /A | State, county and Federal | includes        |
|     |           |    | retirement, or is it just | Federal         |
|     |           |    | Federal retirement?       | payments for    |
|     |           |    |                           | Social          |
|     |           |    |                           | Security. It    |
|     |           |    |                           | does not        |
|     |           |    |                           | include State,  |
|     |           |    |                           | county, and     |
|     |           |    |                           | Federal         |
|     |           |    |                           | pensions.       |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Race Code | 1  | What is the difference    | There is no     |
| art |           | 01 | between N and B? Is this  | difference.     |
| A-2 |           |    | something we need to      | *(This is not a |
|     |           |    | distinguish when keeping  | required data   |
|     |           |    | track of demographic      | element.)*      |
|     |           |    | information?              |                 |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Title XVI | 1  | Is this a duplication of  | The death match |
| art | Date of   | 10 | the death match process   | uses a file     |
| A-2 | Death     | -1 | that was just             | that NTIS       |
|     |           | 17 | implemented?              | purchases from  |
|     |           |    |                           | SSA.            |
|     |           |    |                           | Verification is |
|     |           |    |                           | not a factor on |
|     |           |    |                           | that file. On   |
|     |           |    |                           | the other hand, |
|     |           |    |                           | the date on     |
|     |           |    |                           | this Title XVI  |
|     |           |    |                           | response record |
|     |           |    |                           | is considered   |
|     |           |    |                           | verified when   |
|     |           |    |                           | the Date of     |
|     |           |    |                           | Death Source    |
|     |           |    |                           | Code is 1       |
|     |           |    |                           | through 6.      |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Date of   | 1  | Does the new SSA death    | The SSA death   |
| art | Death     | 18 | information (from the     | information     |
| A-2 | Source    |    | November Release) come    | (from the       |
|     | Code      |    | from all of the sources   | November 2001   |
|     |           |    | shown for this field?     | Release) comes  |
|     |           |    | This was mentioned in the | from all of the |
|     |           |    | call and States were not  | sources in this |
|     |           |    | certain if the            | field and more. |
|     |           |    | information was the same  | This field is   |
|     |           |    | or not.                   | not associated  |
|     |           |    |                           | with that death |
|     |           |    |                           | file. It exists |
|     |           |    |                           | only in the     |
|     |           |    |                           | Title XVI       |
|     |           |    |                           | record and will |
|     |           |    |                           | contain a       |
|     |           |    |                           | "verified" code |
|     |           |    |                           | only when the   |
|     |           |    |                           | recipient is    |
|     |           |    |                           | receiving Title |
|     |           |    |                           | XVI payments.   |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Payee     | 3  | When and why would        | A person can    |
| art | State of  | 87 | another State and county  | live in one     |
| A-2 | Jur       | -3 | have jurisdiction?        | State and       |
|     | isdiction | 88 |                           | receive         |
|     | and       |    | Instead of the State and  | benefits from   |
|     |           | 3  | county code, is it        | another State   |
|     | Payee     | 89 | possible to get the       | (*e.g., be a    |
|     | County of | -3 | address for the other     | resident in one |
|     | Jur       | 91 | locality?                 | State and       |
|     | isdiction |    |                           | in              |
|     |           |    |                           | stitutionalized |
|     |           |    |                           | in a different  |
|     |           |    |                           | State).*        |
|     |           |    |                           |                 |
|     |           |    |                           | That            |
|     |           |    |                           | information is  |
|     |           |    |                           | not available.  |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Payee     | 3  | Is it possible to get the | That            |
| art | District  | 92 | District Office address   | information is  |
| A-2 | Office    | -3 | on SVES?                  | not available   |
|     | Code      | 94 |                           | on SVES.        |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Type of   | 3  | Can you define "Essential | An "essential   |
| art | Payee     | 95 | Person"?                  | person" is a    |
| A-2 | Code      | -3 |                           | person that is  |
|     |           | 97 | What is the difference    | necessary for   |
|     |           |    | between spaces and        | the care of a   |
|     |           |    | \"SEL\"?                  | recipient and   |
|     |           |    |                           | whose presence  |
|     |           |    |                           | is necessary    |
|     |           |    |                           | for the         |
|     |           |    |                           | recipient to    |
|     |           |    |                           | live at home.   |
|     |           |    |                           |                 |
|     |           |    |                           | Spaces are used |
|     |           |    |                           | when the        |
|     |           |    |                           | recipient gets  |
|     |           |    |                           | the check.      |
|     |           |    |                           | There may still |
|     |           |    |                           | be a few        |
|     |           |    |                           | records with    |
|     |           |    |                           | "SEL", which    |
|     |           |    |                           | means the same  |
|     |           |    |                           | thing.          |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Payee     | 3  | Why are 6 lines of        | If a            |
| art | Mailing   | 98 | address being offered     | Representative  |
| A-2 | Address   | -5 | when other programs allow | Payee is        |
|     |           | 17 | for only 4?               | involved, both  |
|     |           |    |                           | the payee's     |
|     |           |    |                           | name and        |
|     |           |    |                           | address and     |
|     |           |    |                           | recipient       |
|     |           |    |                           | information are |
|     |           |    |                           | included in the |
|     |           |    |                           | address field,  |
|     |           |    |                           | which then      |
|     |           |    |                           | might require   |
|     |           |    |                           | the additional  |
|     |           |    |                           | lines.          |
|     |           |    |                           |                 |
|     |           |    |                           | **(Record       |
|     |           |    |                           | layout has been |
|     |           |    |                           | changed since   |
|     |           |    |                           | the meeting.)** |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Record    | 5  | The field comment says,   | This field      |
| art | Esta      | 53 | \"If applicable, this     | should always   |
| A-2 | blishment | -5 | field will contain the    | have a value.   |
|     | Date      | 60 | date the SSI record was   | The words, "If  |
|     |           |    | established for the       | applicable",    |
|     |           |    | recipient\". When would   | will be removed |
|     |           |    | this field not be         | from the        |
|     |           |    | \"applicable\"? Can there | specification.  |
|     |           |    | be a Title XVI recipient  |                 |
|     |           |    | for whom States would     |                 |
|     |           |    | receive information yet   |                 |
|     |           |    | no SSI record has been    |                 |
|     |           |    | established?              |                 |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Date of   | 5  | Is this the date they     | This is the     |
| art | Title XVI | 61 | start receiving?          | date the payee  |
| A-2 | El        | -5 |                           | was found to be |
|     | igibility | 66 | The field comment says,   | eligible. The   |
|     |           |    | \"If applicable, this     | first payment   |
|     |           |    | field will contain the    | is retroactive  |
|     |           |    | application date, final   | to this date.   |
|     |           |    | onset date or date the    |                 |
|     |           |    | recipient attained the    | It can be       |
|     |           |    | age of 65 years,          | spaces if the   |
|     |           |    | whichever is later.\"     | person was      |
|     |           |    | When would this field not | denied or the   |
|     |           |    | be \"applicable\"?        | claim is        |
|     |           |    |                           | pending.        |
|     |           |    | What is meant by \"final  |                 |
|     |           |    | onset date\"?             | The final onset |
|     |           |    |                           | date is the     |
|     |           |    |                           | date to start   |
|     |           |    |                           | the payment in  |
|     |           |    |                           | Disability      |
|     |           |    |                           | cases. *(It is  |
|     |           |    |                           | the date SSA    |
|     |           |    |                           | determined the  |
|     |           |    |                           | individual to   |
|     |           |    |                           | be disabled.)*  |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Title XVI | 5  | How does the appeal level | Appeal Code has |
| art | Appeal    | 67 | affect us?                | virtually no    |
| A-2 | Code      |    |                           | impact on child |
|     |           |    | If the benefits are       | support. It     |
|     |           |    | modified as a result of   | might only be   |
|     |           |    | the appeal, will the      | helpful if the  |
|     |           |    | States receive a new      | recipient is    |
|     |           |    | Title XVI Record?         | being paid      |
|     |           |    |                           | above the level |
|     |           |    |                           | of eligibility  |
|     |           |    |                           | pending the     |
|     |           |    |                           | appeal.         |
|     |           |    |                           |                 |
|     |           |    |                           | No.             |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Title XVI | 5  | Does this denial date     | This date means |
| art | Denial    | 84 | indicate that the         | that the        |
| A-2 | Date      | -5 | individual is not getting | applicant was   |
|     |           | 91 | benefits?                 | denied          |
|     |           |    |                           | immediately and |
|     |           |    | If so, why would a State  | is not          |
|     |           |    | receive this record? Does | receiving       |
|     |           |    | SVES match against        | benefits.       |
|     |           |    | everyone who has ever     |                 |
|     |           |    | received benefits, those  | The FPLS gets a |
|     |           |    | who qualify for benefits, | record whenever |
|     |           |    | and those who are         | Title XVI has a |
|     |           |    | receiving benefits, or    | record,         |
|     |           |    | just those currently      | regardless of   |
|     |           |    | receiving benefits? I was | the eligibility |
|     |           |    | under the impression that | or payment      |
|     |           |    | a State would only        | status.         |
|     |           |    | receive this record if an |                 |
|     |           |    | individual is currently   |                 |
|     |           |    | receiving benefits.       |                 |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Current   | 5  | What is the difference    | Current Payment |
| art | Payment   | 92 | between these two         | Status Code is  |
| A-2 | Status    | -5 | fields?  States can\'t    | the present     |
|     | Code and  | 94 | tell because of the lack  | status          |
|     |           |    | of detail provided in the | *(current       |
|     | Payment   | 5  | field comments and the    | calendar        |
|     | Status    | 95 | lack of a Data Dictionary | month).*        |
|     | Code      | -5 | definition.               |                 |
|     |           | 97 |                           | Payment Status  |
|     |           |    | Is Payment Status Date    | Code is the     |
|     |           |    | the only thing that       | code for the    |
|     |           |    | indicates the date a      | payment that is |
|     |           |    | person starts getting     | calculated six  |
|     |           |    | SSI? Since the Payment    | weeks into the  |
|     |           |    | Status Code appears to    | future.         |
|     |           |    | contain two different     | *(Payment       |
|     |           |    | pieces of information     | Status Code     |
|     |           |    | (the first position       | reflects the    |
|     |           |    | represents SSI status,    | payment and the |
|     |           |    | and positions 558-559     | reason for the  |
|     |           |    | represent the reason for  | status of the   |
|     |           |    | the status code), would   | payment that is |
|     |           |    | it be less confusing to   | calculated six  |
|     |           |    | simply break this field   | weeks into the  |
|     |           |    | down into two separate    | future.)*       |
|     |           |    | fields?                   |                 |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Repre     | 6  | What is a Representative  | Representative  |
| art | sentative | 16 | Payee?                    | Payee is the    |
| A-2 | Payee     |    |                           | person *or      |
|     | Indicator |    |                           | organization*   |
|     |           |    |                           | receiving the   |
|     |           |    |                           | SSI payment on  |
|     |           |    |                           | behalf of the   |
|     |           |    |                           | recipient.      |
|     |           |    |                           | Their name      |
|     |           |    |                           | appears in the  |
|     |           |    |                           | first line of   |
|     |           |    |                           | the address.    |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Custody   | 6  | Since this field is       | This field      |
| art | Code      | 17 | supposed to be describing | describes the   |
| A-2 |           | -6 | who has physical custody, | person or       |
|     |           | 19 | why do codes CHD, ESP and | institution     |
|     |           |    | RPD describe the payee?   | with custody of |
|     |           |    |                           | the recipient.  |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Unearned  | 6  | What is the intended      | This is the     |
| art | Income -  | 26 | purpose of this field?    | counter for the |
| A-2 | Number of |    | Won\'t we get all of the  | number of       |
|     | Entries   |    | occurrences of Unearned   | unearned income |
|     |           |    | Income data without       | types for the   |
|     |           |    | having a field that says  | payee.          |
|     |           |    | how many there are?       |                 |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | State     | Th | Is this considered a      | State           |
| art | S         | is | payment like SSI that is  | Supplement      |
| A-2 | upplement | f  | not counted in child      | Amount is the   |
|     | Amount    | ie | support calculations?     | difference      |
|     |           | ld |                           | between the     |
|     |           | h  |                           | "old"           |
|     |           | as |                           | Supplementation |
|     |           | be |                           | Amount and the  |
|     |           | en |                           | Federal SSI     |
|     |           | r  |                           | amount if the   |
|     |           | em |                           | Federal SSI     |
|     |           | ov |                           | amount was      |
|     |           | ed |                           | less. Many      |
|     |           | fr |                           | States make     |
|     |           | om |                           | these payments  |
|     |           | t  |                           | directly, but   |
|     |           | he |                           | 16 States have  |
|     |           | s  |                           | their payments  |
|     |           | pe |                           | made through    |
|     |           | cs |                           | SSA. They are:  |
|     |           | b  |                           | CA, DE, DC, HI, |
|     |           | as |                           | IA, MA, MI, MT, |
|     |           | ed |                           | NV, NJ, NY, PA, |
|     |           | up |                           | RI, UT, VT and  |
|     |           | on |                           | WA.             |
|     |           | d  |                           |                 |
|     |           | is |                           | NOTE: The       |
|     |           | cu |                           | Technical       |
|     |           | ss |                           | Support Team    |
|     |           | io |                           | will research   |
|     |           | ns |                           | whether this is |
|     |           | pe |                           | used in child   |
|     |           | rt |                           | support         |
|     |           | ai |                           | calculations    |
|     |           | ni |                           | and will notify |
|     |           | ng |                           | the States of   |
|     |           | to |                           | the results.    |
|     |           | th |                           |                 |
|     |           | is |                           |                 |
|     |           | f  |                           |                 |
|     |           | ie |                           |                 |
|     |           | ld |                           |                 |
|     |           | 's |                           |                 |
|     |           | u  |                           |                 |
|     |           | se |                           |                 |
|     |           | fu |                           |                 |
|     |           | ln |                           |                 |
|     |           | es |                           |                 |
|     |           | s. |                           |                 |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | N/A       | N  | Is the prison data only   | This is         |
| art |           | /A | for Federal prisons or    | information     |
| A-3 |           |    | for all prisons? What is  | from all        |
|     |           |    | the source of the         | prisons that    |
|     |           |    | prisoner data? What       | take part in    |
|     |           |    | information does SSA      | the bounty      |
|     |           |    | have, where does it come  | program. State, |
|     |           |    | from, and for what        | Federal, and    |
|     |           |    | purpose?                  | Local jails and |
|     |           |    |                           | prisons are     |
|     |           |    |                           | offered         |
|     |           |    |                           | incentives to   |
|     |           |    |                           | report          |
|     |           |    |                           | prisoners       |
|     |           |    |                           | through a       |
|     |           |    |                           | bounty paid by  |
|     |           |    |                           | SSA. Federal    |
|     |           |    |                           | prisons will be |
|     |           |    |                           | included by the |
|     |           |    |                           | time SVES       |
|     |           |    |                           | becomes an      |
|     |           |    |                           | active Locate   |
|     |           |    |                           | source.         |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | SSN       | 6  | Since a prerequisite of   | This is the SSN |
| art | Reported  | 4- | matching participants     | reported by the |
| A-3 | by Prison | 72 | with the SSA records is a | Prison. It is   |
|     |           |    | verified SSN, will this   | verified by SSA |
|     |           |    | SSN always equal the      | and used on the |
|     |           |    | State-submitted SSN or    | FCR match.      |
|     |           |    | could this be an alias?   |                 |
|     |           |    | We have discovered that   |                 |
|     |           |    | our participants are      |                 |
|     |           |    | using false SSNs through  |                 |
|     |           |    | multiple SSN matches with |                 |
|     |           |    | our State Department of   |                 |
|     |           |    | Corrections, and I am     |                 |
|     |           |    | wondering if the SSN in   |                 |
|     |           |    | this field may end up     |                 |
|     |           |    | being different than the  |                 |
|     |           |    | submitted SSN. If so, is  |                 |
|     |           |    | the prison giving us the  |                 |
|     |           |    | SSN the inmate most       |                 |
|     |           |    | commonly uses?            |                 |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Submitted | 2  | The field comments say    | This is the     |
| art | First     | 74 | \"SVES submitted\" name.  | name that the   |
| A-3 | Name,     | -3 | Where are these values    | State provides  |
|     | Submitted | 05 | derived?                  | on its FCR      |
|     | Middle    |    |                           | Locate Request. |
|     | Initial,  |    |                           | This has been   |
|     | Submitted |    |                           | changed to read |
|     | Last Name |    |                           | "Submitted      |
|     |           |    |                           | Name".          |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Date of   | 3  | The field comments        | This field      |
| art | Co        | 97 | indicate that a date will | always has a    |
| A-3 | nfinement | -4 | be sent if applicable.    | value. The      |
|     |           | 04 | When would this field not | words, "If      |
|     |           |    | be applicable (contain    | applicable",    |
|     |           |    | spaces)?                  | have been       |
|     |           |    |                           | deleted from    |
|     |           |    |                           | the             |
|     |           |    |                           | specification.  |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Submitted | 2  | The field comments say    | This is the     |
| art | First     | 74 | \"SVES submitted\" name.  | name the State  |
| A-4 | Name,     | -3 | Where are these values    | provides on its |
|     | Submitted | 05 | derived?                  | FCR Locate      |
|     | Middle    |    |                           | Request. This   |
|     | Initial,  |    |                           | has been        |
|     | Submitted |    |                           | changed to read |
|     | Last Name |    |                           | "Submitted      |
|     |           |    |                           | Name".          |
+-----+-----------+----+---------------------------+-----------------+
| Ch  | Locate    | 3  | Is it safe to assume that | There is no     |
| art | Response  | 75 | if a State receives one   | response for a  |
| A-4 | Code      | -3 | of the other records      | person with an  |
|     |           | 76 | (CHART A-1, A-2, or A-3)  | FV indicator on |
|     |           |    | that there is no FVI or   | the FCR. If the |
|     |           |    | on the individual? In     | indicator       |
|     |           |    | other words, can we code  | exists when the |
|     |           |    | our programs to remove    | Locate Request  |
|     |           |    | FVI from case             | is received,    |
|     |           |    | participants if that      | the request is  |
|     |           |    | participant receives a    | rejected.       |
|     |           |    | CHART A-1, CHART A-2, or  |                 |
|     |           |    | CHART A-3 record?         |                 |
+-----+-----------+----+---------------------------+-----------------+